Difference between revisions of "Mux configuration"

From IGEP - ISEE Wiki

Jump to: navigation, search
Line 678: Line 678:
 
=== JA41 connector  ===
 
=== JA41 connector  ===
  
−
JA42 is used for DVI (Digital Video Interface) control part, TouchScreen control and SPI1.<br>  
+
JA41 is used for DVI (Digital Video Interface) data part.<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.  
 
-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:  
+
Some pads have mux capabilities:  
  
 
{| cellspacing="1" cellpadding="1" border="1" align="JUSTIFY" style="width: 960px; height: 1463px;"
 
{| cellspacing="1" cellpadding="1" border="1" align="JUSTIFY" style="width: 960px; height: 1463px;"
Line 696: Line 696:
 
|-
 
|-
 
| 1  
 
| 1  
−
| VIO 3V3
+
| VIO 3V3  
 
| -  
 
| -  
 
| Power 3v3  
 
| Power 3v3  
Line 703: Line 703:
 
|-
 
|-
 
| 2  
 
| 2  
−
| GND
+
| GND  
 
|  
 
|  
 
-<br>  
 
-<br>  
Line 714: Line 714:
 
|-
 
|-
 
| 3  
 
| 3  
−
| DVI_DATA0
+
| DVI_DATA0  
−
| - DSS_D0
+
| - DSS_D0  
−
| <br>
+
| <br>  
 
| -  
 
| -  
 
| <div align="JUSTIFY">-<br></div>
 
| <div align="JUSTIFY">-<br></div>
 
|-
 
|-
 
| 4  
 
| 4  
−
| DVI_DATA1
+
| DVI_DATA1  
−
| DSS_D1
+
| DSS_D1  
−
| <br>
+
| <br>  
 
| -  
 
| -  
 
| <div align="JUSTIFY"><br></div> <div align="JUSTIFY">-<br></div>
 
| <div align="JUSTIFY"><br></div> <div align="JUSTIFY">-<br></div>
 
|-
 
|-
 
| 5  
 
| 5  
−
| DVI_DATA2
+
| DVI_DATA2  
 
|  
 
|  
 
&nbsp;DSS_D2  
 
&nbsp;DSS_D2  
  
−
| <br>
+
| <br>  
 
|  
 
|  
 
GPIO_2 (mode=4)  
 
GPIO_2 (mode=4)  
Line 741: Line 741:
 
|-
 
|-
 
| 6  
 
| 6  
−
| DVI_DATA3
+
| DVI_DATA3  
 
|  
 
|  
 
&nbsp;DSS_D3  
 
&nbsp;DSS_D3  
Line 752: Line 752:
 
|-
 
|-
 
| 7  
 
| 7  
−
| DVI_DATA4
+
| DVI_DATA4  
−
| DSS_D4
+
| DSS_D4  
 
| <br>  
 
| <br>  
 
|  
 
|  
Line 761: Line 761:
 
|-
 
|-
 
| 8  
 
| 8  
−
| DVI_DATA5
+
| DVI_DATA5  
−
| DSS_D5
+
| DSS_D5  
−
| <br>
+
| <br>  
 
|  
 
|  
 
GPIO_67 (mode=4)<br>  
 
GPIO_67 (mode=4)<br>  
Line 770: Line 770:
 
|-
 
|-
 
| 9  
 
| 9  
−
| DVI_DATA6
+
| DVI_DATA6  
−
| DSS_D6
+
| DSS_D6  
 
|  
 
|  
 
| &nbsp; GPIO_133(mode=4)  
 
| &nbsp; GPIO_133(mode=4)  
Line 777: Line 777:
 
|-
 
|-
 
| 10  
 
| 10  
−
| DVI_DATA7
+
| DVI_DATA7  
−
| DSS_D7
+
| DSS_D7  
−
| <br>
+
| <br>  
 
| -  
 
| -  
 
| <div align="JUSTIFY"><br></div> <div align="JUSTIFY">TFP410 '''(6)'''</div>
 
| <div align="JUSTIFY"><br></div> <div align="JUSTIFY">TFP410 '''(6)'''</div>
 
|-
 
|-
 
| 11  
 
| 11  
−
| DVI_DATA8
+
| DVI_DATA8  
−
| DSS_D8
+
| DSS_D8  
−
| <br>
+
| <br>  
 
|  
 
|  
 
GPIO_66 (mode=4)<br>  
 
GPIO_66 (mode=4)<br>  
Line 793: Line 793:
 
|-
 
|-
 
| 12  
 
| 12  
−
| DVI_DATA9
+
| DVI_DATA9  
−
| DSS_D9
+
| DSS_D9  
−
| <br>
+
| <br>  
 
|  
 
|  
 
MMC3_CMD  
 
MMC3_CMD  
Line 804: Line 804:
 
|-
 
|-
 
| 13  
 
| 13  
−
| DVI_DATA10
+
| DVI_DATA10  
−
| DSS_D10
+
| DSS_D10  
−
| <br>
+
| <br>  
 
|  
 
|  
 
GPIO_154 (mode=4)<br>  
 
GPIO_154 (mode=4)<br>  
Line 813: Line 813:
 
|-
 
|-
 
| 14  
 
| 14  
−
| DVI_DATA11
+
| DVI_DATA11  
−
| DSS_D11
+
| DSS_D11  
−
| <br>
+
| <br>  
 
|  
 
|  
 
GPIO_153 (mode=4)<br>  
 
GPIO_153 (mode=4)<br>  
Line 822: Line 822:
 
|-
 
|-
 
| 15  
 
| 15  
−
| DVI_DATA12
+
| DVI_DATA12  
−
| DSS_D12
+
| DSS_D12  
−
| <br>
+
| <br>  
 
|  
 
|  
 
GPIO_155 (mode=4)<br>  
 
GPIO_155 (mode=4)<br>  
Line 831: Line 831:
 
|-
 
|-
 
| 16  
 
| 16  
−
| DVI_DATA13
+
| DVI_DATA13  
−
| DSS_D13
+
| DSS_D13  
−
| <br>
+
| <br>  
 
|  
 
|  
 
GPIO_152 (mode=4)<br>  
 
GPIO_152 (mode=4)<br>  
Line 840: Line 840:
 
|-
 
|-
 
| 17  
 
| 17  
−
| DVI_DATA14
+
| DVI_DATA14  
 
|  
 
|  
 
DSS_D14  
 
DSS_D14  
  
−
| <br>
+
| <br>  
 
|  
 
|  
 
GPIO_171 (mode=4)  
 
GPIO_171 (mode=4)  
Line 851: Line 851:
 
|-
 
|-
 
| 18  
 
| 18  
−
| DVI_DATA15
+
| DVI_DATA15  
−
| DSS_D15
+
| DSS_D15  
−
| <br>
+
| <br>  
 
|  
 
|  
 
GPIO_172 (mode=4)  
 
GPIO_172 (mode=4)  
Line 860: Line 860:
 
|-
 
|-
 
| 19  
 
| 19  
−
| DVI_DATA16
+
| DVI_DATA16  
−
| DSS_D16
+
| DSS_D16  
−
| <br>
+
| <br>  
 
|  
 
|  
 
GPIO_174 (mode=4)  
 
GPIO_174 (mode=4)  
Line 869: Line 869:
 
|-
 
|-
 
| 20  
 
| 20  
−
| DVI_DATA17
+
| DVI_DATA17  
−
| DSS_D17
+
| DSS_D17  
−
| <br>
+
| <br>  
 
|  
 
|  
 
GPIO_173 (mode=4)  
 
GPIO_173 (mode=4)  
Line 877: Line 877:
 
| -<br>
 
| -<br>
 
|-
 
|-
−
| 21<br>
+
| 21<br>  
−
| DVI_DATA18
+
| DVI_DATA18  
−
| DSS_D18
+
| DSS_D18  
−
| <br>
+
| <br>  
−
| <br>
+
| <br>  
 
| <br>
 
| <br>
 
|-
 
|-
−
| 22<br>
+
| 22<br>  
−
| DVI_DATA19
+
| DVI_DATA19  
−
| DSS_D19
+
| DSS_D19  
−
| <br>
+
| <br>  
−
| <br>
+
| <br>  
 
| <br>
 
| <br>
 
|-
 
|-
−
| 23<br>
+
| 23<br>  
−
| DVI_DATA20
+
| DVI_DATA20  
−
| DSS_D20
+
| DSS_D20  
−
| <br>
+
| <br>  
−
| <br>
+
| <br>  
 
| <br>
 
| <br>
 
|-
 
|-
−
| 24<br>
+
| 24<br>  
−
| DVI_DATA21
+
| DVI_DATA21  
−
| DSS_D21
+
| DSS_D21  
−
| <br>
+
| <br>  
−
| <br>
+
| <br>  
 
| <br>
 
| <br>
 
|-
 
|-
−
| 25<br>
+
| 25<br>  
−
| DVI_DATA22<br>
+
| DVI_DATA22<br>  
−
| DSS_D22<br>
+
| DSS_D22<br>  
−
| <br>
+
| <br>  
−
| <br>
+
| <br>  
 
| <br>
 
| <br>
 
|-
 
|-
−
| 26<br>
+
| 26<br>  
−
| DVI_DATA23<br>
+
| DVI_DATA23<br>  
−
| DSS_D23<br>
+
| DSS_D23<br>  
−
| <br>
+
| <br>  
−
| <br>
+
| <br>  
 
| <br>
 
| <br>
 
|-
 
|-
−
| 27<br>
+
| 27<br>  
−
| I2C3_SCL<br>
+
| I2C3_SCL<br>  
−
| I2C3_SCL
+
| I2C3_SCL  
−
| <br>
+
| <br>  
−
| <br>
+
| <br>  
 
| <br>
 
| <br>
 
|-
 
|-
−
| 28<br>
+
| 28<br>  
−
| I2C3_SDA<br>
+
| I2C3_SDA<br>  
−
| I2C3_SDA
+
| I2C3_SDA  
−
| <br>
+
| <br>  
−
| <br>
+
| <br>  
 
| <br>
 
| <br>
 
|}
 
|}

