Changes

Mux configuration

4,861 bytes removed, 10:55, 17 February 2014

no edit summary

= Overview =

Mux (or multiplexer) This wiki is meant to be a Omap peripheral that can be controlled via software. Its function is connect other peripherals starting point for people to some available Omap padslearn configure mux for IGEP devices as quickly and easily as possible. This wiki contains:<br>

IgepV2 Board have a default mux configuration, but some cases is necessary change it, for example your project need UART2 at j990 connector *Mux characteristics summary*Tips to avoid problems*Ways to transmit data, for this purpose you need change some configure mux configurations to enable it and be sure *Tables that this modification don't break or interferes in other IC or links peripherals. The mux options are vast. and connectors for IGEPv2 and IGEP MODULE

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 There are three ways to configure mux in IGEP Boards based in OMAP35xx and Contributing =DM37xx:<br>

At any point*[[Mux_instructions|Configuring MUX from OS User Space]]. This mode has a issue, if when your system reboot or shutdown you see a mistake you can contribute 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 this 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-Toto set up UART2 in J990#Third_way|Example]]. <br>

= Available peripherals on external connector =

Before configure mux is necessary review some things: = Introduction =

- If connector Mux (or multiplexer) is shared with other peripherals you should disable it a Omap peripheral that can be controlled via software or hardware.<br> - Don't use the same peripheral in more than one padIts function is connect other peripherals to some available Omap pins.

The next tables show you all the mux capabilitiesEach pin is configurable by software using its associated pad configuration register field, which is 16 bits wide:

=== 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: 960px; height: 1463px;center"

|-

| Pad[[Image: Mux register.png]]| Connect to: | Default peripheral (mode=0) }

| Default function: | Other available peripherals: | style="text-align: left;" | Share with:|-| 1 | VIO 1V8 | - | Power 1v8 | - | -<br>|One pad configuration register field is available for each pin. Each 32-| 2 | DC 5V | - | Power 5v | - | bit pad configuration register is grouped into two 16-bit pad configuration register fields. One pad configuration register provides control for two different pins. These registers can be accessed using 8, 16 and 32 bits operations.<br>|-| 3 | MMC2_DAT7 | MMC2_DAT7 | Reset Wlan | MMC2_CLKIN(mode=1)

MMC3_DAT3(mode=3) The functional bits of a pad configuration register field are divided into the following five fields:

GPIO_139• '''MUXMODE''' (3 bits) defines the multiplexing mode=4applied 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.

| <div align="JUSTIFY">• '''Wlan:PULL''' This pad can reset Wlan peripheral using Omap GPIO low level (GND2 bits). If you reset continuously Wlan all their pads are in High Impedance. Also you can disable Wlan from J990 low level.<for combinational pullup/div> <div align="JUSTIFY">'''Omappulldown configuration: '''protect Omap pad if you don't use it.'''(1)'''</div>|-| 5 | MMC2_DAT6 | MMC2_DAT6 | Power down&nbsp; Wlan | MMC2_DIR_CMD(mode=1)

MMC3_DAT2(mode=3) -&gt; PULLTYPESELECT: Pullup/pulldown selection for the pin.

GPIO_138(mode=4) -&gt; PULLUDENABLE: Pullup/pulldown enable for the pin.

| <div align="JUSTIFY">• '''Wlan:INPUTENABLE''' This pad can power down Wlan peripheral using Omap GPIO low level (GND1 bit), power up removing GND. Also you can power down Wlan from J990 low level.<drives an input enable signal to the I/div> <div align="JUSTIFY">'''Omap: '''protect Omap pad if you don't use itO CTRL.'''(1)'''</div>|-| 7 | MMC2_DAT5 | MMC2_DAT5 | Reset Bluethoot | MMC2_DIR_DAT1(mode=1)

MMC3_DAT1• '''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=3) 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:

GPIO_137(-&gt;OFFENABLE: Off mode=4) pin state override control. Set to 1 to enable the feature and to 0 to disable it.

