Explanation = Overview =
{| border="1" align="center" width="200" cellspacing="1" cellpadding="1"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>|-| Pad: *Mux characteristics summary| Connect *Tips to: avoid problems| Default peripheral (mode=0) | Default function: *Ways to configure mux| Other available *Tables that links peripherals: and connectors for IGEPv2 and IGEP MODULE| Share with:|-| 1 | VIO 1V8 | - | Power 1v8 | - | |-| 2 | DC 5V | - | Power 5v | - | |-| 3 | MMC2_DAT7 | MMC2_DAT7 | Reset Wlan | MMC2_CLKIN(mode=1) There are three ways to configure mux in IGEP Boards based in OMAP35xx and DM37xx:<br>
MMC3_DAT3(*[[Mux_instructions|Configuring MUX from OS User Space]]. This mode=3) 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>
GPIO_139(mode=4)
| <div align="JUSTIFY"><font sizeIntroduction ="2">'''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.</font></div> <div align="JUSTIFY"><font size="2">'''Omap: '''<span style="font-weight: normal">protect Omap pad if you don'tuse it.</span>'''(1)'''</font></div> |-| 5 | MMC2_DAT6 | MMC2_DAT6 | Power down Wlan | MMC2_DIR_CMD(mode=1)
MMC3_DAT2Mux (mode=3or multiplexer) is a Omap peripheral that can be controlled via software. Its function is connect other peripherals to some available Omap pins.
GPIO_138(mode=4) Each pin is configurable by software using its associated pad configuration register field, which is 16 bits wide:
{| <div aligncellspacing="JUSTIFY1"><font sizecellpadding="21">'''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.</font></div> <div alignborder="JUSTIFY1"><font sizealign="2center">'''Omap: '''<span style="font-weight: normal">protect Omap pad if you don'tuse it.</span>'''(1)'''</font></div>
|-
| 7 [[Image:Mux register.png]]| MMC2_DAT5 }| MMC2_DAT5 | Reset Bluethoot | MMC2_DIR_DAT1(mode=1) <br> One pad configuration register field is available for each pin. Each 32-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>
MMC3_DAT1(mode=3) The functional bits of a pad configuration register field are divided into the following five fields:
GPIO_137• '''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"><font size="2">• '''Bluethoot: PULL'''<span style="font-weight: normal">This pad can reset Bluethootperipheral using Omap GPIO low level (GND2 bits). If you reset continuouslyBluethoot all their pads are in High Impedance. Also you can disableBluethoot from J990 low level.<for combinational pullup/span></font></div> <div align="JUSTIFY"><font size="2">'''Omap: '''<span style="font-weightpulldown configuration: normal">protect Omap pad if you don'tuse it.</span>'''(1)'''</font></div> |-| 9 | MMC2_DAT4 | MMC2_DAT4 | - | MMC_DIR_DAT0(mode=1)
MMC3_DAT0(mode=3) -> PULLTYPESELECT: Pullup/pulldown selection for the pin.
GPIO136(mode=4) -> PULLUDENABLE: Pullup/pulldown enable for the pin.
| <div align="JUSTIFY"><font size="2">• '''Wlan: '''<span style="font-weight: normal">Protect Wlan if you don' useit. See MMC2_DAT7 pad.</span></font></div> <div align="JUSTIFY"><font size="2">'''Omap: '''<span style="font-weight: normal">protect Omap pad if you don'tuse it.</span>INPUTENABLE'''(1bit)'''<drives an input enable signal to the I/font></div> |-| 11 | MMC2_DAT3 | MMC2_DAT3 | (1)Transfer data between Omap and Wlan | McSPI3_CS0(mode=1)O CTRL.
GPIO_135• '''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=4)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:
| <div align="JUSTIFY"><font size="2">'''<br>'''<span style="font-weight>OFFENABLE: normal" /></font></div> |-| 13 | MMC2_DAT2 | MMC2_DAT2 | (1) | McSPI3_CS1(Off mode=pin state override control. Set to 1)to enable the feature and to 0 to disable it.
GPIO_134(->OFFOUTENABLE: Off mode=4)output enable value. Set to 0 to enable the feature and to 1 to disable it.
| |-| 15 | MMC2_DAT1 | MMC2_DAT1 | (1) | GPIO_133(>OFFOUTVALUE: Off mode=4)| |-| 17 | MMC2_DAT0 | MMC2_DAT0 | (1) | McSPI3_SOMI(mode=1)output value.
GPIO_132(->OFFPULLUDENABLE: Off mode=4)pullup/pulldown enable.
| <br>|-| 19 | MMC2_CMD | MMC2_CMD | Control Wire for bus MMC2 (Wlan) | McSPI3_SIMO(>OFFPULLTYPESELECT: Off mode=1)pullup/pulldown selection.
GPIO_131• '''Wake-up''' bits (mode=42 bits):
| |-| 21 | MMC2_CLK0 | MMC2_CLK | Clock for MMC2 (Wlan) | McSPI3_CLK(>WAKEUPENABLE: Enable wake-up detection on input. It is also the off mode=1)input enable value.
GPIO_130(mode=4)->WAKEUPEVENT: Wake-up event status for the pin.'''<br>'''
{| cellspacing="1" cellpadding="1" border="1" align="center" width="200"
|-
| 4
| MCBSP3_DX
| MCBSP3_DX
| Transmitted serial Data (Bluethoot audio)
|
UART2_CTS(mode=1)[[Image:Mux pad configuration diagram.png]]
GPIO_140(mode=4)|}
| <div align="JUSTIFY"><font size="2">'''TPS65950:''' disable it via kernel '''(2) '''<span style="font-weight: normal">Ifyou don't use it.</span></font></div>|-| 6 | MCBSP3_CLKX | MCBSP3_CLKX | Transmitted serial Clock (Bluethoot audio) | UART2_TX(modeMode selection ===1)
GPIO_142(mode=4)The next table shows all capabilities.<br>
{| <div aligncellspacing="JUSTIFY1"><font sizecellpadding="21" border="1">'''Bluethoot: '''<span style="font-weightwidth: 287px; height: normal235px;">Protect Bluethoot if you don'use it. See MMC2_DAT5 pad.</span></font></div> <div align|-| MUXMODE | Select Mode|-| 0b000="JUSTIFY"><br> </div> <div align="JUSTIFY"><font size="2">'''TPS65950:''' disable it via kernel '''0 | Mode 0 (2Primary mode) '''<span style="font-weight: normal">Ifyou don't use it.</span></font></div>
|-
| 8 0b001=1 | Mode 1 (Possible mode)<br>| MCBSP3_FSX -| MCBSP3_FSX 0b010=2 | Transmited Frame Syncronisation Mode 2 (Bluethoot audioPossible mode) | -UART2_RX| 0b011=3 | Mode 3 (Possible mode)|-| 0b100=14 | Mode 4 (Possible mode)|-| 0b101=5 | Mode 5 (Possible mode)|-| 0b110=6 | Mode 6 (Possible mode)|-| 0b111=7 | Mode 7 (Safe Mode)<br>|}
GPIO_143(mode=4)'''Definitions:'''
| <div align="JUSTIFY"><font size="2">'''Bluethoot: Mode 0'''<span style="font-weight: normal">Protect Bluethoot if you don'use itis the primary mode. See MMC2_DAT5 padWhen mode 0 is set, the function mapped to the pin corresponds to the name of the pin.</span></font></div> <div align="JUSTIFY"><br> </div> <div align="JUSTIFY"><font size="2">'''TPS65950:''' disable it via kernel '''(2) '''<span style="font-weight: normal">Ifyou In IGEP some pads don't use itprimary mode by default.</span></font></div> |-| 10 | MCBSP3_DR | MCBSP3_DR | Received Serial Data (Bluethoot audio) | UART2_RTS(mode=1)
GPIO_141('''Mode 1 to mode=4)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.
| <div align="JUSTIFY"><font size="2">'''TPS65950:''' disable it via kernel '''The safe mode (2default mode 7) '''<span style="fontavoids 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-weight: normal">Ifyou don't use iton reset.</span></font></divbr> |-| 12 | MCBSP1_DX | MCBSP1_DX | Transmited serial Data (not used) | McSPI4_SIMO(mode=1)
McBSP3_DX(mode=2)== Pull Selection ===
GPIO_158(mode=4)The next table shows all capabilities.
{| cellspacing="1" cellpadding="1" border="1" style="width: 696px; height: 1px;"|-| PULLTYPESELECT | PULLUDENABLE | Pin Behavior|-| 0b0 | 0b0 | Pull-down selected but not activated|-| 0b0 | 0b1 | Pull-down selected and activated if pin is NOT configured as OUTPUT
|-
| 14 0b1 | MCBSP1_CLKX 0b0 | MCBSP1_CLKX | {| border="1" align="center" width="200" cellspacing="1" cellpadding="1"Pull-up selected but not activated
|-
| 0b1 | 0b1 | Pull-up selected and activated if pin is NOT configured as OUTPUT
|}
| When a pin is in output mode, pulls are automatically disable. === Input Enable === INPUTENABLE = 0: Input Disable. Pin is configured in output only mode. INPUTENABLE = 1: Input Enable. Pin is configured in bidirectional mode.<br> McBSP3_CLKX(=== '''Off modevalues''' and '''Wake-up''' ===2) This mode is used to disable some pins and reduce power consumption. <br> Please contribute.
GPIO_162(mode=4)[http://www.ti.com/lit/ug/spruf98x/spruf98x.pdf More information] about mux.
| |-| 16 | MCBSP1_FSX | MCBSP1_FSX | Transmited Frame Syncronization (not used) | McSPI4_CS0(mode=1)Configure Mux =
McBSP3_FSX(mode=2)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:
GPIO_161(mode=4)*Mux can connect multiple connectors at the same peripheral, this improper use can damage the processor. Before configure mux, revise that this peripheral is not used in other pads. See schematics or [[Connectors Summary|connectors summary]] for more information. *Some peripherals are only available if you place or replace some resistances. See schematics for more information.<br> *Some connectors share multiples peripherals like OMAP, WIFI/BT combo, etc. You should disable unused peripherals to avoid interferences. 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.
| |-| 18 | MCBSP1_DR | MCBSP1_DR | Received Serial Data (not used) | McSPI4_SOMI(mode=1)== IGEPv2 ===
McBSP3_DR(mode=2)Next 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, but they don't have all signals to use it. <br> Table shows four answers:
GPIO_159*"'''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'''"
{| cellspacing="1" cellpadding="1" border="1" style="width: 933px; height: 409px;"|-| <br> | [[Connectors Summary#J990_connector|J990]] | [[Connectors Summary#J960_connector|J960]] | [[Connectors Summary#J970_connector|J970]] | [[Connectors Summary#J400_connector|J400]] | [[Connectors Summary#JC30_connector|JC30]] | [[Connectors Summary#JA42_connector|JA42]] | [[Connectors Summary#JA41_connector|JA41]]|-| [[Peripherals Summary#UART|UART1]] | No | Yes, not default configuration ([[Mux instructions#UART1_in_J960|disable RS485]]) | No | No | No | No | Yes, not default configuration ([[Mux_instructions#TFP410|disable DVI]])
|-
| 20 [[Peripherals Summary#UART| MCBSP1_CLKR UART2]] | MCBSP1_CLKR Yes, not default configuration ([[How to set up UART2 in J990| Received Clock (not useddisable Bluetooth]])
|
GPIO_156(mode=4)<br>No, [[How to use UARTs#RS232_Schematic_Igep_V2|via hardware]],
[[Mux instructions#Bluetooth| disable Bluetooth]] | No | No | No | No | No|-| [[Peripherals Summary#UART|UART3]] | No | Yes, default configuration ([[Mux instructions#UART3_in_J960|Serial debug]]) | No | No | No | No | Yes, not default configuration ([[Mux_instructions#TFP410|disable DVI]])|-| [[Peripherals Summary#UART|UART4]] | No | No | No | No | No | No | No
|-
| 22 [[Peripherals Summary#GPIO| MCBSP1_FSR | MCBSP1_FSR | Received frame syncronization (not used) GPIO]]
|
GPIO_157Yes, default configuration (mode=4[[Mux instructions#GPIO_in_J990|info]])<br>
| No | No | Yes, not default configuration ([[Mux instructions#GPIO_in_J990|disable JTAG]]) | Yes, default configuration | Yes, default configuration | Yes, not default configuration ([[Mux_instructions#TFP410|disable DVI]])|-| [[Peripherals Summary#SPI|McSPI1]] | No | No | No | No | No | Yes, default configuration | No|-| [[Peripherals Summary#SPI|McSPI2]] | No | No | No | No | No | No | No
|-
| 23 [[Peripherals Summary#SPI| I2C2_SDA | I2C2_SDA | I2C Data McSPI3]]
|
GPIO_183Yes, not default configuration (mode=4[[Mux instructions#WIFI|disable WIFI]])<br>
| <div align="JUSTIFY"><font size="2">'''Cam connector:''' Check RC13 and RC14 is No | No | No | No | No | Yes, not welded or don't use it.default configuration ([[Mux_instructions#TFP410|disable DVI]])<br></font></div> |-| [[Peripherals Summary#SPI|McSPI4]] | Yes, not default configuration ([[Mux instructions#GPIO_in_J990|disable GPIOs]]) | No | No | No | No | No | No|-| [[Peripherals Summary#BSP|McBSP1]] | Yes, not default configuration ([[Mux instructions#GPIO_in_J990|disable GPIOs]]) | No | No | No | No | No | No|-| [[Peripherals Summary#BSP|McBSP2]] | No | No | No | No | No | No | No|-| [[Peripherals Summary#BSP|McBSP3]] | Yes, default configuration ([[Mux instructions#TP65950_PCM_VSP|Bluetooth audio]]) | No | No | No | No | No | No|-| [[Peripherals Summary#BSP|McBSP4]] | No | No | No | No | No | Yes, not default configuration ([[Mux instructions#GPIO_in_J990|disable GPIOs]]) | No|-| [[Peripherals Summary#BSP|McBSP5]] | No | No | No | No | No | No | No|-| [[Peripherals Summary#MMC|MMC1]] | No | No | No | No | No | No | No|-| [[Peripherals Summary#MMC|MMC2]] | Yes, default configuration ([[Mux instructions#WIFI|WIFI]]) | No | No | No | No | No | No|-| [[Peripherals Summary#MMC|MMC3]] | No | No | No | No | No | No | No|-| [[Peripherals Summary#I2C|I2C1]] | No | No | No | No | No | No | No|-| [[Peripherals Summary#I2C|I2C2]] | Yes, default configuration | No | No | No | No, [[Connectors Summary#JC30_connector|via hardware]] | No | No|-| [[Peripherals Summary#I2C|I2C3]] | No | No | No | No | No | No | Yes, default configuration (DVI)
|-
| 24 [[Peripherals Summary#I2C|I2C4]] | No | I2C2_SCL No | I2C2_SCL No | I2C Clock No | No | No | No| } === IGEP MODULE === 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: GPIO_168*"'''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'''"
{| cellspacing="1" cellpadding="1" border="1" style="width: 933px; height: 190px;"|-| <br>| [[Connectors Summary#J1_connector|J1]] | [[Connectors Summary#J4_connector|J4]] | [[Connectors Summary#J5_connector|J5]]|-| [[Peripherals Summary#UART|UART1]] | Yes, not default configuration (disable DSS) | Yes, default configuration | No|-| [[Peripherals Summary#UART|UART2]] | Yes, not default configuration(enable: TX and RX) | No | No|-| [[Peripherals Summary#UART|UART3]] | Yes, default configuration | No | No|-| [[Peripherals Summary#UART|UART4]] | No | Yes, not default configuration(disable: GPIO_64 and GPMC_WAIT3) | No|-| [[Peripherals Summary#GPIO|GPIO]] | Yes, default configuration | Yes, default configuration | Yes, default configuration|-| [[Peripherals Summary#SPI|McSPI1]] | No | Yes, default configuration | No|-| [[Peripherals Summary#SPI|McSPI2]] | No | No | No|-| [[Peripherals Summary#SPI|McSPI3]] | Yes, not default configuration (disable DSS) | No | No|-| [[Peripherals Summary#SPI|McSPI4]] | No | No | No|-| [[Peripherals Summary#BSP|McBSP1]] | No | No | No|-| [[Peripherals Summary#BSP|McBSP2]] | No | No | No|-| [[Peripherals Summary#BSP|McBSP3]] | Yes, not default configuration (disable UART2) | No | No|-| [[Peripherals Summary#BSP|McBSP4]] | No | Yes, not default configuration (disable GPMCs) | No|-| [[Peripherals Summary#BSP|McBSP5]] | No | Yes, not default configuration (disable GPIOs) | No|-| [[Peripherals Summary#MMC|MMC1]] | No | No | No|-| [[Peripherals Summary#MMC|MMC2]] | No | No | No|-| [[Peripherals Summary#MMC|MMC3]] | No | No | Yes, not default configuration (disable GPIOs)
|-
| 25 | REGEN [[Peripherals Summary#I2C| - I2C1]] | No | -No | No
|-
| 26 | nRESET [[Peripherals Summary#I2C| - I2C2]] | Read Reset Omap No | -No | No
|-
| 27 | GND [[Peripherals Summary#I2C| - I2C3]] | GND Yes, default configuration (J5) | -No | Yes, default configuration (J1)
|-
| 28 | GND [[Peripherals Summary#I2C| - I2C4]] | GND No | -No | No
|}
Under construction[[Category:Work_in_progress]][[Category:Peripherals]]