Changes

Mux configuration

7,735 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.
The functional bits of a pad configuration register field are divided into the following five fields:
- • '''MUXMODE ''' (3 bits) defines the multiplexing mode applied to the pin. A mode corresponds to the selection of the functionality mapped on the pin with six (0 to 5) possible functional modes for each pin.
- • '''PULL ''' (2 bits) for combinational pullup/pulldown configuration:
-&gt; PULLTYPESELECT: Pullup/pulldown selection for the pin.
-&gt; PULLUDENABLE: Pullup/pulldown enable for the pin.
- • '''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. - 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:->OFFENABLE: Off mode pin state override control. Set to 1 to enable the feature and to 0 to disable it.->OFFOUTENABLE: Off mode output enable value. Set to 0 to enable the feature and to 1 to disable it.->OFFOUTVALUE: Off mode output value.->OFFPULLUDENABLE: Off mode pullup/pulldown enable->OFFPULLTYPESELECT: Off mode pullup/pulldown selection <br> <br> <br> '''(more information)'''  <br>  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 =• '''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:
Before configure mux is necessary review some things-&gt;OFFENABLE: Off mode pin state override control. Set to 1 to enable the feature and to 0 to disable it.
- If connector is shared with other peripherals you should disable it via software or hardware&gt;OFFOUTENABLE: Off mode output enable value.<br> - Don't use Set to 0 to enable the same peripheral in more than one pad.<br> - Omap mux have 8 modes, somes modes are feature and to 1 to disable in some padsit.
The next tables show you all the mux capabilities-&gt;OFFOUTVALUE: Off mode output value.
=== J990 connector ===-&gt;OFFPULLUDENABLE: Off mode pullup/pulldown enable.
-There are some peripherals than can be connected to J990 like mm3 and camera, but is not used in this how-to&gt;OFFPULLTYPESELECT: Off mode pullup/pulldown selection.
• '''Wake-High Speed USB 3 is only available on Omap 3530 in the next padsup''' bits (2 bits):
-&nbspgt;&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; 10WAKEUPENABLE: HSUSB3_TLL_D5 Enable wake-up detection on input. It is also the off mode input enable value.
-&gt;WAKEUPEVENT: Wake-up event status for the pin.'''<br> '''
{| cellspacing="1" cellpadding="1" border="1" align="JUSTIFYcenter" stylewidth="width: 960px; height: 1463px;200"
|-
| Pad:
| Connect to:
|
Default peripheral (mode=0) [[Image:Mux pad configuration diagram.png]]
| Default function: | Other available peripherals: | style="text-align: left;" | Share with:|-| 1 | VIO 1V8 | - | Power 1v8 | - | -<br>|-| 2 | DC 5V | - | Power 5v | - | -<br>|-| 3 | MMC2_DAT7 | MMC2_DAT7 | Reset Wlan | MMC2_CLKIN(mode=1) }
MMC3_DAT3(mode=3) == Mode selection ===
GPIO_139(mode=4) The next table shows all capabilities.<br>
{| <div aligncellspacing="JUSTIFY1" cellpadding="1">'''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 alignborder="JUSTIFY1" style=">'''Omapwidth: 287px; height: '''protect Omap pad if you don't use it.'''(1)'''</div>235px;"
|-
| 5 MUXMODE | MMC2_DAT6 | MMC2_DAT6 | Power down&nbsp; Wlan | MMC2_DIR_CMD(mode=1)  MMC3_DAT2(mode=3)  GPIO_138(mode=4)  | <div align="JUSTIFY">'''Wlan:''' This pad can power down Wlan peripheral using Omap GPIO low level (GND), 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.'''(1)'''</div>Select Mode
|-
| 7 | MMC2_DAT5 | MMC2_DAT5 | Reset Bluethoot 0b000=0 | MMC2_DIR_DAT1(mode=1)  MMC3_DAT1Mode 0 (Primary mode=3)  GPIO_137(mode=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 disable Bluethoot from J990 low level.'''Omap: '''protect Omap pad if you don't use it.'''(1)'''<br> </div>
|-
| 9 0b001=1 | MMC2_DAT4 | MMC2_DAT4 | - | MMC_DIR_DAT0(mode=Mode 1)  MMC3_DAT0(Possible mode=3)  GPIO136(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)'''</divbr>
|-
| 11 | MMC2_DAT3 | MMC2_DAT3 0b010=2 | Transfer data between Omap and Wlan | McSPI3_CS0(mode=1)  GPIO_135Mode 2 (Possible 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>
|-
| 13 | MMC2_DAT2 | MMC2_DAT2 0b011=3 | Transfer data between Omap and Wlan | McSPI3_CS1(mode=1)<br>  GPIO_134Mode 3 (Possible 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>
|-
| 15 | MMC2_DAT1 | MMC2_DAT1 | Transfer data between Omap and Wlan | &nbsp;GPIO_133(mode0b100=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.'''Mode 4 (1Possible mode)'''</div>
|-
| 17 | MMC2_DAT0 | MMC2_DAT0 0b101=5 | Transfer data between Omap and Wlan | McSPI3_SOMI(mode=1)  GPIO_132Mode 5 (Possible 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>
|-
| 19 | MMC2_CMD | MMC2_CMD | Control Wire for bus MMC2 (Wlan) 0b110=6 | McSPI3_SIMO(mode=1)  GPIO_131Mode 6 (Possible 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>
|-
| 21 | MMC2_CLK0 | MMC2_CLK | Clock for MMC2 (Wlan) | McSPI3_CLK(mode=1)  GPIO_130(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>|-| 4 | MCBSP3_DX | MCBSP3_DX | Transmitted serial Data (Bluethoot audio) | UART2_CTS(mode0b111=1)  GPIO_140(mode=4) 7 | <div align="JUSTIFY">'''TPS65950:''' disable it via kernel '''Mode 7 (2Safe Mode) '''If you don't use it.</div>|-| 6 | MCBSP3_CLKX | MCBSP3_CLKX | Transmitted serial Clock (Bluethoot audio) | UART2_TX(mode=1)  GPIO_142(mode=4)  | <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>|-| 8 | MCBSP3_FSX | MCBSP3_FSX | Transmited Frame Syncronisation (Bluethoot audio) | UART2_RX(mode=1)  GPIO_143(mode=4)  | <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>|-| 10 | MCBSP3_DR | MCBSP3_DR | Received Serial Data (Bluethoot audio) | UART2_RTS(mode=1) }
GPIO_141(mode=4) '''Definitions:'''
| <div align="JUSTIFY">'''TPS65950:Mode 0''' disable it via kernel '''(2) '''If you 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 itprimary mode by default.</div>|-| 12 | MCBSP1_DX | MCBSP1_DX | Transmited serial Data (not used) | McSPI4_SIMO(mode=1)
McBSP3_DX('''Mode 1 to mode=2) 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.
GPIO_158'''The safe mode (default mode=47) '''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>|-| 14 | MCBSP1_CLKX | MCBSP1_CLKX | Transmited serial clock (not used) | McBSP3_CLKX(mode=2)<br> == Pull Selection ===
GPIO_162(mode=4) The next table shows all capabilities.
{| -<br>cellspacing="1" cellpadding="1" border="1" style="width: 696px; height: 1px;"
|-
| 16 PULLTYPESELECT | MCBSP1_FSX PULLUDENABLE | MCBSP1_FSX | Transmited Frame Syncronization (not used) | McSPI4_CS0(mode=1)  McBSP3_FSX(mode=2)  GPIO_161(mode=4)  | -<br>Pin Behavior
|-
| 18 0b0 | MCBSP1_DR 0b0 | MCBSP1_DR | Received Serial Data (Pull-down selected but not used) | McSPI4_SOMI(mode=1)  McBSP3_DR(mode=2)  GPIO_159(mode=4)  | -<br>activated
|-
| 20 0b0 | MCBSP1_CLKR | MCBSP1_CLKR | Received Clock (not used) | GPIO_156(mode=4)<br> 0b1 | Pull-<br>down selected and activated if pin is NOT configured as OUTPUT
|-
| 22 0b1 | 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>0b0 |Pull-| 24 | I2C2_SCL | I2C2_SCL | I2C Clock | GPIO_168(mode=4)<br>  | '''Cam connector:''' Check and RC13 is up selected but not welded or don't use it.activated
|-
| 25 0b1 | REGEN 0b1 | Pull- | Master/Slave control power TPS65950<br> | - | -<br>|-| 26 | nRESET | - | Read Reset Omap | - | -<br>|-| 27 | GND | - | GND | - | -<br>|-| 28 | GND | - | GND | - | -<br>up selected and activated if pin is NOT configured as OUTPUT
|}
'''(1):''' To protect Omap pads from external signals, configure Mux When a pin is in output mode=7 (safe_mode), pulls are automatically disable. 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>=== Input Enable ===
INPUTENABLE === J960 connector ===0: Input Disable. Pin is configured in output only mode.
J960 connector can not use mux capabilities, because this connector INPUTENABLE = 1: Input Enable. Pin is dedicated to use RS232 comunicationconfigured in bidirectional mode. Default hardware/software configuration is:<span lang="en" id="result_box"><span class="hps"></span></span><br>
{| cellspacing="1" cellpadding="1" border="1" style="width: 498px; height: 381px;"|-| Pad | Connect to: | Default periphera: | Other peripheral: | Share with:<br> | Default function:<br>|-| 1 | - | - | - | -<br> | <br>|-| 2 | RS232_RX2 | UART3_RX | UART2_RX | -<br> | Kernel console params'''(4)Off mode values'''<br>|-| 3 | RS232_TX2 | UART3_TX | UART2_TX | -<br> | Kernel console params'''(4)and '''<br>|Wake-| 4 | - | - | - | -<br> | -<br>|-| 5 | GND | - | - | -<br> | -<br>|-| 6 | GND | - | - | -<br> | -<br>|-| 7 | - | - | - | -<br> | -<br>|-| 8 | RS232_TX1 | UART1_TX | UART3_TX | RS485 interface'''(5)up'''<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, 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 datasheetsThis mode is used to disable some pins and reduce power consumption.<br>
=== JC30 connector ===Please contribute.
JC30 is used to connect a camera for capture video or image[http://www. Omap have the processing capability to connect RAW image-sensor modules via this connectorti.com/lit/ug/spruf98x/spruf98x.pdf More information] about mux.
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> = Configure Mux =
Mux options are vast, at the beginning can be difficult and tedious change some configurations. Before configure mux, use this connector be careful at these pointsthe following tips to avoid problems:
- Pad 1 *Mux can be used to power down wifi module if RD41 is short circuitconnect multiple connectors at the same peripheral, replace RD42 for this porpouseimproper use can damage the processor.<br>- Pad 2 can be Before configure mux, revise that this peripheral is not used to reset wifi module in other pads. See schematics or [[Connectors Summary|connectors summary]] for more information. *Some peripherals are only available if RD43 is short circuit, you place or replace RD44 some resistances. See schematics for this porpousemore information.<br>- Pad 21 can be connected to I2C2_SCL*Some connectors share multiples peripherals like OMAP, WIFI/BT combo, that wire is shared with J990 connector and I2C2_SCL peripheraletc. Placing/replacing RC13 for tis porpouseYou should disable unused peripherals to avoid interferences.<br>- Pad 22 can be connected &nbsp; For example: if you want to control WIFI module via J990 disable OMAP or if you want use [[How to I2C2_SDA, that wire is shared with set up UART2 in J990 connector and I2C2_SDA peripheral|UART2 at j990]] disable Bluetooth. Placing/replacing RC14 See schematics of board or [[Connectors Summary|connectors summary]] or [[Mux_instructions#Disable_Peripherals|how-to disable peripherals]] or [[How_to_use_GPIOs|how-to use gpios]] for tis porpousemore information.
=== JA42 connector IGEPv2 ===
JA42 is used for DVI (Digital Video Interface) control partNext 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> There are some connectors than have more peripherals available, TouchScreen control and SPI1but they don't have all signals to use it.<br> Table shows four answers:&nbsp;
-There are some peripherals than can be connected to JA42 like MM3*"'''Yes, MM2default configuration(utility)'''": Peripheral enabled by default. "utility" shows if this peripheral is used.<br> *"'''Yes, SSInot default configuration(information)'''": Peripheral don't enabled by default. Maybe you need to disable other one<br> *"'''No, USB and HW_DBGvia hardware'''": Not available, but is not used in this how-tovia hardware (placing or replacing some resistances) can be enabled. <br> *"'''No'''"
Some pads have mux capabilities:  {| cellspacing="1" cellpadding="1" border="1" align="JUSTIFY" style="width: 804px933px; height: 343px409px;"
|-
| 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 [[Peripherals Summary#UART| SYS_BOOT5 UART2]] | SYS_BOOT5<br>  Yes, not default configuration ([[How to set up UART2 in J990| Omap boot config disable Bluetooth]])
|
MMC2_DIR_DAT(mode=1) No, [[How to use UARTs#RS232_Schematic_Igep_V2|via hardware]],
GPIO_7 (mode=4) [[Mux instructions#Bluetooth|disable Bluetooth]]
| -<br>No | No | No | No | No
|-
| 3 [[Peripherals Summary#UART|UART3]] | No | DC_5V Yes, default configuration ([[Mux instructions#UART3_in_J960|Serial debug]]) | - No | Power 5v No | - No | <div align="JUSTIFY">-<br></div>No | Yes, not default configuration ([[Mux_instructions#TFP410|disable DVI]])
|-
| 4 [[Peripherals Summary#UART|UART4]] | No | No | GND No | - No | GND No | - No | <div align="JUSTIFY"><br></div> <div align="JUSTIFY">-<br></div>No
|-
| 5 [[Peripherals Summary#GPIO| SYS_BOOT0 GPIO]]
|
SYS_BOOT0<br> Yes, default configuration ([[Mux instructions#GPIO_in_J990|info]])
| Omap boot config No | No GPIO_2 | Yes, not default configuration (mode=4[[Mux instructions#GPIO_in_J990|disable JTAG]]) | Yes, default configuration | <div align="JUSTIFY"><br> Yes, default configuration | Yes, not default configuration ([[Mux_instructions#TFP410|disable DVI]])|-<br> </div>| [[Peripherals Summary#SPI|McSPI1]] | No | No | No | No | No | Yes, default configuration | No
|-
| 6 [[Peripherals Summary#SPI|McSPI2]] | SYS_BOOT1 No | No SYS_BOOT1<br> | No | No | Omap boot config<br> No | GPIO_3 (mode=4) No | <div align="JUSTIFY">-<br></div> <div align="JUSTIFY"><br></div>No
|-
| 7 [[Peripherals Summary#SPI| DVI_VSYNC | DSS_VSYNC | LCD&nbsp;vertical sync (Expansion)<br> McSPI3]]
|
GPIO_68Yes, not default configuration (mode=4[[Mux instructions#WIFI|disable WIFI]])
| <div align="JUSTIFY"><br></div> <div align="JUSTIFY">No | No | No | No | No | Yes, not default configuration ([[Mux_instructions#TFP410 '''(6|disable DVI]])'''<br></div>
|-
| 8 [[Peripherals Summary#SPI|McSPI4]] | DVI_HSYNC Yes, not default configuration ([[Mux instructions#GPIO_in_J990|disable GPIOs]]) | DSS_HSYNC No | LCD Horitzontal sync (Expansion) No | No GPIO_67 (mode=4)<br> | No | No | <div align="JUSTIFY"><br></div> <div align="JUSTIFY"><div align="JUSTIFY">TFP410 '''(6)'''<br></div></div>No
|-
| 9 [[Peripherals Summary#BSP|McBSP1]] | Yes, not default configuration ([[Mux instructions#GPIO_in_J990|disable GPIOs]]) | No | DVI_ACBIAS No | DSS_ACBIAS No | 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 [[Peripherals Summary#BSP|McBSP2]] | No | No | DVI_PUP No | - No | Control signal for DVI controler (Expansion) No | - No | <div align="JUSTIFY"><br></div> <div align="JUSTIFY">TFP410 '''(6)'''</div>No
|-
| 11 [[Peripherals Summary#BSP|McBSP3]] | DVI_PCLK Yes, default configuration ([[Mux instructions#TP65950_PCM_VSP|Bluetooth audio]]) | DSS_PCLK No | LCD clock (Expansion) No | No GPIO_66 (mode=4)<br> | No | No | <div align="JUSTIFY"><br></div> <div align="JUSTIFY">TFP410 '''(6)'''</div>No
|-
| 12 [[Peripherals Summary#BSP|McBSP4]] | TS_nPEN_IRQ No | McSPI1_CS1 No | Touchscreen control (Expansion) No | No MMC3_CMD(mode=3) | No  GPIO_175 | Yes, not default configuration (mode=4[[Mux instructions#GPIO_in_J990|disable GPIOs]])  | <div align="JUSTIFY">-<br></div> <div align="JUSTIFY"><br></div>No
|-
| 13 [[Peripherals Summary#BSP|McBSP5]] | LCD_QVGA/nVGA No | McBSP4_DX No | Touchscreen control (Expansion) No | No GPIO_154 (mode=4)<br> | No | No | <div align="JUSTIFY">-<br></div>No
|-
| 14 [[Peripherals Summary#MMC|MMC1]] | LCD_ENVDD No | McBSP4_DR No | Touchscreen control (Expansion) No | No GPIO_153 (mode=4)<br> | No | No | -<br>No
|-
| 15 [[Peripherals Summary#MMC|MMC2]] | LCD_RESB Yes, default configuration ([[Mux instructions#WIFI|WIFI]]) | McBSP4_FSX No | Touchscreen control (Expansion) No | No GPIO_155 (mode=4)<br> | No | No | <div align="JUSTIFY"><br></div> <div align="JUSTIFY">-<br> </div> <div align="JUSTIFY"><br></div>No
|-
| 16 [[Peripherals Summary#MMC|MMC3]] | LCD_INI No | McBSP4_CLKX No | Touchscreen control (Expansion) No | No GPIO_152 (mode=4)<br> | No | No | <div align="JUSTIFY">-<br></div>No
|-
| 17 [[Peripherals Summary#I2C|I2C1]] | MCSPI1_CLK No | No McSPI1_CLK<br> | No | No | Touchscreen control (Expansion) No | GPIO_171 (mode=4) No | -<br>No
|-
| 18 [[Peripherals Summary#I2C|I2C2]] | MCSPI1_SIMO Yes, default configuration | McSPI1_SIMO No | Touchscreen control (Expansion) No | No GPIO_172 (mode=4) | No, [[Connectors Summary#JC30_connector|via hardware]] | No | -<br>No
|-
| 19 [[Peripherals Summary#I2C|I2C3]] | MCSPI1_CS0 No | McSPI1_CS0 No | Touchscreen control (Expansion) No | No GPIO_174 (mode=4) | No | No | -<br>Yes, default configuration (DVI)
|-
| 20 [[Peripherals Summary#I2C|I2C4]] | MCSPI1_SOMI No | McSPI1_SOMI No | Touchscreen control (Expansion) No | No GPIO_173 (mode=4) | No | No | -<br>No
|}
<br> '''(6):''' TFP410: Converts DVI&nbsp;signal to HDMI. They share the same video signal.<br> === IGEP MODULE ===
=== JA41 Next table pretends help you to 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 take different solutions. <br> There are some connectors than have more peripherals available, but they don't have all signals to use it. <br> Table shows four answers:&nbsp;
JA41 *"'''Yes, default configuration(utility)'''": Peripheral enabled by default. "utility" shows if this peripheral is used for DVI .<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 (Digital Video Interfaceplacing or replacing some resistances) data partcan be enabled.<br> *"'''No'''"
-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: 669px933px; height: 1064px190px;"
|-
| 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 3V3 [[Peripherals Summary#UART| - UART1]] | Power 3v3 Yes, not default configuration (disable DSS) | - Yes, default configuration | -<br>No
|-
| 2 [[Peripherals Summary#UART| GND UART2]] | -<br> Yes, not default configuration(enable: TX and RX) | GND | -<br> No | -<br>No
|-
| 3 | DVI_DATA0 [[Peripherals Summary#UART| &nbsp; DSS_D0 UART3]] | LCD&nbsp;pixel data bit<br> Yes, default configuration | UART1_CTS(mode=2)  GPIO_70(mode=4) No | TFP410 '''(6)'''No
|-
| 4 | DVI_DATA1 [[Peripherals Summary#UART| &nbsp; DSS_D1 UART4]] | LCD&nbsp;pixel data bit No | UART1_RTSYes, not default configuration(mode=2disable: GPIO_64 and GPMC_WAIT3)  GPIO_71(mode=4)  | <div align="JUSTIFY"><br></div> <div align="JUSTIFY">TFP410 '''(6)'''</div>No
|-
| 5 [[Peripherals Summary#GPIO| DVI_DATA2 GPIO]] | &nbsp;DSS_D2 Yes, default configuration | LCD&nbsp;pixel data bit | GPIO_72(mode=4) Yes, default configuration | TFP410 '''(6)'''Yes, default configuration
|-
| 6 [[Peripherals Summary#SPI| DVI_DATA3 McSPI1]] | DSS_D3 No | LCD&nbsp;pixel data bit | GPIO_73(mode=4) Yes, default configuration | TFP410 '''(6)'''<div align="JUSTIFY"><br></div>No
|-
| 7 | DVI_DATA4 [[Peripherals Summary#SPI| &nbsp;DSS_D4 McSPI2]] | LCD&nbsp;pixel data bit No | UART3_RX(mode=2)  GPIO_74(mode=4) No | <div align="JUSTIFY">TFP410 '''(6)'''</div> <div align="JUSTIFY"><br></div>No
|-
| 8 | DVI_DATA5 [[Peripherals Summary#SPI| DSS_D5 McSPI3]] | LCD&nbsp;pixel data bit | UART3_TXYes, not default configuration (mode=2disable DSS)  GPIO_75(mode=4)<br> | No | <div align="JUSTIFY">TFP410 '''(6)'''</div> <div align="JUSTIFY"><br></div>No
|-
| 9 | DVI_DATA6 [[Peripherals Summary#SPI| DSS_D6 McSPI4]] | LCD&nbsp;pixel data bit No | &nbsp;UART1_TX(mode=2)  GPIO_76(mode=4) No | <div align="JUSTIFY">TFP410 '''(6)'''</div> <div align="JUSTIFY"><div align="JUSTIFY"><br></div></div>No
|-
| 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 [[Peripherals Summary#BSP| DSS_D9 McBSP1]] | LCD&nbsp;pixel data bit No | 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> No | <div align="JUSTIFY"><br></div> <div align="JUSTIFY">TFP410 '''(6)''' </div> <div align="JUSTIFY"><br></div>No
|-
| 16 [[Peripherals Summary#BSP| DVI_DATA13 McBSP2]] | DSS_D13 No | LCD&nbsp;pixel data bit | GPIO_83(mode=4)<br> No | <div align="JUSTIFY">TFP410 '''(6)'''</div>No
|-
| 17 [[Peripherals Summary#BSP| DVI_DATA14 McBSP3]] | DSS_D14  | LCD&nbsp;pixel data bit | GPIO_84(mode=4)  | TFP410 '''Yes, not default configuration (6disable UART2)'''|-No | 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)'''No
|-
| 20 | DVI_DATA17 [[Peripherals Summary#BSP| DSS_D17 McBSP4]] | LCD&nbsp;pixel data bit No | GPIO_87Yes, not default configuration (mode=4disable GPMCs)  | TFP410 '''(6)'''No
|-
| 21<br> | DVI_DATA18 [[Peripherals Summary#BSP| DSS_D18 McBSP5]] | LCD&nbsp;pixel data bit No | DSS_D0 (mode=3)  MCSPI3_CLKYes, not default configuration (mode=2disable GPIOs)  GPIO_88(mode=4)  | TFP410 '''(6)'''No
|-
| 22<br> [[Peripherals Summary#MMC| DVI_DATA19 MMC1]] | DSS_D19 No | LCD&nbsp;pixel data bit | DSS_1 (mode=3)  MCSPI3_SIMO(mode=2)  GPIO_89(mode=4) No | TFP410 '''(6)'''No
|-
| 23<br> [[Peripherals Summary#MMC| DVI_DATA20 MMC2]] | DSS_D20 No | 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]]