| <div align="JUSTIFY">'''Bluethoot-&gt;OFFOUTENABLE: '''This pad can reset Bluethoot peripheral using Omap GPIO low level (GND)Off mode output enable value. If you reset continuously Bluethoot all their pads are in High Impedance. Also you can Set to 0 to enable the feature and to 1 to disable Bluethoot from J990 low level.'''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(-&gt;OFFOUTVALUE: Off mode=3) output value.

GPIO136(-&gt;OFFPULLUDENABLE: Off mode=4) pullup/pulldown enable.

| <div align="JUSTIFY">'''Wlan-&gt;OFFPULLTYPESELECT: '''Protect Wlan if you don' use it. See MMC2_DAT7 pad.<Off mode pullup/div> <div align="JUSTIFY">'''Omap: '''protect Omap pad if you don't use itpulldown selection.'''(1)'''</div>|-| 11 | MMC2_DAT3 | MMC2_DAT3 | Transfer data between Omap and Wlan | McSPI3_CS0(mode=1)

GPIO_135• '''Wake-up''' bits (mode=42 bits) :

| <div align="JUSTIFY">'''Wlan-&gt;WAKEUPENABLE: '''Protect Wlan if you don' use itEnable wake-up detection on input. See MMC2_DAT7 padIt is also the off mode input enable value.</div> <div align="JUSTIFY">'''Omap: '''protect Omap pad if you don't use it.'''(1)'''</div>|-| 13 | MMC2_DAT2 | MMC2_DAT2 | Transfer data between Omap and Wlan | McSPI3_CS1(mode=1)<br>

GPIO_134(mode=4) -&gt;WAKEUPEVENT: Wake-up event status for the pin.'''<br>'''

{| <div aligncellspacing="JUSTIFY1">'''Wlan: '''Protect Wlan if you don' use it. See MMC2_DAT7 pad.</div> <div aligncellpadding="JUSTIFY1" border=">'''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(mode=4) | <div " align="JUSTIFYcenter">'''Wlan: '''Protect Wlan if you don' use it. See MMC2_DAT7 pad.</div> <div alignwidth="JUSTIFY200">'''Omap: '''protect Omap pad if you don't use it.'''(1)'''</div>

|-

| 17

| MMC2_DAT0

| MMC2_DAT0

| Transfer data between Omap and Wlan

|

McSPI3_SOMI(mode=1) [[Image:Mux pad configuration diagram.png]]

GPIO_132(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) | McSPI3_SIMO(mode=1) Mode selection ===

GPIO_131(mode=4) The next table shows all capabilities.<br>

{| <div aligncellspacing="JUSTIFY1" cellpadding="1">'''Wlan: '''Protect Wlan if you don' use it. See MMC2_DAT7 pad.</div> <div alignborder="JUSTIFY1" style=">'''Omapwidth: 287px; height: '''protect Omap pad if you don't use it.'''(1)'''</div>235px;"

|-

| 21 MUXMODE | 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>Select Mode

|-

| 4 | MCBSP3_DX | MCBSP3_DX | Transmitted serial Data (Bluethoot audio) 0b000=0 | UART2_CTSMode 0 (Primary mode=1)  GPIO_140(mode=4)  | <div align="JUSTIFY">'''TPS65950:''' disable it via kernel '''(2) '''If you don't use it.</div>

|-

| 6 | MCBSP3_CLKX | MCBSP3_CLKX | Transmitted serial Clock (Bluethoot audio) 0b001=1 | UART2_TX(mode=Mode 1)  GPIO_142(Possible 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 0b010=2 | MCBSP3_FSX | MCBSP3_FSX | Transmited Frame Syncronisation (Bluethoot audio) | UART2_RX(mode=1)  GPIO_143Mode 2 (Possible 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) 0b011=3 | UART2_RTSMode 3 (Possible mode=1)  GPIO_141(mode=4)  | <div align="JUSTIFY">'''TPS65950:''' disable it via kernel '''(2) '''If you don't use it.</div>

|-

| 12 0b100=4 | MCBSP1_DX | MCBSP1_DX | Transmited serial Data (not used) | McSPI4_SIMOMode 4 (Possible mode=1)  McBSP3_DX(mode=2)  GPIO_158(mode=4)  | -<br>

|-

| 14 | MCBSP1_CLKX | MCBSP1_CLKX 0b101=5 | Transmited serial clock (not used) | McBSP3_CLKX(mode=2)<br>  GPIO_162Mode 5 (Possible mode=4)  | -<br>

|-

| 16 | MCBSP1_FSX 0b110=6 | MCBSP1_FSX | Transmited Frame Syncronization (not used) | McSPI4_CS0(mode=1)  McBSP3_FSXMode 6 (Possible mode=2)  GPIO_161(mode=4)  | -<br>

|-

| 18 | MCBSP1_DR | MCBSP1_DR | Received Serial Data (not used) | McSPI4_SOMI(mode=1)  McBSP3_DR(mode=2)  GPIO_159(mode0b111=4) 7 | -<br>|-| 20 | MCBSP1_CLKR | MCBSP1_CLKR | Received Clock Mode 7 (not used) | GPIO_156(mode=4Safe Mode)<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 connectorDefinitions:''' Check and RC14 is not welded or don't use it.<br></div>|-| 24 | I2C2_SCL | I2C2_SCL | I2C Clock | GPIO_168(mode=4)<br>

| '''Cam connector:Mode 0''' Check and RC13 is not welded or 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.|-| 25 | REGEN | - | Master/Slave control power TPS65950<br> | - | -<br>|-| 26 | nRESET | - | Read Reset Omap | - | -<br>|-| 27 | GND | - | GND | - | -<br>|-| 28 | GND | - | GND | - | -<br>|}