Revision as of 18:35, 23 November 2011

Overview

Mux (or multiplexer) is a Omap peripheral that can be controlled via software. Its function is connect other peripherals to some available Omap pads.

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 Linaro Headless and Ubuntu 10.04 with Linaro Toolchain.

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.
- Don't use the same peripheral in more than one pad.

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:

     3: HSUSB3_TLL_NXT
     4: HSUSB3_TLL_D4
     5: HSUSB3_TLL_DIR
     6: HSUSB3_TLL_D6
     7: HSUSB3_TLL_STP
     8: HSUSB3_TLL_D7
     10: HSUSB3_TLL_D5


Pad: Connect to:

Default peripheral (mode=0)

Default function: Other available peripherals: Share with:
1 VIO 1V8 - Power 1v8 - -
2 DC 5V - Power 5v - -
3 MMC2_DAT7 MMC2_DAT7 Reset Wlan

MMC2_CLKIN(mode=1)

MMC3_DAT3(mode=3)

GPIO_139(mode=4)

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.
Omap: protect Omap pad if you don't use it.(1)
5 MMC2_DAT6 MMC2_DAT6 Power down  Wlan

MMC2_DIR_CMD(mode=1)

MMC3_DAT2(mode=3)

GPIO_138(mode=4)

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.
Omap: protect Omap pad if you don't use it.(1)
7 MMC2_DAT5 MMC2_DAT5 Reset Bluethoot

