Open main menu

Changes

Mux configuration

10,667 bytes removed, 10:55, 17 February 2014
no edit summary
= Overview =
 
This wiki is meant to be a starting point for people to learn configure mux for IGEP devices as quickly and easily as possible. This wiki contains:<br>
 
*Mux characteristics summary
*Tips to avoid problems
*Ways to configure mux
*Tables that links peripherals and connectors for IGEPv2 and IGEP MODULE
 
 
There are three ways to configure mux in IGEP Boards based in OMAP35xx and DM37xx:<br>
 
*[[Mux_instructions|Configuring MUX from OS User Space]]. This mode has a issue, when your system reboot or shutdown you will need to configure again. [[How to set up UART2 in J990#First_way|Example]].
*Configuring MUX by using kernel commandline buddies. This way is not avaliable in some cases. [[How to set up UART2 in J990#Second_way|Example]] and [[Linux Kernel 2.6.37.y#Kernel_Parameters|buddies parametres]].<br>
*Editing and compile kernel sources. [[How to set up UART2 in J990#Third_way|Example]].<br>
 
 
= Introduction =
Mux (or multiplexer) is a Omap peripheral that can be controlled via software. Its function is connect other peripherals to some available Omap pins.
• '''INPUTENABLE''' (1 bit) drives an input enable signal to the I/O CTRL.
• '''Off mode values''' (5 bits) override the pin state when the OFFENABLE bit CONTROL. This feature is used for power saving management. Pins in off mode can be configured like output with HIGH or LOW value or input with wake-up detection feature. For input pins, OFFOUTENABLE and OFFOUTVALUE bits can not be configured:
-&gt;OFFENABLE: Off mode pin state override control. Set to 1 to enable the feature and to 0 to disable it.
• '''Wake-up''' bits (2 bits):
-&gt;WAKEUPENABLE: Enable wake-up detection on input. It is also the off mode input enable value.<br> -&gt;WAKEUPEVENT: Wake-up event status for the pin.'''<br>'''  NOTE: Off mode can be configured like pin output with a HIGH&nbsp;or LOW value or pin input with wake-up detection feature.
NOTE-&gt;WAKEUPEVENT: For input pins, OFFOUTENABLE and OFFOUTVALUE bits can not be configuredWake-up event status for the pin.'''<br> '''
{| cellspacing="1" cellpadding="1" border="1" align="center" width="200"
|-
|
=== [[Image:Mux pad configuration diagram.png]] ===
|}
=== Mode selection ===
 
The next table shows all capabilities.<br>
{| cellspacing="1" cellpadding="1" border="1" style="width: 287px; height: 235px;"
|}
<br> '''Definitions:'''
'''Mode 0''' is the primary mode. When mode 0 is set, the function mapped to the pin corresponds to the name of the pin. In IGEP some pads don't use primary mode by default.
'''Mode 1 to mode 6''' are possible modes for alternate functions. On each pin, some modes are used effectively for alternate functions, while other modes are unused and correspond to no functional configuration.
'''The safe mode''' (default mode 7) '''avoids any risk of electrical contention by configuring the pin as an input with no functional interface mapped to it. The safe mode is used mainly as the default mode for all pins containing no mandatory interface at the release of power-on reset.  NOTE: For most pads, the reset value for the MUXMODE field is 0b111. The exceptions are pads to be used at boot time to transfer data from selected peripherals to the external flash memory. <br>
=== Pull Selection ===
Note: when a pin is in output mode, pulls are automatically disableThe next table shows all capabilities.
{| cellspacing="1" cellpadding="1" border="1" style="width: 696px; height: 1px;"
| Pull-up selected and activated if pin is NOT configured as OUTPUT
|}
 
When a pin is in output mode, pulls are automatically disable.
=== Input Enable ===
INPUTENABLE = 0: Input Disable. Pin is configured in output only mode.
INPUTENABLE = 1: Input Enable. Pin is configured in bidirectional mode.  NOTE: For proper functioning of some peripherals INPUTENABLE must be set to 1 for pads configured to drive output clocks:  *SDRC *GPMC *McSPIi *I2Ci *MMCi *McBSPi *HSUSB HOST<br>
=== '''Off mode values''' and '''Wake-up''' ===
This mode is used to disable some pins and reduce low power consumption. <br>  Please contribute .. === '''IGEPv2<br>''' === This How-To is meant to be a starting point for people to learn configure mux for IGEP v2 devices as quickly and easily as possible. For this how-to i used [http://releases.linaro.org/platform/linaro-m/headless/final/linaro-m-headless-tar-20101108-2.tar.gz Linaro Headless] and Ubuntu 10.04 with Linaro Toolchain.<br> IgepV2 Board have a default mux configuration, but some cases is necessary change it, for example your project need [[How to set up UART2 in J990|UART2 at j990]] connector to transmit data, for this purpose you need change some mux configurations to enable it and be sure that this modification don't break or interferes in other IC or peripherals. The mux options are vast. There are three ways to configure mux at DM37xx and OMAP35xx:<br>  *Editing OS User Space. this mode has a issue, when your system reboot or shutdown you will need to configure again. [[How to set up UART2 in J990#First_way|Example]]. *Using kernel buddies. This way is ot avaliable in some cases. [[How to set up UART2 in J990#Second_way|Example]]. *Editing and compile kernel sources. [[How to set up UART2 in J990#Third_way|Example]]. <br> = Feedback and Contributing =
At any point, if you see a mistake you can Please contribute to this How-To.
= Available peripherals on external connector =[http://www.ti.com/lit/ug/spruf98x/spruf98x.pdf More information] about mux.
The next tables show you all the mux capabilities:= Configure Mux =
=== J990 connector ===Mux options are vast, at the beginning can be difficult and tedious change some configurations. Before configure mux, use the following tips to avoid problems:
-There *Mux can connect multiple connectors at the same peripheral, this improper use can damage the processor. Before configure mux, revise that this peripheral is not used in other pads. See schematics or [[Connectors Summary|connectors summary]] for more information. *Some peripherals are only available if you place or replace some resistances. See schematics for more information.<br> *Some connectors share multiples peripherals like OMAP, WIFI/BT combo, etc. You should disable unused peripherals than can be connected to avoid interferences.&nbsp; For example: if you want to control WIFI module via J990 like mm3 and camera, but is not used disable OMAP or if you want use [[How to set up UART2 in this J990|UART2 at j990]] disable Bluetooth. See schematics of board or [[Connectors Summary|connectors summary]] or [[Mux_instructions#Disable_Peripherals|how-to disable peripherals]] or [[How_to_use_GPIOs|how-touse gpios]] for more information.
-High Speed USB 3 is only available on Omap 3530 in the next pads: === IGEPv2 ===
&nbsp;&nbsp;&nbsp;&nbsp; 3: HSUSB3_TLL_NXTNext table pretends help you to configure IGEPv2. First column shows some OMAP35xx/DM37xx peripherals and first row shows all IGEPv2 connectors. Read articles about connector and peripheral before use them. Each configuration can take different solutions. <br> &nbsp;&nbsp;&nbsp;&nbsp; 4: HSUSB3_TLL_D4There are some connectors than have more peripherals available, but they don't have all signals to use it. <br> &nbsp;&nbsp;&nbsp;&nbsp; 5Table shows four answers: HSUSB3_TLL_DIR <br> &nbsp;&nbsp;&nbsp;&nbsp; 6: HSUSB3_TLL_D6<br> &nbsp;&nbsp;&nbsp;&nbsp; 7: HSUSB3_TLL_STP<br> &nbsp;&nbsp;&nbsp;&nbsp; 8: HSUSB3_TLL_D7 <br> &nbsp;&nbsp;&nbsp;&nbsp; 10: HSUSB3_TLL_D5
*"'''Yes, default configuration(utility)'''": Peripheral enabled by default. "utility" shows if this peripheral is used.<br> *"'''Yes, not default configuration(information)'''": Peripheral don't enabled by default. Maybe you need to disable other one<br> *"'''No, via hardware'''": Not available, but via hardware (placing or replacing some resistances) can be enabled.<br> *"'''No'''"
{| cellspacing="1" cellpadding="1" border="1" align="JUSTIFY" style="width: 960px933px; height: 1463px409px;"
|-
| Pad: <br> | Connect to: [[Connectors Summary#J990_connector|J990]] | [[Connectors Summary#J960_connector|J960]] Default peripheral (mode=0) | [[Connectors Summary#J970_connector|J970]] | [[Connectors Summary#J400_connector|J400]] | Default function: [[Connectors Summary#JC30_connector|JC30]] | Other available peripherals: [[Connectors Summary#JA42_connector|JA42]] | style="text-align: left;" [[Connectors Summary#JA41_connector| Share with:JA41]]
|-
| 1 [[Peripherals Summary#UART|UART1]] | No | VIO 1V8 Yes, not default configuration ([[Mux instructions#UART1_in_J960|disable RS485]]) | - No | Power 1v8 No | - No | -<br>No | Yes, not default configuration ([[Mux_instructions#TFP410|disable DVI]])
|-
| 2 | DC 5V | - | Power 5v | - | -<br>|-| 3 [[Peripherals Summary#UART| MMC2_DAT7 UART2]] | MMC2_DAT7 Yes, not default configuration ([[How to set up UART2 in J990| Reset Wlan disable Bluetooth]])
|
MMC2_CLKIN(mode=1) No, [[How to use UARTs#RS232_Schematic_Igep_V2|via hardware]],
MMC3_DAT3(mode=3) [[Mux instructions#Bluetooth|disable Bluetooth]]
GPIO_139(mode=4) | No | No | No | No | <div align="JUSTIFY">'''Wlan:''' This pad can reset Wlan peripheral using Omap GPIO low level (GND). If you reset continuously Wlan all their pads are in High Impedance. Also you can disable Wlan from J990 low level.</div> <div align="JUSTIFY">'''Omap: '''protect Omap pad if you don't use it.'''(1)'''</div>No
|-
| 5 [[Peripherals Summary#UART| MMC2_DAT6 UART3]] | MMC2_DAT6 No | Power down&nbsp; Wlan Yes, default configuration ([[Mux instructions#UART3_in_J960| MMC2_DIR_CMD(mode=1Serial debug]]) | No MMC3_DAT2(mode=3) | No | No GPIO_138(mode=4) | No | <div align="JUSTIFY">'''Wlan:''' This pad can power down Wlan peripheral using Omap GPIO low level (GND)Yes, power up removing GND. Also you can power down Wlan from J990 low level.</div> <div align="JUSTIFY">'''Omap: '''protect Omap pad if you don't use it.'''not default configuration (1[[Mux_instructions#TFP410|disable DVI]])'''</div>
|-
| 7 [[Peripherals Summary#UART|UART4]] | MMC2_DAT5 No | MMC2_DAT5 No | Reset Bluethoot No | No MMC2_DIR_DAT1(mode=1)  MMC3_DAT1(mode=3)  GPIO_137(mode=4) | No | No | <div align="JUSTIFY">'''Bluethoot: '''This pad can reset Bluethoot peripheral using Omap GPIO low level (GND). If you reset continuously Bluethoot all their pads are in High Impedance. Also you can disable Bluethoot from J990 low level.'''Omap: '''protect Omap pad if you don't use it.'''(1)'''<br> </div>No
|-
| 9 [[Peripherals Summary#GPIO| MMC2_DAT4 | MMC2_DAT4 | - GPIO]]
|
MMC_DIR_DAT0Yes, default configuration (mode=1[[Mux instructions#GPIO_in_J990|info]])
MMC3_DAT0(mode=3) | No | No GPIO136| Yes, not default configuration (mode=4[[Mux instructions#GPIO_in_J990|disable JTAG]]) | Yes, default configuration | <div align="JUSTIFY">'''Wlan: '''Protect Wlan if you don' use it. See MMC2_DAT7 pad.</div> <div align="JUSTIFY">'''Omap: '''protect Omap pad if you don't use it.'''Yes, default configuration | Yes, not default configuration (1[[Mux_instructions#TFP410|disable DVI]])'''</div>
|-
| 11 [[Peripherals Summary#SPI|McSPI1]] | MMC2_DAT3 No | MMC2_DAT3 No | Transfer data between Omap and Wlan No | No McSPI3_CS0(mode=1)  GPIO_135(mode=4) | No | Yes, default configuration | <div align="JUSTIFY">'''Wlan: '''Protect Wlan if you don' use it. See MMC2_DAT7 pad.</div> <div align="JUSTIFY">'''Omap: '''protect Omap pad if you don't use it.'''(1)'''</div>No
|-
| 13 [[Peripherals Summary#SPI|McSPI2]] | MMC2_DAT2 No | MMC2_DAT2 No | Transfer data between Omap and Wlan No | No McSPI3_CS1(mode=1)<br>  GPIO_134(mode=4) | No | No | <div align="JUSTIFY">'''Wlan: '''Protect Wlan if you don' use it. See MMC2_DAT7 pad.</div> <div align="JUSTIFY">'''Omap: '''protect Omap pad if you don't use it.'''(1)'''</div>No
|-
| 15 [[Peripherals Summary#SPI| MMC2_DAT1 | MMC2_DAT1 | Transfer data between Omap and Wlan | &nbsp;GPIO_133(mode=4) | <div align="JUSTIFY">'''Wlan: '''Protect Wlan if you don' use it. See MMC2_DAT7 pad.</div> <div align="JUSTIFY">'''Omap: '''protect Omap pad if you don't use it.'''(1)'''</div>|-| 17 | MMC2_DAT0 | MMC2_DAT0 | Transfer data between Omap and Wlan McSPI3]]
|
McSPI3_SOMIYes, not default configuration (mode=1[[Mux instructions#WIFI|disable WIFI]])
GPIO_132(mode=4) | No | No | No | No | No | <div align="JUSTIFY">'''Wlan: '''Protect Wlan if you don' use it. See MMC2_DAT7 pad.</div> <div align="JUSTIFY">'''Omap: '''protect Omap pad if you don't use it.'''Yes, not default configuration (1[[Mux_instructions#TFP410|disable DVI]])'''</divbr>
|-
| 19 [[Peripherals Summary#SPI| MMC2_CMD McSPI4]] | MMC2_CMD Yes, not default configuration ([[Mux instructions#GPIO_in_J990| Control Wire for bus MMC2 (Wlandisable GPIOs]]) | No McSPI3_SIMO(mode=1) | No | No GPIO_131(mode=4) | No | No | <div align="JUSTIFY">'''Wlan: '''Protect Wlan if you don' use it. See MMC2_DAT7 pad.</div> <div align="JUSTIFY">'''Omap: '''protect Omap pad if you don't use it.'''(1)'''</div>No
|-
| 21 [[Peripherals Summary#BSP| MMC2_CLK0 McBSP1]] | MMC2_CLK Yes, not default configuration ([[Mux instructions#GPIO_in_J990| Clock for MMC2 (Wlandisable GPIOs]]) | No McSPI3_CLK(mode=1) | No | No GPIO_130(mode=4) | No | No | <div align="JUSTIFY">'''Wlan: '''Protect Wlan if you don' use it. See MMC2_DAT7 pad.</div> <div align="JUSTIFY">'''Omap: '''protect Omap pad if you don't use it.'''(1)'''</div>No
|-
| 4 [[Peripherals Summary#BSP|McBSP2]] | MCBSP3_DX No | MCBSP3_DX No | Transmitted serial Data (Bluethoot audio) No | No UART2_CTS(mode=1)  GPIO_140(mode=4) | No | No | <div align="JUSTIFY">'''TPS65950:''' disable it via kernel '''(2) '''If you don't use it.</div>No
|-
| 6 [[Peripherals Summary#BSP| MCBSP3_CLKX McBSP3]] | MCBSP3_CLKX Yes, default configuration ([[Mux instructions#TP65950_PCM_VSP| Transmitted serial Clock (Bluethoot Bluetooth audio]]) | No UART2_TX(mode=1) | No | No GPIO_142(mode=4) | No | No | <div align="JUSTIFY">'''Bluethoot: '''Protect Bluethoot if you don' use it. See MMC2_DAT5 pad.</div> <div align="JUSTIFY"><br> </div> <div align="JUSTIFY">'''TPS65950:''' disable it via kernel '''(2) '''If you don't use it.</div>No
|-
| 8 [[Peripherals Summary#BSP|McBSP4]] | MCBSP3_FSX No | MCBSP3_FSX No | Transmited Frame Syncronisation (Bluethoot audio) No | No UART2_RX(mode=1) | No  GPIO_143| Yes, not default configuration (mode=4[[Mux instructions#GPIO_in_J990|disable GPIOs]])  | <div align="JUSTIFY">'''Bluethoot: '''Protect Bluethoot if you don' use it. See MMC2_DAT5 pad.</div> <div align="JUSTIFY"><br> </div> <div align="JUSTIFY">'''TPS65950:''' disable it via kernel '''(2) '''If you don't use it.</div>No
|-
| 10 [[Peripherals Summary#BSP|McBSP5]] | MCBSP3_DR No | MCBSP3_DR No | Received Serial Data (Bluethoot audio) No | No UART2_RTS(mode=1)  GPIO_141(mode=4) | No | No | <div align="JUSTIFY">'''TPS65950:''' disable it via kernel '''(2) '''If you don't use it.</div>No
|-
| 12 [[Peripherals Summary#MMC|MMC1]] | MCBSP1_DX No | MCBSP1_DX No | Transmited serial Data (not used) No | No McSPI4_SIMO(mode=1)  McBSP3_DX(mode=2)  GPIO_158(mode=4) | No | No | -<br>No
|-
| 14 [[Peripherals Summary#MMC| MCBSP1_CLKX MMC2]] | MCBSP1_CLKX Yes, default configuration ([[Mux instructions#WIFI| Transmited serial clock (not usedWIFI]]) | No McBSP3_CLKX(mode=2)<br> | No | No GPIO_162(mode=4) | No | No | -<br>No
|-
| 16 [[Peripherals Summary#MMC|MMC3]] | MCBSP1_FSX No | MCBSP1_FSX No | Transmited Frame Syncronization (not used) No | No McSPI4_CS0(mode=1)  McBSP3_FSX(mode=2)  GPIO_161(mode=4) | No | No | -<br>No
|-
| 18 [[Peripherals Summary#I2C| MCBSP1_DR I2C1]] | MCBSP1_DR No | Received Serial Data (not used) No | McSPI4_SOMI(mode=1)  McBSP3_DR(mode=2)  GPIO_159(mode=4)  | -<br>No |-No | 20 No | MCBSP1_CLKR | MCBSP1_CLKR | Received Clock (not used) | GPIO_156(mode=4)<br>  | -<br>|-| 22 | MCBSP1_FSR | MCBSP1_FSR | Received frame syncronization (not used) | GPIO_157(mode=4)<br> No | -<br>No
|-
| 23 [[Peripherals Summary#I2C|I2C2]] | I2C2_SDA Yes, default configuration | I2C2_SDA No | I2C Data No | No GPIO_183(mode=4)<br> | No, [[Connectors Summary#JC30_connector|via hardware]] | No | <div align="JUSTIFY">'''Cam connector:''' Check and RC14 is not welded or don't use it.<br></div>No
|-
| 24 [[Peripherals Summary#I2C|I2C3]] | I2C2_SCL No | I2C2_SCL No | I2C Clock No | No GPIO_168(mode=4)<br> | No | No | '''Cam connector:''' Check and RC13 is not welded or don't use it.Yes, default configuration (DVI)
|-
| 25 | REGEN | - | Master/Slave control power TPS65950<br> | - | -<br>|-| 26 | nRESET | - | Read Reset Omap | - | -<br>|-| 27 | GND | - | GND | - [[Peripherals Summary#I2C| -<br>I2C4]] |-No | 28 No | GND No | - No | GND No | - No | -<br>No
|}
'''(1):''' To protect Omap pads from external signals, configure Mux in mode=7 (safe_mode). With this mode, buffer is configured in high impedance == IGEP MODULE ===
'''(2):''' Disable TPS65950 go Next table pretends help you to file soundconfigure IGEP MODULE. First column shows some OMAP35xx/soc/codecs/twl4030DM37xx peripherals and first row shows all IGEP MODULE connectors. Read articles about connector and peripheral before use them. Each configuration can take different solutions.c change line 54 Code: <prebr>0x00There are some connectors than have more peripherals available, /* REG_VOICE_IF (0xF) */but they don't have all signals to use it. </prebr> to CodeTable shows four answers: <pre>0x04, /* REG_VOICE_IF (0xF) */</pre> === J960 connector ===&nbsp;
J960 connector can not use mux capabilities*"'''Yes, because default configuration(utility)'''": Peripheral enabled by default. "utility" shows if this connector peripheral is dedicated to use RS232 comunicationused. Default hardware/software <br> *"'''Yes, not default configuration is(information)'''":Peripheral don't enabled by default. Maybe you need to disable other one<span lang="en" id="result_box"br><span class=*"hps'''No, via hardware'''"></span></span>: Not available, but via hardware (placing or replacing some resistances) can be enabled.<br> *"'''No'''"
{| cellspacing="1" cellpadding="1" border="1" style="width: 498px933px; height: 381px190px;"|-| Pad | Connect to: | Default periphera: | Other peripheral: | Share with:<br> | Default function:<br>
|-
| 1
| -
| -
| -
| -<br>
| <br>
| [[Connectors Summary#J1_connector|J1]]
| [[Connectors Summary#J4_connector|J4]]
| [[Connectors Summary#J5_connector|J5]]
|-
| 2 | RS232_RX2 | UART3_RX | UART2_RX | -<br> | Kernel console params'''(4)'''<br>|-| 3 | RS232_TX2 | UART3_TX [[Peripherals Summary#UART| UART2_TX | -<br> | Kernel console params'''(4)'''<br>|-| 4 | - | - | - | -<br> | -<br>|-| 5 | GND | - | - | -<br> | -<br>|-| 6 | GND | - | - | -<br> | -<br>|-| 7 | - | - | - | -<br> | -<br>|-| 8 | RS232_TX1 | UART1_TX | UART3_TX | RS485 interface'''(5)'''<br> | -<br>|-| 9 | RS232_RX1 | UART1_RX | UART3_RX | RS485 interface'''(5)'''<br> | -<br>|-| 10 | - | - | - | -<br> | -<br>|} <br>  - Other peripherals can be configured via hardware, placing/replacing some resistances. See IGEPv2 Schematic for more information.  '''(4):''' To set other functionalities to UART3 (/dev/ttyS2) edit igep.ini file:  Search line: <pre>console=ttyS2,115200n8</pre> Replace by: <pre>; console=ttyS2,115200n8</pre> '''(5): '''Allows to use UART1 as RS232 instead of EI485, edit igep.ini:<br>  Search line: <pre>board.ei485=yes</pre> Replace by: <pre>board.ei485=no</pre> === J400 connector === J400 is used to JTAG (Joint Test Action Group). JTAG is a standardized serial protocol widely used in printed circuit boards. Its main functions are:<br>  -Debug the software of an embedded system directly <br>-Storing firmware<br> -Boundary scan testing  More information: [http://es.wikipedia.org/wiki/JTAG http://es.wikipedia.org/wiki/JTAG]. ]  Only Pad 13 and 14 have mux capabilities| Yes, for example you can use them like GPIO(mode=4). More information in IGEPv2 Schematic.<br>  === J970 connector === This connector don't have mux capabilities.  J970 is used to implement a keypad. It is controlled by TPS65950, this method avoid reduce Omap proces capabilities. TPS65950 send via I2C1 all the interrupt request. Their characteristics are:<br>  - Can handle up to 8 x 8 keypads, IGEPv2 can handle up to 4 x 4 keypads.<br>- Optionally, you can decode via Omap software.<br>- Event detection on key press and key release.<br>- Multikey press detection, can detect up 2&nbsp; keys at the same time.<br>- Long-key detection on prolonged key press.<br>- Programmable time-out on permanent key press or after keypad release.  More information in TPS65950 datasheets.<br>  === JC30 connector === JC30 is used to connect a camera for capture video or image. Omap have the processing capability to connect RAW image-sensor modules via this connector.  There are some peripherals than can be connected to JC30 like like CAM, SSI and CSI, but is not used in this how-to. GPIO are the default peripheral.<br>  Before use this connector be careful at these points:  - Pad 1 can be used to power down wifi module if RD41 is short circuit, replace RD42 for this porpouse.<br>- Pad 2 can be used to reset wifi module if RD43 is short circuit, replace RD44 for this porpouse.<br>- Pad 21 can be connected to I2C2_SCL, that wire is shared with J990 connector and I2C2_SCL peripheral. Placing/replacing RC13 for tis porpouse.<br>- Pad 22 can be connected to I2C2_SDA, that wire is shared with J990 connector and I2C2_SDA peripheral. Placing/replacing RC14 for tis porpouse.  === JA42 connector === JA42 is used for DVI configuration (Digital Video Interfacedisable DSS) control part, TouchScreen control and SPI1.<br>  -There are some peripherals than can be connected to JA42 like MM3| Yes, MM2, SSI, USB and HW_DBG, but is not used in this how-to.  Some pads have mux capabilities:  {| cellspacing="1" cellpadding="1" border="1" align="JUSTIFY" style="width: 804px; height: 343px;"|-| Pad: | Connect to: | Default peripheral (mode=0)  | Default function: | Other available peripherals: | style="text-align: left;" | Share with:|-| 1 | VIO 1V8 | - | Power 1v8 | - | -<br>|-| 2 | SYS_BOOT5 | SYS_BOOT5<br>  | Omap boot config | MMC2_DIR_DAT(mode=1)  GPIO_7 (mode=4)  | -<br>|-| 3 | DC_5V | - | Power 5v | - | <div align="JUSTIFY">-<br></div>|-| 4 | GND | - | GND | - | <div align="JUSTIFY"><br></div> <div align="JUSTIFY">-<br></div>|-| 5 | SYS_BOOT0 | SYS_BOOT0<br>  | Omap boot config | GPIO_2 (mode=4)  | <div align="JUSTIFY"><br> -<br> </div>|-| 6 | SYS_BOOT1 | SYS_BOOT1<br>  | Omap boot config<br> | GPIO_3 (mode=4)  | <div align="JUSTIFY">-<br></div> <div align="JUSTIFY"><br></div>|-| 7 | DVI_VSYNC | DSS_VSYNC default configuration | LCD&nbsp;vertical sync (Expansion)<br> | GPIO_68(mode=4)  | <div align="JUSTIFY"><br></div> <div align="JUSTIFY">TFP410 '''(6)'''<br></div>No
|-
| 8 [[Peripherals Summary#UART| DVI_HSYNC UART2]] | DSS_HSYNC | LCD Horitzontal sync Yes, not default configuration(Expansionenable: TX and RX) | GPIO_67 (mode=4)<br> No | <div align="JUSTIFY"><br></div> <div align="JUSTIFY"><div align="JUSTIFY">TFP410 '''(6)'''<br></div></div>No
|-
| 9 | DVI_ACBIAS [[Peripherals Summary#UART| DSS_ACBIAS UART3]] | LCD Control (Expansion) Yes, default configuration | &nbsp; GPIO_133(mode=4) No | <div align="JUSTIFY"><br></div> <div align="JUSTIFY"><div align="JUSTIFY">TFP410 '''(6)'''<br></div></div>No
|-
| 10 [[Peripherals Summary#UART| DVI_PUP UART4]] | - No | Control signal for DVI controler Yes, not default configuration(Expansiondisable: GPIO_64 and GPMC_WAIT3) | - | <div align="JUSTIFY"><br></div> <div align="JUSTIFY">TFP410 '''(6)'''</div>No
|-
| 11 [[Peripherals Summary#GPIO| DVI_PCLK GPIO]] | DSS_PCLK Yes, default configuration | LCD clock (Expansion) | GPIO_66 (mode=4)<br> Yes, default configuration | <div align="JUSTIFY"><br></div> <div align="JUSTIFY">TFP410 '''(6)'''</div>Yes, default configuration
|-
| 12 | TS_nPEN_IRQ [[Peripherals Summary#SPI| McSPI1_CS1 McSPI1]] | Touchscreen control (Expansion) No | MMC3_CMD(mode=3)  GPIO_175 (mode=4) Yes, default configuration | <div align="JUSTIFY">-<br></div> <div align="JUSTIFY"><br></div>No
|-
| 13 [[Peripherals Summary#SPI| LCD_QVGA/nVGA McSPI2]] | McBSP4_DX No | Touchscreen control (Expansion) | GPIO_154 (mode=4)<br> No | <div align="JUSTIFY">-<br></div>No
|-
| 14 | LCD_ENVDD [[Peripherals Summary#SPI| McBSP4_DR McSPI3]] | Touchscreen control Yes, not default configuration (Expansiondisable DSS) | GPIO_153 (mode=4)<br> No | -<br>No
|-
| 15 [[Peripherals Summary#SPI| LCD_RESB McSPI4]] | McBSP4_FSX No | Touchscreen control (Expansion) | GPIO_155 (mode=4)<br> No | <div align="JUSTIFY"><br></div> <div align="JUSTIFY">-<br> </div> <div align="JUSTIFY"><br></div>No
|-
| 16 [[Peripherals Summary#BSP| LCD_INI McBSP1]] | McBSP4_CLKX No | Touchscreen control (Expansion) | GPIO_152 (mode=4)<br> No | <div align="JUSTIFY">-<br></div>No
|-
| 17 [[Peripherals Summary#BSP| MCSPI1_CLK McBSP2]] | McSPI1_CLK<br> No | Touchscreen control (Expansion) | GPIO_171 (mode=4) No | -<br>No
|-
| 18 | MCSPI1_SIMO [[Peripherals Summary#BSP| McSPI1_SIMO McBSP3]] | Touchscreen control Yes, not default configuration (Expansiondisable UART2) | GPIO_172 (mode=4) No | -<br>No
|-
| 19 [[Peripherals Summary#BSP| MCSPI1_CS0 McBSP4]] | McSPI1_CS0 No | Touchscreen control Yes, not default configuration (Expansiondisable GPMCs) | GPIO_174 (mode=4)  | -<br>No
|-
| 20 [[Peripherals Summary#BSP| MCSPI1_SOMI McBSP5]] | McSPI1_SOMI No | Touchscreen control (Expansion) | GPIO_173 (mode=4)  | -<br>|} <br> '''(6):''' TFP410: Converts DVI&nbsp;signal to HDMI. They share the same video signal.<br>  === JA41 connector === JA41 is used for DVI Yes, not default configuration (Digital Video Interfacedisable GPIOs) data part.<br>  -There are some peripherals than can be connected to JA41 like DSSVENC, HW, DSS and SDI, but is not used in this how-to.  Some pads have mux capabilities:  {| cellspacing="1" cellpadding="1" border="1" align="JUSTIFY" style="width: 669px; height: 1064px;"No
|-
| Pad: | Connect to: [[Peripherals Summary#MMC| Default peripheral (mode=0) MMC1]] | Default function: No | Other available peripherals: No | style="text-align: left;" | Share with:No
|-
| 1 | VIO 3V3 [[Peripherals Summary#MMC| - MMC2]] | Power 3v3 No | - No | -<br>No
|-
| 2 [[Peripherals Summary#MMC| GND MMC3]] | -<br> No | GND | -<br> No | -<br>Yes, not default configuration (disable GPIOs)
|-
| 3 | DVI_DATA0 [[Peripherals Summary#I2C| &nbsp; DSS_D0 I2C1]] | LCD&nbsp;pixel data bit<br> No | UART1_CTS(mode=2)  GPIO_70(mode=4) No | TFP410 '''(6)'''No
|-
| 4 | DVI_DATA1 [[Peripherals Summary#I2C| &nbsp; DSS_D1 I2C2]] | LCD&nbsp;pixel data bit No | UART1_RTS(mode=2)  GPIO_71(mode=4) No | <div align="JUSTIFY"><br></div> <div align="JUSTIFY">TFP410 '''(6)'''</div>No
|-
| 5 [[Peripherals Summary#I2C| DVI_DATA2 I2C3]] | &nbsp;DSS_D2  | LCD&nbsp;pixel data bit | GPIO_72Yes, default configuration (mode=4J5) | No | TFP410 '''Yes, default configuration (6J1)'''
|-
| 6 | DVI_DATA3 | DSS_D3  | LCD&nbsp;pixel data bit | GPIO_73(mode=4)  | TFP410 '''(6)'''<div align="JUSTIFY"><br></div>|-| 7 | DVI_DATA4 | &nbsp;DSS_D4 | LCD&nbsp;pixel data bit | UART3_RX(mode=2)  GPIO_74(mode=4)  | <div align="JUSTIFY">TFP410 '''(6)'''</div> <div align="JUSTIFY"><br></div>|-| 8 | DVI_DATA5 | DSS_D5 | LCD&nbsp;pixel data bit | UART3_TX(mode=2)  GPIO_75(mode=4)<br>  | <div align="JUSTIFY">TFP410 '''(6)'''</div> <div align="JUSTIFY"><br></div>|-| 9 | DVI_DATA6 | DSS_D6 | LCD&nbsp;pixel data bit | &nbsp;UART1_TX(mode=2)  GPIO_76(mode=4)  | <div align="JUSTIFY">TFP410 '''(6)'''</div> <div align="JUSTIFY"><div align="JUSTIFY"><br></div></div>|-| 10 | DVI_DATA7 | DSS_D7 | LCD&nbsp;pixel data bit | &nbsp; UART1_RX(mode=2)  GPIO_77(mode=4)  | <div align="JUSTIFY"><br></div> <div align="JUSTIFY">TFP410 '''(6)'''</div>|-| 11 | DVI_DATA8 | DSS_D8 | LCD&nbsp;pixel data bit | GPIO_78(mode=4)<br>  | <div align="JUSTIFY"><br></div> <div align="JUSTIFY">TFP410 '''(6)'''</div>|-| 12 | DVI_DATA9 | DSS_D9 | LCD&nbsp;pixel data bit | GPIO_79(mode=4)  | <div align="JUSTIFY">TFP410 '''(6)'''</div> <div align="JUSTIFY"><br></div>|-| 13 | DVI_DATA10 | DSS_D10 | LCD&nbsp;pixel data bit | GPIO_80(mode=4)<br>  | <div align="JUSTIFY">TFP410 '''(6)'''</div>|-| 14 | DVI_DATA11 | DSS_D11 | LCD&nbsp;pixel data bit | GPIO_81(mode=4)<br>  | TFP410 '''(6)'''[[Peripherals Summary#I2C|-I2C4]] | 15 No | DVI_DATA12 | DSS_D12 | LCD&nbsp;pixel data bit | GPIO_82(mode=4)<br>  | <div align="JUSTIFY"><br></div> <div align="JUSTIFY">TFP410 '''(6)''' </div> <div align="JUSTIFY"><br></div>|-| 16 | DVI_DATA13 | DSS_D13 | LCD&nbsp;pixel data bit | GPIO_83(mode=4)<br>  | <div align="JUSTIFY">TFP410 '''(6)'''</div>|-| 17 | DVI_DATA14 | DSS_D14  | LCD&nbsp;pixel data bit | GPIO_84(mode=4)  | TFP410 '''(6)'''|-| 18 | DVI_DATA15 | DSS_D15 | LCD&nbsp;pixel data bit | GPIO_85(mode=4)  | TFP410 '''(6)'''|-| 19 | DVI_DATA16 | DSS_D16 | LCD&nbsp;pixel data bit | GPIO_86(mode=4)  | TFP410 '''(6)'''|-| 20 | DVI_DATA17 | DSS_D17 | LCD&nbsp;pixel data bit | GPIO_87(mode=4)  | TFP410 '''(6)'''|-| 21<br> | DVI_DATA18 | DSS_D18 | LCD&nbsp;pixel data bit | DSS_D0 (mode=3)  MCSPI3_CLK(mode=2)  GPIO_88(mode=4)  | TFP410 '''(6)'''|-| 22<br> | DVI_DATA19 | DSS_D19 | LCD&nbsp;pixel data bit | DSS_1 (mode=3)  MCSPI3_SIMO(mode=2)  GPIO_89(mode=4)  | TFP410 '''(6)'''|-| 23<br> | DVI_DATA20 | DSS_D20 | LCD&nbsp;pixel data bit | DSS_D2 (mode=3)  MCSPI3_SOMI(mode=2)  GPIO_90(mode=4)  | TFP410 '''(6)'''|-| 24<br> | DVI_DATA21 | DSS_D21 | LCD&nbsp;pixel data bit | DSS_3 (mode=3)  MCSPI3_CSO(mode=2)  GPIO_91(mode=4)  | TFP410 '''(6)'''|-| 25<br> | DVI_DATA22<br> | DSS_D22<br> | LCD&nbsp;pixel data bit | DSS_D4 (mode=3)  MCSPI3_CS1(mode=2)  GPIO_92(mode=4)  | TFP410 '''(6)'''|-| 26<br> | DVI_DATA23<br> | DSS_D23<br> | LCD&nbsp;pixel data bit | DSS_D5(mode=3)  GPIO_93(mode=4)  | TFP410 '''(6)'''|-| 27<br> | I2C3_SCL<br> | I2C3_SCL | I2C3 interface | GPIO_184(mode=4)  | TXS0102DCUR<br>|-| 28<br> | I2C3_SDA<br> | I2C3_SDA | I2C3 interface | GPIO_185(mode=4) No | TXS0102DCUR<br>No
|}
<br> '''(6)[[Category:''' TFP410Work_in_progress]][[Category: Converts DVI&nbsp;signal to HDMI. They share the same video signal.<br>  '''Under construction '''<br>Peripherals]]
Retrieved from "http://labs.isee.biz/index.php?title=Special:MobileDiff/3568...9928"