Open main menu

Changes

Mux configuration

9,627 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.
-&gt; INPUTENABLE = 0: Input Disable. Pin is configured in output only mode.  -&gt; INPUTENABLE = 1: Input Enable. Pin is configured in bidirectional mode.  • '''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]] 
|}
<br> === Mode selection ===
Multiplexing modes: 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. <br>
<br> 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> '''(more information)''' === Pull Selection ===
<br> The next table shows all capabilities.
IgepV2 Board have a default mux configuration, but some cases is necessary change it, for example your project need 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.  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> = Feedback and Contributing = At any point, if you see a mistake you can contribute to this How-To.  = Available peripherals on external connector = Before configure mux is necessary review some things:  - If connector is shared with other peripherals you should disable it via software or hardware.<br> - Don't use the same peripheral in more than one pad.<br> - Omap mux have 8 modes, somes modes are disable in some pads.  The next tables show you all the mux capabilities:  === J990 connector === -There are some peripherals than can be connected to J990 like mm3 and camera, but is not used in this how-to.  -High Speed USB 3 is only available on Omap 3530 in the next pads:  &nbsp;&nbsp;&nbsp;&nbsp; 3: HSUSB3_TLL_NXT<br> &nbsp;&nbsp;&nbsp;&nbsp; 4: HSUSB3_TLL_D4<br> &nbsp;&nbsp;&nbsp;&nbsp; 5: 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  <br>  {| cellspacing="1" cellpadding="1" border="1" align="JUSTIFY" style="width: 960px696px; height: 1463px1px;"
|-
| Pad: PULLTYPESELECT | Connect to: PULLUDENABLE | Default peripheral (mode=0)  | Default function: | Other available peripherals: | style="text-align: left;" | Share with:Pin Behavior
|-
| 1 0b0 | VIO 1V8 0b0 | Pull- | Power 1v8 | - | -<br>down selected but not activated
|-
| 2 0b0 | DC 5V 0b1 | Pull- | Power 5v | - | -<br>down selected and activated if pin is NOT configured as OUTPUT
|-
| 3 0b1 | MMC2_DAT7 0b0 | MMC2_DAT7 | Reset Wlan | MMC2_CLKIN(mode=1)  MMC3_DAT3(mode=3)  GPIO_139(mode=4)  | <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>Pull-up selected but not activated
|-
| 5 0b1 | MMC2_DAT6 0b1 | MMC2_DAT6 Pull-up selected and activated if pin is NOT configured as OUTPUT| Power down&nbsp; Wlan | MMC2_DIR_CMD(mode=1) }
MMC3_DAT2(When a pin is in output mode=3) , pulls are automatically disable.
GPIO_138(mode=4) == Input Enable ===
| <div alignINPUTENABLE ="JUSTIFY">'''Wlan0:''' This pad can power down Wlan peripheral using Omap GPIO low level (GND), power up removing GNDInput Disable. Also you can power down Wlan from J990 low level.</div> <div align="JUSTIFY">'''Omap: '''protect Omap pad if you don't use itPin is configured in output only mode.'''(1)'''</div>|-| 7 | MMC2_DAT5 | MMC2_DAT5 | Reset Bluethoot | MMC2_DIR_DAT1(mode=1)
MMC3_DAT1(INPUTENABLE = 1: Input Enable. Pin is configured in bidirectional mode=3) .<br>
GPIO_137(=== '''Off modevalues''' and '''Wake-up''' ===4)
| <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 mode is used to disable Bluethoot from J990 low levelsome pins and reduce power consumption.'''Omap: '''protect Omap pad if you don't use it.'''(1)'''<br> </div>|-| 9 | MMC2_DAT4 | MMC2_DAT4 | - | MMC_DIR_DAT0(mode=1)
MMC3_DAT0(mode=3) Please contribute.
GPIO136(mode=4) [http://www.ti.com/lit/ug/spruf98x/spruf98x.pdf More information] about mux.
| <div align="JUSTIFY">'''Wlan: '''Protect Wlan if you don' use it. See MMC2_DAT7 pad.</div> <div alignConfigure Mux ="JUSTIFY">'''Omap: '''protect Omap pad if you don't use it.'''(1)'''</div>|-| 11 | MMC2_DAT3 | MMC2_DAT3 | Transfer data between Omap and Wlan | McSPI3_CS0(mode=1)
GPIO_135(mode=4) 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:
*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| <div align="JUSTIFY">'''Wlan: '''Protect Wlan connectors summary]] for more information. *Some peripherals are only available if you don' use itplace or replace some resistances. See MMC2_DAT7 padschematics for more information.<br> *Some connectors share multiples peripherals like OMAP, WIFI/div> <div align="JUSTIFY">'''OmapBT combo, etc. You should disable unused peripherals to avoid interferences.&nbsp; For example: '''protect Omap pad if you don't want to control WIFI module via J990 disable OMAP or if you want use it[[How to set up UART2 in J990|UART2 at j990]] disable Bluetooth.'''(1)'''</div>See schematics of board or [[Connectors Summary|connectors summary]] or [[Mux_instructions#Disable_Peripherals|how-to disable peripherals]] or [[How_to_use_GPIOs| 13 | MMC2_DAT2 | MMC2_DAT2 | Transfer data between Omap and Wlan | McSPI3_CS1(mode=1)<br> how-to use gpios]] for more information.
GPIO_134(mode=4) == IGEPv2 ===
| <div align="JUSTIFY">'''Wlan: '''Protect Wlan if Next table pretends help you don' use itto configure IGEPv2. See MMC2_DAT7 pad.<First column shows some OMAP35xx/div> <div align="JUSTIFY">'''Omap: '''protect Omap pad if you don't use itDM37xx peripherals and first row shows all IGEPv2 connectors.'''(1)'''</div>|-| 15 | MMC2_DAT1 | MMC2_DAT1 | Transfer data between Omap Read articles about connector and Wlan | &nbsp;GPIO_133(mode=4) | <div align="JUSTIFY">'''Wlan: '''Protect Wlan if you don' peripheral before use itthem. See MMC2_DAT7 padEach configuration can take different solutions.</div> <div align="JUSTIFY"br>'''Omap: '''protect Omap pad if you There are some connectors than have more peripherals available, but they don't have all signals to use it.'''(1)'''</divbr>|-| 17 | MMC2_DAT0 | MMC2_DAT0 | Transfer data between Omap and Wlan | McSPI3_SOMI(mode=1) Table shows four answers:&nbsp;
GPIO_132*"'''Yes, default configuration(mode=4utility) '''": 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'''"
{| <div aligncellspacing="JUSTIFY1" cellpadding="1">'''Wlan: '''Protect Wlan if you don' use it. See MMC2_DAT7 pad.</div> <div alignborder="JUSTIFY1" style=">'''Omapwidth: 933px; height: '''protect Omap pad if you don't use it.'''(1)'''</div>409px;"
|-
| 19 <br> | MMC2_CMD [[Connectors Summary#J990_connector|J990]] | MMC2_CMD [[Connectors Summary#J960_connector|J960]] | Control Wire for bus MMC2 (Wlan) [[Connectors Summary#J970_connector|J970]] | [[Connectors Summary#J400_connector|J400]] McSPI3_SIMO(mode=1)  GPIO_131(mode=4) | [[Connectors Summary#JC30_connector|JC30]] | [[Connectors Summary#JA42_connector|JA42]] | <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>[[Connectors Summary#JA41_connector|JA41]]
|-
| 21 [[Peripherals Summary#UART| MMC2_CLK0 UART1]] | MMC2_CLK No | Clock for MMC2 Yes, not default configuration (Wlan[[Mux instructions#UART1_in_J960|disable RS485]]) | No McSPI3_CLK(mode=1) | No | No GPIO_130(mode=4) | 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]])'''</div>
|-
| 4 [[Peripherals Summary#UART| MCBSP3_DX UART2]] | MCBSP3_DX Yes, not default configuration ([[How to set up UART2 in J990| Transmitted serial Data (Bluethoot audiodisable Bluetooth]])
|
UART2_CTS(mode=1) No, [[How to use UARTs#RS232_Schematic_Igep_V2|via hardware]],
GPIO_140(mode=4) [[Mux instructions#Bluetooth|disable Bluetooth]]
| <div align="JUSTIFY">'''TPS65950:''' disable it via kernel '''(2) '''If you don't use it.</div>No | No | No | No | No
|-
| 6 [[Peripherals Summary#UART| MCBSP3_CLKX UART3]] | MCBSP3_CLKX No | Transmitted serial Clock Yes, default configuration (Bluethoot audio[[Mux instructions#UART3_in_J960|Serial debug]]) | No UART2_TX(mode=1) | No | No GPIO_142| No | Yes, not default configuration (mode=4)  [[Mux_instructions#TFP410| <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 '''(2DVI]]) '''If you don't use it.</div>
|-
| 8 [[Peripherals Summary#UART|UART4]] | MCBSP3_FSX No | MCBSP3_FSX No | Transmited Frame Syncronisation (Bluethoot audio) No | No UART2_RX(mode=1)  GPIO_143(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
|-
| 10 [[Peripherals Summary#GPIO| MCBSP3_DR | MCBSP3_DR | Received Serial Data (Bluethoot audio) GPIO]]
|
UART2_RTSYes, default configuration (mode=1[[Mux instructions#GPIO_in_J990|info]])
GPIO_141| No | No | Yes, not default configuration (mode=4[[Mux instructions#GPIO_in_J990|disable JTAG]]) | Yes, default configuration | Yes, default configuration | <div align="JUSTIFY">'''TPS65950:''' Yes, not default configuration ([[Mux_instructions#TFP410|disable it via kernel '''(2DVI]]) '''If you don't use it.</div>
|-
| 12 [[Peripherals Summary#SPI|McSPI1]] | 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 | Yes, default configuration | -<br>No
|-
| 14 [[Peripherals Summary#SPI|McSPI2]] | MCBSP1_CLKX No | MCBSP1_CLKX No | Transmited serial clock (not used) No | No McBSP3_CLKX(mode=2)<br>  GPIO_162(mode=4) | No | No | -<br>No
|-
| 16 [[Peripherals Summary#SPI| MCBSP1_FSX | MCBSP1_FSX | Transmited Frame Syncronization (not used) McSPI3]]
|
McSPI4_CS0Yes, not default configuration (mode=1)  McBSP3_FSX(mode=2)  GPIO_161(mode=4[[Mux instructions#WIFI|disable WIFI]])
| -No | No | No | No | No | Yes, not default configuration ([[Mux_instructions#TFP410|disable DVI]])<br>
|-
| 18 [[Peripherals Summary#SPI| MCBSP1_DR McSPI4]] | MCBSP1_DR Yes, not default configuration ([[Mux instructions#GPIO_in_J990| Received Serial Data (not useddisable GPIOs]]) | No McSPI4_SOMI(mode=1) | No | No McBSP3_DR(mode=2)  GPIO_159(mode=4) | No | No | -<br>No
|-
| 20 [[Peripherals Summary#BSP| MCBSP1_CLKR McBSP1]] | MCBSP1_CLKR | Received Clock (Yes, not used) | GPIO_156default configuration (mode=4)<br>  | -<br>|-| 22 | MCBSP1_FSR | MCBSP1_FSR | Received frame syncronization (not used) | GPIO_157(mode=4)<br>  | -<br>|-| 23 | I2C2_SDA | I2C2_SDA | I2C Data | GPIO_183(mode=4)<br>  | <div align="JUSTIFY">'''Cam connector:''' Check and RC14 is not welded or don't use it.<br></div>|-| 24 | I2C2_SCL | I2C2_SCL [[Mux instructions#GPIO_in_J990| I2C Clock | GPIO_168(mode=4disable GPIOs]])<br>  | '''Cam connector:''' Check and RC13 is not welded or don't use it.|-| 25 | REGEN | - | Master/Slave control power TPS65950<br> | - | -<br>|-| 26 | nRESET | - | Read Reset Omap | - | -<br>|-| 27 | GND | - | GND | - | -<br>|-| 28 | GND | - 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  '''(2):''' Disable TPS65950 go to file sound/soc/codecs/twl4030.c change line 54 Code: <pre>0x00, /* REG_VOICE_IF (0xF) */</pre> to Code: <pre>0x04, /* REG_VOICE_IF (0xF) */</pre> === J960 connector === J960 connector can not use mux capabilities, because this connector is dedicated to use RS232 comunication. Default hardware/software configuration is:<span lang="en" id="result_box"><span class="hps"></span></span><br> No {| cellspacing="1" cellpadding="1" border="1" style="width: 498px; height: 381px;"No
|-
| Pad [[Peripherals Summary#BSP|McBSP2]] | No | No | Connect to: No | Default periphera: No | Other peripheral: No | Share with:<br> No | Default function:<br>No
|-
| 1 [[Peripherals Summary#BSP|McBSP3]] | Yes, default configuration ([[Mux instructions#TP65950_PCM_VSP|Bluetooth audio]]) | No | - No | - No | - No | -<br> No | <br>No
|-
| 2 [[Peripherals Summary#BSP|McBSP4]] | No | RS232_RX2 No | UART3_RX No | UART2_RX No | -<br> No | Kernel console params'''Yes, not default configuration (4[[Mux instructions#GPIO_in_J990|disable GPIOs]])'''<br>| No
|-
| 3 [[Peripherals Summary#BSP|McBSP5]] | No | No | RS232_TX2 No | UART3_TX No | UART2_TX No | -<br> No | Kernel console params'''(4)'''<br>No
|-
| 4 [[Peripherals Summary#MMC|MMC1]] | No | No | - No | - No | - No | -<br> No | -<br>No
|-
| 5 [[Peripherals Summary#MMC|MMC2]] | Yes, default configuration ([[Mux instructions#WIFI|WIFI]]) | No | GND No | - No | - No | -<br> No | -<br>No
|-
| 6 [[Peripherals Summary#MMC|MMC3]] | No | No | GND No | - No | - No | -<br> No | -<br>No
|-
| 7 [[Peripherals Summary#I2C|I2C1]] | No | No | - No | - No | - No | -<br> No | -<br>No
|-
| 8 [[Peripherals Summary#I2C|I2C2]] | Yes, default configuration | No | RS232_TX1 No | UART1_TX No | UART3_TX No, [[Connectors Summary#JC30_connector|via hardware]] | RS485 interface'''(5)'''<br> No | -<br>No
|-
| 9 [[Peripherals Summary#I2C|I2C3]] | RS232_RX1 No | UART1_RX No | UART3_RX No | RS485 interface'''No | No | No | Yes, default configuration (5DVI)'''<br> | -<br>
|-
| 10 [[Peripherals Summary#I2C|I2C4]] | No | No | - No | - No | - No | -<br> No | -<br>No
|}
<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, for example you can use them like GPIO(mode=4). More information in IGEPv2 Schematic.<br> === J970 connector IGEP MODULE === 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 Next table pretends help you to 8 x 8 keypads, IGEPv2 configure IGEP MODULE. First column shows some OMAP35xx/DM37xx peripherals and first row shows all IGEP MODULE connectors. Read articles about connector and peripheral before use them. Each configuration can handle up to 4 x 4 keypadstake different solutions.<br>- OptionallyThere are some connectors than have more peripherals available, you can decode via Omap softwarebut they don't have all signals to use it.<br>- Event detection on key press and key release.<br>- Multikey press detection, can detect up 2Table shows four answers:&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 *"'''Yes, default configuration(utility)'''": Peripheral enabled by default. "utility" shows if this peripheral is used.<br> *"'''Yes, not default configuration(information in TPS65950 datasheets)'''": 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'''"
=== 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 (Digital Video Interface) control part, TouchScreen control and SPI1.<br>  -There are some peripherals than can be connected to JA42 like MM3, 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: 804px933px; height: 343px190px;"
|-
| Pad: <br>| Connect to: [[Connectors Summary#J1_connector| Default peripheral (mode=0) J1]] | Default function: [[Connectors Summary#J4_connector| Other available peripherals: J4]] | style="text-align: left;" [[Connectors Summary#J5_connector| Share with:J5]]
|-
| 1 | VIO 1V8 [[Peripherals Summary#UART| - UART1]] | Power 1v8 Yes, not default configuration (disable DSS) | - Yes, default configuration | -<br>No
|-
| 2 [[Peripherals Summary#UART| SYS_BOOT5 UART2]] | SYS_BOOT5<br>  | Omap boot config | MMC2_DIR_DATYes, not default configuration(mode=1)  GPIO_7 (mode=4enable: TX and RX) | No | -<br>No
|-
| 3 | DC_5V [[Peripherals Summary#UART| - UART3]] | Power 5v Yes, default configuration | - No | <div align="JUSTIFY">-<br></div>No
|-
| 4 | GND [[Peripherals Summary#UART| - UART4]] | GND No | - Yes, not default configuration(disable: GPIO_64 and GPMC_WAIT3) | <div align="JUSTIFY"><br></div> <div align="JUSTIFY">-<br></div>No
|-
| 5 [[Peripherals Summary#GPIO| SYS_BOOT0 GPIO]] | SYS_BOOT0<br> Yes, default configuration | Omap boot config Yes, default configuration | GPIO_2 (mode=4)  | <div align="JUSTIFY"><br> -<br> </div>Yes, default configuration
|-
| 6 [[Peripherals Summary#SPI| SYS_BOOT1 McSPI1]] | SYS_BOOT1<br> No | Omap boot config<br> | GPIO_3 (mode=4) Yes, default configuration | <div align="JUSTIFY">-<br></div> <div align="JUSTIFY"><br></div>No
|-
| 7 [[Peripherals Summary#SPI| DVI_VSYNC McSPI2]] | DSS_VSYNC No | LCD&nbsp;vertical sync (Expansion)<br> | GPIO_68(mode=4) No | <div align="JUSTIFY"><br></div> <div align="JUSTIFY">TFP410 '''(6)'''<br></div>No
|-
| 8 [[Peripherals Summary#SPI| DVI_HSYNC McSPI3]] | DSS_HSYNC | LCD Horitzontal sync Yes, not default configuration (Expansiondisable DSS) | 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#SPI| DSS_ACBIAS McSPI4]] | LCD Control (Expansion) No | &nbsp; GPIO_133(mode=4) No | <div align="JUSTIFY"><br></div> <div align="JUSTIFY"><div align="JUSTIFY">TFP410 '''(6)'''<br></div></div>No
|-
| 10 | DVI_PUP [[Peripherals Summary#BSP| - McBSP1]] | Control signal for DVI controler (Expansion) No | - No | <div align="JUSTIFY"><br></div> <div align="JUSTIFY">TFP410 '''(6)'''</div>No
|-
| 11 [[Peripherals Summary#BSP| DVI_PCLK McBSP2]] | DSS_PCLK No | LCD clock (Expansion) | GPIO_66 (mode=4)<br> No | <div align="JUSTIFY"><br></div> <div align="JUSTIFY">TFP410 '''(6)'''</div>No
|-
| 12 | TS_nPEN_IRQ | McSPI1_CS1 | Touchscreen control (Expansion) | MMC3_CMD(mode=3)  GPIO_175 (mode=4)  | <div align="JUSTIFY">-<br></div> <div align="JUSTIFY"><br></div>|-| 13 | LCD_QVGA/nVGA | McBSP4_DX | Touchscreen control (Expansion) | GPIO_154 (mode=4)<br>  | <div align="JUSTIFY">-<br></div>|-| 14 | LCD_ENVDD | McBSP4_DR | Touchscreen control (Expansion) | GPIO_153 (mode=4)<br>  | -<br>|-| 15 | LCD_RESB | McBSP4_FSX | Touchscreen control (Expansion) | GPIO_155 (mode=4)<br>  | <div align="JUSTIFY"><br></div> <div align="JUSTIFY">-<br> </div> <div align="JUSTIFY"><br></div>|-| 16 | LCD_INI | McBSP4_CLKX | Touchscreen control (Expansion) | GPIO_152 (mode=4)<br>  | <div align="JUSTIFY">-<br></div>|-| 17 | MCSPI1_CLK | McSPI1_CLK<br>  | Touchscreen control (Expansion) | GPIO_171 (mode=4)  | -<br>|-| 18 | MCSPI1_SIMO | McSPI1_SIMO | Touchscreen control (Expansion) | GPIO_172 (mode=4)  | -<br>|-| 19 | MCSPI1_CS0 | McSPI1_CS0 | Touchscreen control (Expansion) | GPIO_174 (mode=4)  | -<br>|-| 20 | MCSPI1_SOMI [[Peripherals Summary#BSP| McSPI1_SOMI | Touchscreen control (Expansion) McBSP3]] | 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 (Digital Video Interface) data part.<br>  -There are some peripherals than can be connected to JA41 like DSSVENCYes, 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;"|-| Pad: | Connect to: | Default peripheral default configuration (mode=0disable UART2)  | Default function: | Other available peripherals: | style="text-align: left;" | Share with:|-No | 1 | VIO 3V3 | - | Power 3v3 | - | -<br>|-| 2 | GND | -<br>  | GND | -<br>  | -<br>|-| 3 | DVI_DATA0 | &nbsp; DSS_D0 | LCD&nbsp;pixel data bit<br> | UART1_CTS(mode=2)  GPIO_70(mode=4)  | TFP410 '''(6)'''|-| 4 | DVI_DATA1 | &nbsp; DSS_D1 | LCD&nbsp;pixel data bit | UART1_RTS(mode=2)  GPIO_71(mode=4)  | <div align="JUSTIFY"><br></div> <div align="JUSTIFY">TFP410 '''(6)'''</div>|-| 5 | DVI_DATA2 | &nbsp;DSS_D2  | LCD&nbsp;pixel data bit | GPIO_72(mode=4)  | TFP410 '''(6)'''|-| 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)'''|-| 15 | 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)'''No
|-
| 19 | DVI_DATA16 [[Peripherals Summary#BSP| DSS_D16 McBSP4]] | LCD&nbsp;pixel data bit No | GPIO_86Yes, not default configuration (mode=4disable GPMCs)  | TFP410 '''(6)'''No
|-
| 20 | DVI_DATA17 [[Peripherals Summary#BSP| DSS_D17 McBSP5]] | LCD&nbsp;pixel data bit No | GPIO_87Yes, not default configuration (mode=4disable GPIOs)  | TFP410 '''(6)'''No
|-
| 21<br> [[Peripherals Summary#MMC| DVI_DATA18 MMC1]] | DSS_D18 No | LCD&nbsp;pixel data bit | DSS_D0 (mode=3)  MCSPI3_CLK(mode=2)  GPIO_88(mode=4) No | TFP410 '''(6)'''No
|-
| 22<br> | DVI_DATA19 [[Peripherals Summary#MMC| DSS_D19 MMC2]] | LCD&nbsp;pixel data bit No | 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) No | TFP410 '''(6)'''No
|-
| 24<br> | DVI_DATA21 [[Peripherals Summary#MMC| DSS_D21 MMC3]] | LCD&nbsp;pixel data bit No | DSS_3 (mode=3)  MCSPI3_CSO(mode=2)  GPIO_91(mode=4) No | TFP410 '''Yes, not default configuration (6disable GPIOs)'''
|-
| 25<br> [[Peripherals Summary#I2C| DVI_DATA22<br> I2C1]] | DSS_D22<br> No | LCD&nbsp;pixel data bit | DSS_D4 (mode=3)  MCSPI3_CS1(mode=2)  GPIO_92(mode=4) No | TFP410 '''(6)'''No
|-
| 26<br> | DVI_DATA23<br> [[Peripherals Summary#I2C| DSS_D23<br> I2C2]] | LCD&nbsp;pixel data bit No | DSS_D5(mode=3)  GPIO_93(mode=4) No | TFP410 '''(6)'''No
|-
| 27<br> [[Peripherals Summary#I2C| I2C3_SCL<br> I2C3]] | I2C3_SCL Yes, default configuration (J5) | I2C3 interface No | GPIO_184Yes, default configuration (mode=4J1)  | TXS0102DCUR<br>
|-
| 28<br> [[Peripherals Summary#I2C| I2C3_SDA<br> I2C4]] | I2C3_SDA No | 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/3552...9928"