MMC2_DIR_DAT1(mode=1)

MMC3_DAT1(mode=3)

GPIO_137(mode=4)

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)

9 MMC2_DAT4 MMC2_DAT4 -

MMC_DIR_DAT0(mode=1)

MMC3_DAT0(mode=3)

GPIO136(mode=4)

Wlan: Protect Wlan if you don' use it. See MMC2_DAT7 pad.
Omap: protect Omap pad if you don't use it.(1)
11 MMC2_DAT3 MMC2_DAT3 Transfer data between Omap and Wlan

McSPI3_CS0(mode=1)

GPIO_135(mode=4)

Wlan: Protect Wlan if you don' use it. See MMC2_DAT7 pad.
Omap: protect Omap pad if you don't use it.(1)
13 MMC2_DAT2 MMC2_DAT2 Transfer data between Omap and Wlan

McSPI3_CS1(mode=1)

GPIO_134(mode=4)

Wlan: Protect Wlan if you don' use it. See MMC2_DAT7 pad.
Omap: protect Omap pad if you don't use it.(1)
15 MMC2_DAT1 MMC2_DAT1 Transfer data between Omap and Wlan  GPIO_133(mode=4)
Wlan: Protect Wlan if you don' use it. See MMC2_DAT7 pad.
Omap: protect Omap pad if you don't use it.(1)
17 MMC2_DAT0 MMC2_DAT0 Transfer data between Omap and Wlan