'''(Mode 1):to mode 6''' To protect Omap pads from esternal signals configure Mux in mode=7 (safe_mode)are possible modes for alternate functions. With this modeOn each pin, some modes are used effectively for alternate functions, buffer is configured in high impedance while other modes are unused and correspond to no functional configuration.

'''The safe mode (2default mode 7):''' Disable TPS65950 go avoids any risk of electrical contention by configuring the pin as an input with no functional interface mapped to file sound/soc/codecs/twl4030it. The safe mode is used mainly as the default mode for all pins containing no mandatory interface at the release of power-on reset.c change line 54 Code: <pre>0x00, /* REG_VOICE_IF (0xF) */</prebr> to Code: <pre>0x04, /* REG_VOICE_IF (0xF) */</pre> '''(3):''' Omap mux have 8 modes, somes modes are disable in some pads.

=== J960 connector Pull Selection ===

J960 connector can not use mux The next table shows all 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>

{| cellspacing="1" cellpadding="1" border="1" style="width: 498px696px; height: 381px1px;"|-| 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)'''<br>|-| 3 | RS232_TX2 | UART3_TX | UART2_TX | -<br> | Kernel console params'''(4)'''<br>|-| 4 | - | - | - | -<br> | -<br>|-| 5 | GND | - | - | -<br> | -<br>

|-

| 6 PULLTYPESELECT | GND PULLUDENABLE | - | - | -<br> | -<br>Pin Behavior

|-

| 7 0b0 | - | - | - | -<br> 0b0 | Pull-<br>down selected but not activated

|-

| 8 0b0 | RS232_TX1 | UART1_TX | UART3_TX | RS485 interface'''(5)'''<br> 0b1 | Pull-<br>down selected and activated if pin is NOT configured as OUTPUT

|-

| 9 0b1 | RS232_RX1 | UART1_RX | UART3_RX | RS485 interface'''(5)'''<br> 0b0 | Pull-<br>up selected but not activated

|-

| 10 0b1 | - | - | - | -<br> 0b1 | Pull-<br>up selected and activated if pin is NOT configured as OUTPUT

|}

<br>  - Don't use the same peripheral When a pin is in more than one padoutput mode, pulls are automatically disable.

- Other peripherals can be configured via hardware, placing/replacing some resistances. See IGEPv2 Schematic for more information. === Input Enable ===

'''(4)INPUTENABLE = 0:''' To set other functionalities to UART3 (/dev/ttyS2) edit igepInput Disable. Pin is configured in output only mode.ini file:

Search line: <pre>consoleINPUTENABLE =ttyS2,115200n8</pre> Replace by1: <pre>; console=ttyS2,115200n8</pre> '''(5): '''Allows to use UART1 as RS232 instead of EI485, edit igepInput Enable. Pin is configured in bidirectional mode.ini:<br>

Search line: <pre>board.ei485=yes</pre> Replace by: <pre>board.ei485=no</pre> === J400 connector '''Off mode values''' and '''Wake-up''' ===

J400 This mode is used to JTAG (Joint Test Action Group)disable some pins and reduce power consumption. 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 Please contribute.

More information: [http://eswww.wikipediati.orgcom/wikilit/JTAG http:ug/spruf98x/esspruf98x.wikipedia.org/wiki/JTAGpdf More information]about mux.

Only Pad 13 and 14 have mux capabilities, for example you can use them like GPIO(mode=4). More information in IGEPv2 Schematic.<br> Configure Mux =

=== J970 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:

This connector don't have *Mux can connect multiple connectors at the same peripheral, this improper use can damage the processor. Before configure mux capabilities, 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 to avoid interferences.&nbsp; For example: if you want to control WIFI module via J990 disable OMAP or if you want use [[How to set up UART2 in 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-to use gpios]] for more information.

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> === IGEPv2 ===

- Can handle up Next table pretends help you to 8 x 8 keypads, 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 handle up to 4 x 4 keypadstake different solutions.<br>- OptionallyThere are some connectors than have more peripherals available, you can decode via Omap software.<br>- Event detection on key press and key releasebut they don't have all signals to use it.<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 capabilitie:  {| 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 [[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_DAT3 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 | 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> === JA41 connector IGEP MODULE === 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 capabilitie:  {| cellspacing="1" cellpadding="1" border="1" align="JUSTIFY" style="width: 960px; height: 1463px;"|-| Pad: | Connect to: | Default peripheral (mode=0)

| Default function: | Other available Next table pretends help you to configure IGEP MODULE. First column shows some OMAP35xx/DM37xx peripherals: | style="text-align: left;" | Share with:|-| 1 | VIO 3V3| - | Power 3v3 | - | -and first row shows all IGEP MODULE connectors. Read articles about connector and peripheral before use them. Each configuration can take different solutions. <br>|-| 2 | GND| -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;

| GND *"'''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'''"

{| -<br>cellspacing="1" cellpadding="1" border="1" style="width: 933px; height: 190px;"

|-

| 3

| DVI_DATA0

| - DSS_D0

| <br>

| - [[Connectors Summary#J1_connector|J1]] | <div align="JUSTIFY">-<br></div>[[Connectors Summary#J4_connector|J4]] | [[Connectors Summary#J5_connector|J5]]

|-

| 4 | DVI_DATA1[[Peripherals Summary#UART| DSS_D1UART1]] | <br>Yes, not default configuration (disable DSS) | - Yes, default configuration | <div align="JUSTIFY"><br></div> <div align="JUSTIFY">-<br></div>No

|-

| 5 | DVI_DATA2[[Peripherals Summary#UART| &nbsp;DSS_D2 UART2]] | <br>| GPIO_2 Yes, not default configuration(mode=4enable: TX and RX) | No | <div align="JUSTIFY"><br> -<br> </div>No

|-

| 6 [[Peripherals Summary#UART| DVI_DATA3UART3]] | &nbsp;DSS_D3 Yes, default configuration | <br> | GPIO_3 (mode=4) No | <div align="JUSTIFY">-<br></div> <div align="JUSTIFY"><br></div>No

|-

| 7 | DVI_DATA4[[Peripherals Summary#UART| DSS_D4UART4]] | <br> No | GPIO_68Yes, not default configuration(mode=4disable: GPIO_64 and GPMC_WAIT3)  | <div align="JUSTIFY"><br></div> <div align="JUSTIFY">TFP410 '''(6)'''<br></div>No

|-

| 8 [[Peripherals Summary#GPIO| DVI_DATA5GPIO]] | DSS_D5Yes, default configuration | <br>| GPIO_67 (mode=4)<br> Yes, default configuration | <div align="JUSTIFY"><br></div> <div align="JUSTIFY"><div align="JUSTIFY">TFP410 '''(6)'''<br></div></div>Yes, default configuration

|-

| 9 | DVI_DATA6[[Peripherals Summary#SPI| DSS_D6McSPI1]] | No | &nbsp; GPIO_133(mode=4) Yes, default configuration | <div align="JUSTIFY"><br></div> <div align="JUSTIFY"><div align="JUSTIFY">TFP410 '''(6)'''<br></div></div>No

|-

| 10 | DVI_DATA7[[Peripherals Summary#SPI| DSS_D7McSPI2]] | <br>No | - No | <div align="JUSTIFY"><br></div> <div align="JUSTIFY">TFP410 '''(6)'''</div>No

|-

| 11 [[Peripherals Summary#SPI| DVI_DATA8McSPI3]] | DSS_D8| <br>| GPIO_66 Yes, not default configuration (mode=4disable DSS)<br> | No | <div align="JUSTIFY"><br></div> <div align="JUSTIFY">TFP410 '''(6)'''</div>No

|-

| 12 | DVI_DATA9[[Peripherals Summary#SPI| DSS_D9McSPI4]] | <br>No | MMC3_CMD  GPIO_175 (mode=4) No | <div align="JUSTIFY"><br></div> <div align="JUSTIFY"><br></div>No

|-

| 13 [[Peripherals Summary#BSP| DVI_DATA10McBSP1]] | DSS_D10No | <br>| GPIO_154 (mode=4)<br> No | <div align="JUSTIFY"><br></div>No

|-

| 14 | DVI_DATA11[[Peripherals Summary#BSP| DSS_D11McBSP2]] | <br>No | GPIO_153 (mode=4)<br>  | <br>|-| 15 | DVI_DATA12| DSS_D12| <br>| GPIO_155 (mode=4)<br> No | <div align="JUSTIFY"><br></div> <div align="JUSTIFY"><br> </div> <div align="JUSTIFY"><br></div>No

|-

| 16 | DVI_DATA13[[Peripherals Summary#BSP| DSS_D13McBSP3]] | <br>| GPIO_152 Yes, not default configuration (mode=4disable UART2)<br> | No | <div align="JUSTIFY"><br></div>No

|-

| 17 | DVI_DATA14[[Peripherals Summary#BSP| DSS_D14 McBSP4]] | <br>No | GPIO_171 Yes, not default configuration (mode=4disable GPMCs)  | -<br>|-| 18 | DVI_DATA15| DSS_D15| <br>| GPIO_172 (mode=4)  | -<br>|-| 19 | DVI_DATA16| DSS_D16| <br>| GPIO_174 (mode=4)  | -<br>|-| 20 | DVI_DATA17| DSS_D17| <br>| GPIO_173 (mode=4)  | -<br>No

|-

| 21<br>| DVI_DATA18[[Peripherals Summary#BSP| DSS_D18McBSP5]] | <br>No | <br>Yes, not default configuration (disable GPIOs) | <br>No

|-

| 22<br>| DVI_DATA19[[Peripherals Summary#MMC| DSS_D19MMC1]] | <br>No | <br>No | <br>No

|-

| 23<br>| DVI_DATA20[[Peripherals Summary#MMC| DSS_D20MMC2]] | <br>No | <br>No | <br>No

|-

| 24<br>| DVI_DATA21[[Peripherals Summary#MMC| DSS_D21MMC3]] | <br>No | <br>No | <br>Yes, not default configuration (disable GPIOs)

|-

| 25<br>| DVI_DATA22<br>[[Peripherals Summary#I2C| DSS_D22<br>I2C1]] | <br>No | <br>No | <br>No

|-

| 26<br>| DVI_DATA23<br>[[Peripherals Summary#I2C| DSS_D23<br>I2C2]] | <br>No | <br>No | <br>No

|-

| 27<br>| I2C3_SCL<br>[[Peripherals Summary#I2C| I2C3_SCLI2C3]] | <br>Yes, default configuration (J5) | <br>No | <br>Yes, default configuration (J1)

|-

| 28<br>| I2C3_SDA<br>[[Peripherals Summary#I2C| I2C3_SDAI2C4]] | <br>No | <br>No | <br>No

|}

<br> '''(6)[[Category:''' TFP410Work_in_progress]][[Category: Converts DVI&nbsp;signal to HDMI. They share the same video signal.<br>  Under constructionPeripherals]]

• ← Older edit

Agustí Fontquerni

User

88

edits