McSPI3_SOMI(mode=1)

GPIO_132(mode=4)

Wlan: Protect Wlan if you don' use it. See MMC2_DAT7 pad.
Omap: protect Omap pad if you don't use it.(1)
19 MMC2_CMD MMC2_CMD Control Wire for bus MMC2 (Wlan)

McSPI3_SIMO(mode=1)

GPIO_131(mode=4)

Wlan: Protect Wlan if you don' use it. See MMC2_DAT7 pad.
Omap: protect Omap pad if you don't use it.(1)
21 MMC2_CLK0 MMC2_CLK Clock for MMC2 (Wlan)

McSPI3_CLK(mode=1)

GPIO_130(mode=4)

Wlan: Protect Wlan if you don' use it. See MMC2_DAT7 pad.
Omap: protect Omap pad if you don't use it.(1)
4 MCBSP3_DX MCBSP3_DX Transmitted serial Data (Bluethoot audio)

UART2_CTS(mode=1)

GPIO_140(mode=4)

TPS65950: disable it via kernel (2) If you don't use it.
6 MCBSP3_CLKX MCBSP3_CLKX Transmitted serial Clock (Bluethoot audio)

UART2_TX(mode=1)

GPIO_142(mode=4)

Bluethoot: Protect Bluethoot if you don' use it. See MMC2_DAT5 pad.

TPS65950: disable it via kernel (2) If you don't use it.
8 MCBSP3_FSX MCBSP3_FSX Transmited Frame Syncronisation (Bluethoot audio)

UART2_RX(mode=1)

GPIO_143(mode=4)

Bluethoot: Protect Bluethoot if you don' use it. See MMC2_DAT5 pad.

TPS65950: disable it via kernel (2) If you don't use it.
10 MCBSP3_DR MCBSP3_DR Received Serial Data (Bluethoot audio)

UART2_RTS(mode=1)

GPIO_141(mode=4)

TPS65950: disable it via kernel (2) If you don't use it.
12 MCBSP1_DX MCBSP1_DX Transmited serial Data (not used)

McSPI4_SIMO(mode=1)

McBSP3_DX(mode=2)

GPIO_158(mode=4)

-
14 MCBSP1_CLKX MCBSP1_CLKX Transmited serial clock (not used)

McBSP3_CLKX(mode=2)

GPIO_162(mode=4)

-
16 MCBSP1_FSX MCBSP1_FSX Transmited Frame Syncronization (not used)

McSPI4_CS0(mode=1)

McBSP3_FSX(mode=2)

GPIO_161(mode=4)

-
18 MCBSP1_DR MCBSP1_DR Received Serial Data (not used)

McSPI4_SOMI(mode=1)

McBSP3_DR(mode=2)

GPIO_159(mode=4)

-
20 MCBSP1_CLKR MCBSP1_CLKR Received Clock (not used)

GPIO_156(mode=4)

 -
22 MCBSP1_FSR MCBSP1_FSR Received frame syncronization (not used)

GPIO_157(mode=4)

 -
23 I2C2_SDA I2C2_SDA I2C Data

GPIO_183(mode=4)
Cam connector: Check and RC14 is not welded or don't use it.
24 I2C2_SCL I2C2_SCL I2C Clock

GPIO_168(mode=4)

 Cam connector: Check and RC13 is not welded or don't use it.
25 REGEN - Master/Slave control power TPS65950
 - -
26 nRESET - Read Reset Omap - -
27 GND - GND - -
28 GND - GND - -

(1): To protect Omap pads from esternal 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: 

0x00, /* REG_VOICE_IF (0xF) */

to Code: 

0x04, /* REG_VOICE_IF (0xF) */

(3): Omap mux have 8 modes, somes modes are disable in some pads.

J960 connector

J960 connector can not use mux capabilities, because this connector is dedicated to use RS232 comunication. Default hardware/software configuration is:

Pad Connect to: Default periphera: Other peripheral: Share with:
 Default function:
1 - - - -
2 RS232_RX2 UART3_RX UART2_RX -
 Kernel console params(4)
3 RS232_TX2 UART3_TX UART2_TX -
 Kernel console params(4)
4 - - - -
 -
5 GND - - -
 -
6 GND - - -
 -
7 - - - -
 -
8 RS232_TX1 UART1_TX UART3_TX RS485 interface(5)
 -
9 RS232_RX1 UART1_RX UART3_RX RS485 interface(5)
 -
10 - - - -
 -


- Don't use the same peripheral in more than one pad.

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

console=ttyS2,115200n8

Replace by: 

; console=ttyS2,115200n8

(5): Allows to use UART1 as RS232 instead of EI485, edit igep.ini:

Search line: 

board.ei485=yes

Replace by: 

board.ei485=no

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:

-Debug the software of an embedded system directly
-Storing firmware
-Boundary scan testing

More information: 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.

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:

- Can handle up to 8 x 8 keypads, IGEPv2 can handle up to 4 x 4 keypads.
- Optionally, you can decode via Omap software.
- Event detection on key press and key release.
- Multikey press detection, can detect up 2  keys at the same time.
- Long-key detection on prolonged key press.
- Programmable time-out on permanent key press or after keypad release.

More information in TPS65950 datasheets.

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.

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.
- Pad 2 can be used to reset wifi module if RD43 is short circuit, replace RD44 for this porpouse.
- 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.
- 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.

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

Pad: Connect to:

Default peripheral (mode=0)

Default function: Other available peripherals: Share with:
1 VIO 1V8 - Power 1v8 - -
2 SYS_BOOT5

SYS_BOOT5

 Omap boot config

MMC2_DIR_DAT3

GPIO_7 (mode=4)

-
3 DC_5V - Power 5v -
-
4 GND - GND -

-
5 SYS_BOOT0

SYS_BOOT0

 Omap boot config

GPIO_2 (mode=4)


-

6 SYS_BOOT1

SYS_BOOT1

 Omap boot config

GPIO_3 (mode=4)

-

7 DVI_VSYNC DSS_VSYNC LCD vertical sync (Expansion)

GPIO_68(mode=4)


TFP410 (6)
8 DVI_HSYNC DSS_HSYNC LCD Horitzontal sync (Expansion)

GPIO_67 (mode=4)

TFP410 (6)
9 DVI_ACBIAS DSS_ACBIAS LCD Control (Expansion)   GPIO_133(mode=4)

TFP410 (6)
10 DVI_PUP - Control signal for DVI controler (Expansion) -

TFP410 (6)
11 DVI_PCLK DSS_PCLK LCD clock (Expansion)

GPIO_66 (mode=4)

TFP410 (6)
12 TS_nPEN_IRQ McSPI1_CS1 Touchscreen control (Expansion)

MMC3_CMD

GPIO_175 (mode=4)



13 LCD_QVGA/nVGA McBSP4_DX Touchscreen control (Expansion)

GPIO_154 (mode=4)

14 LCD_ENVDD McBSP4_DR Touchscreen control (Expansion)

GPIO_153 (mode=4)
15 LCD_RESB McBSP4_FSX Touchscreen control (Expansion)

GPIO_155 (mode=4)



16 LCD_INI McBSP4_CLKX Touchscreen control (Expansion)

GPIO_152 (mode=4)

17 MCSPI1_CLK

McSPI1_CLK

 Touchscreen control (Expansion)

GPIO_171 (mode=4)

-
18 MCSPI1_SIMO McSPI1_SIMO Touchscreen control (Expansion)

GPIO_172 (mode=4)

-
19 MCSPI1_CS0 McSPI1_CS0 Touchscreen control (Expansion)

GPIO_174 (mode=4)

-
20 MCSPI1_SOMI McSPI1_SOMI Touchscreen control (Expansion)

GPIO_173 (mode=4)

-


(6): TFP410: Converts DVI signal to HDMI. They share the same video signal.

JA41 connector

JA41 is used for DVI (Digital Video Interface) data part.

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

Pad: Connect to:

Default peripheral (mode=0)

Default function: Other available peripherals: Share with:
1 VIO 3V3 - Power 3v3 - -
2 GND

-

 GND

-

 -
3 DVI_DATA0 - DSS_D0
-
-
4 DVI_DATA1 DSS_D1
-

-
5 DVI_DATA2

 DSS_D2


GPIO_2 (mode=4)


-

6 DVI_DATA3

 DSS_D3


GPIO_3 (mode=4)

-

7 DVI_DATA4 DSS_D4

GPIO_68(mode=4)


TFP410 (6)
8 DVI_DATA5 DSS_D5

GPIO_67 (mode=4)

TFP410 (6)
9 DVI_DATA6 DSS_D6   GPIO_133(mode=4)

TFP410 (6)
10 DVI_DATA7 DSS_D7
-

TFP410 (6)
11 DVI_DATA8 DSS_D8

GPIO_66 (mode=4)

TFP410 (6)
12 DVI_DATA9 DSS_D9

MMC3_CMD

GPIO_175 (mode=4)



13 DVI_DATA10 DSS_D10

GPIO_154 (mode=4)

14 DVI_DATA11 DSS_D11

GPIO_153 (mode=4)
15 DVI_DATA12 DSS_D12

GPIO_155 (mode=4)



16 DVI_DATA13 DSS_D13

GPIO_152 (mode=4)

17 DVI_DATA14

DSS_D14


GPIO_171 (mode=4)

-
18 DVI_DATA15 DSS_D15

GPIO_172 (mode=4)

-
19 DVI_DATA16 DSS_D16

GPIO_174 (mode=4)

-
20 DVI_DATA17 DSS_D17

GPIO_173 (mode=4)

-
21
 DVI_DATA18 DSS_D18


22
 DVI_DATA19 DSS_D19


23
 DVI_DATA20 DSS_D20


24
 DVI_DATA21 DSS_D21


25
 DVI_DATA22
 DSS_D22


26
 DVI_DATA23
 DSS_D23


27
 I2C3_SCL
 I2C3_SCL


28
 I2C3_SDA
 I2C3_SDA



(6): TFP410: Converts DVI signal to HDMI. They share the same video signal.

Under construction

Retrieved from "http://labs.isee.biz/index.php?title=Mux_configuration&oldid=2905"