= 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:
{| cellspacing="1" cellpadding="1" border= J990 connector =="1" align="center"|-| [[Image:Mux register.png]]|} <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>
-There The functional bits of a pad configuration register field are some peripherals than can be connected to J990 like mm3 and camera, but is not used in this how-to. divided into the following five fields:
-High Speed USB • '''MUXMODE''' (3 is only available bits) defines the multiplexing mode applied to the pin. A mode corresponds to the selection of the functionality mapped on Omap 3530 in the next pads: pin with six (0 to 5) possible functional modes for each pin.
3• '''PULL''' (2 bits) for combinational pullup/pulldown configuration: HSUSB3_TLL_NXT<br> 4: HSUSB3_TLL_D4<br> 5: HSUSB3_TLL_DIR <br> 6: HSUSB3_TLL_D6<br> 7: HSUSB3_TLL_STP<br> 8: HSUSB3_TLL_D7 <br> 10: HSUSB3_TLL_D5
-> PULLTYPESELECT: Pullup/pulldown selection for the pin.
-> PULLUDENABLE: Pullup/pulldown enable for the pin.
{| cellspacing="• '''INPUTENABLE''' (1" cellpadding="1" border="1" align="JUSTIFY" style="width: 960px; height: 1463px;"|-| Pad: | Connect bit) drives an input enable signal to: | Default peripheral (mode=0) the I/O CTRL.
| Default function: | Other available peripherals: | style="text• '''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-alignup detection feature. For input pins, OFFOUTENABLE and OFFOUTVALUE bits can not be configured: 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(->OFFENABLE: Off mode=3) pin state override control. Set to 1 to enable the feature and to 0 to disable it.
GPIO_139(->OFFOUTENABLE: Off mode=4) output enable value. Set to 0 to enable the feature and to 1 to disable it.
| <div align="JUSTIFY">'''Wlan:''' This pad can reset Wlan peripheral using Omap GPIO low level (GND). If you reset continuously Wlan all their pads are in High Impedance. Also you can disable Wlan from J990 low level.</div> <div align="JUSTIFY">'''Omap: '''protect Omap pad if you don't use it.'''(1)'''</div>|-| 5 | MMC2_DAT6 | MMC2_DAT6 | Power down gt; Wlan | MMC2_DIR_CMD(OFFOUTVALUE: Off mode=1) output value.
MMC3_DAT2(->OFFPULLUDENABLE: Off mode=3) pullup/pulldown enable.
GPIO_138(->OFFPULLTYPESELECT: Off mode=4) pullup/pulldown selection.
| <div align="JUSTIFY">• '''Wlan:Wake-up''' This pad can power down Wlan peripheral using Omap GPIO low level bits (GND2 bits), 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>|-| 7 | MMC2_DAT5 | MMC2_DAT5 | Reset Bluethoot | MMC2_DIR_DAT1(mode=1)
MMC3_DAT1(->WAKEUPENABLE: Enable wake-up detection on input. It is also the off mode=3) input enable value.
GPIO_137(mode=4) ->WAKEUPEVENT: Wake-up event status for the pin.'''<br>'''
{| <div cellspacing="1" cellpadding="1" border="1" align="JUSTIFYcenter" width="200">'''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
| MMC2_DAT4
| MMC2_DAT4
| -
|
MMC_DIR_DAT0(mode=1) [[Image:Mux pad configuration diagram.png]] |}
MMC3_DAT0(mode=3) == Mode selection ===
GPIO136(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">'''Omapstyle="width: 287px; height: '''protect Omap pad if you don't use it.'''(1)'''</div>235px;"|-| MUXMODE | Select Mode
|-
| 11 0b000=0 | Mode 0 (Primary mode)| MMC2_DAT3 -| MMC2_DAT3 0b001=1 | Mode 1 (Possible mode)<br>| Transfer data between Omap and Wlan -| 0b010=2 McSPI3_CS0| Mode 2 (Possible mode=1) |-GPIO_135| 0b011=3 | Mode 3 (Possible mode=4) |-| <div align0b100="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.'''4 | Mode 4 (1Possible mode)'''</div>
|-
| 13 | MMC2_DAT2 | MMC2_DAT2 0b101=5 | Transfer data between Omap and Wlan | McSPI3_CS1(mode=1)<br> GPIO_134Mode 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>
|-
| 15 | MMC2_DAT1 | MMC2_DAT1 | Transfer data between Omap and Wlan 0b110=6 | GPIO_133Mode 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>
|-
| 17 0b111=7 | MMC2_DAT0 Mode 7 (Safe Mode)<br>| MMC2_DAT0 }| Transfer data between Omap and Wlan | McSPI3_SOMI(mode=1) '''Definitions:'''
GPIO_132('''Mode 0''' is the primary mode=4) . When mode 0 is set, the function mapped to the pin corresponds to the name of the pin. In IGEP some pads don't use primary mode by default.
| <div align="JUSTIFY">'''Wlan: Mode 1 to mode 6'''Protect Wlan if you don' use itare possible modes for alternate functions. See MMC2_DAT7 padOn each pin, some modes are used effectively for alternate functions, while other modes are unused and correspond to no functional configuration.</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)
GPIO_131'''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>
| <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) Pull Selection ===
GPIO_130(mode=4) The next table shows all capabilities.
{| <div aligncellspacing="JUSTIFY1" cellpadding="1">'''Wlan: '''Protect Wlan if you don' use it. See MMC2_DAT7 pad.</div> <div alignborder="JUSTIFY1" style=">'''Omapwidth: 696px; height: '''protect Omap pad if you don't use it.'''(1)'''</div>1px;"
|-
| 4 PULLTYPESELECT | MCBSP3_DX PULLUDENABLE | MCBSP3_DX Pin Behavior| Transmitted serial Data (Bluethoot audio) -| 0b0 UART2_CTS(mode=1) | 0b0 | Pull-down selected but not activated|-| 0b0 | 0b1 | Pull-down selected and activated if pin is NOT configured as OUTPUT|-| 0b1 | 0b0 | Pull-up selected but not activated|-| 0b1 | 0b1 | Pull-up selected and activated if pin is NOT configured as OUTPUT|}
GPIO_140(When a pin is in output mode=4) , pulls are automatically disable.
| <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) | UART2_TX(mode=1) = Input Enable ===
GPIO_142(INPUTENABLE = 0: Input Disable. Pin is configured in output only mode=4) .
| <div alignINPUTENABLE ="JUSTIFY">'''Bluethoot1: '''Protect Bluethoot if you don' use itInput Enable. See MMC2_DAT5 padPin is configured in bidirectional mode.</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(=== '''Off modevalues''' and '''Wake-up''' ===4)
| <div align="JUSTIFY">'''Bluethoot: '''Protect Bluethoot if you don' use itThis mode is used to disable some pins and reduce power consumption. 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) Please contribute.
| <div align="JUSTIFY">'''TPS65950[http:''' disable it via kernel '''(2) '''If you don't use it//www.ti.<com/lit/ug/spruf98x/div>|-| 12 | MCBSP1_DX | MCBSP1_DX | Transmited serial Data (not used) | McSPI4_SIMO(mode=1) spruf98x.pdf More information] about mux.
McBSP3_DX(mode=2) Configure Mux =
GPIO_158(mode=4) Mux options are vast, at the beginning can be difficult and tedious change some configurations. Before configure mux, use the following tips to avoid problems:
*Mux can connect multiple connectors at the same peripheral, this improper use can damage the processor. Before configure mux, revise that this peripheral is not used in other pads. See schematics or [[Connectors Summary| -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| 14 connectors summary]] or [[Mux_instructions#Disable_Peripherals| MCBSP1_CLKX how-to disable peripherals]] or [[How_to_use_GPIOs| MCBSP1_CLKX | Transmited serial clock (not used) | McBSP3_CLKX(mode=2)<br> how-to use gpios]] for more information.
GPIO_162(mode=4) == IGEPv2 ===
| -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>|-| 16 | MCBSP1_FSX | MCBSP1_FSX | Transmited Frame Syncronization (not used) | McSPI4_CS0(mode=1) There are some connectors than have more peripherals available, but they don't have all signals to use it. <br> Table shows four answers:
McBSP3_FSX*"'''Yes, default configuration(mode=2utility) '''": 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'''"
GPIO_161(mode{| cellspacing="1" cellpadding="1" border="1" style=4) "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]])
|-
| 18 [[Peripherals Summary#UART| MCBSP1_DR UART2]] | MCBSP1_DR Yes, not default configuration ([[How to set up UART2 in J990| Received Serial Data (not useddisable Bluetooth]])
|
McSPI4_SOMI(mode=1) No, [[How to use UARTs#RS232_Schematic_Igep_V2|via hardware]],
McBSP3_DR(mode=2) [[Mux instructions#Bluetooth|disable Bluetooth]]
GPIO_159| No | No | No | No | No|-| [[Peripherals Summary#UART|UART3]] | No | Yes, default configuration (mode=4[[Mux instructions#UART3_in_J960|Serial debug]]) | No | No | No | No | Yes, not default configuration ([[Mux_instructions#TFP410|disable DVI]])| -<br>| [[Peripherals Summary#UART|UART4]] | No | No | No | No | No | No | No
|-
| 20 [[Peripherals Summary#GPIO| MCBSP1_CLKR | MCBSP1_CLKR | Received Clock (not used) GPIO]]
|
GPIO_156Yes, default configuration (mode=4[[Mux instructions#GPIO_in_J990|info]])<br>
| -<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]])
|-
| 22 [[Peripherals Summary#SPI|McSPI1]] | MCBSP1_FSR No | MCBSP1_FSR No | Received frame syncronization (not used) No | No | No | Yes, default configuration | No|-| [[Peripherals Summary#SPI|McSPI2]] | No | No | No | No | No | No | No|-| [[Peripherals Summary#SPI|McSPI3]]
|
GPIO_157Yes, not default configuration (mode=4[[Mux instructions#WIFI|disable WIFI]])<br>
| -No | No | No | No | No | Yes, not default configuration ([[Mux_instructions#TFP410|disable DVI]])<br>|-| [[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
|-
| 23 [[Peripherals Summary#MMC|MMC2]] | I2C2_SDA Yes, default configuration ([[Mux instructions#WIFI|WIFI]]) | I2C2_SDA No | I2C Data No | No GPIO_183(mode=4)<br> | No | No | <div align="JUSTIFY">'''Cam connector:''' Check and RC14 is not welded or don't use it.<br></div>No
|-
| 24 [[Peripherals Summary#MMC|MMC3]] | I2C2_SCL No | I2C2_SCL No | I2C Clock No | No GPIO_168(mode=4)<br> | No | No | '''Cam connector:''' Check and RC13 is not welded or don't use it.No
|-
| 25 [[Peripherals Summary#I2C|I2C1]] | No | No | REGEN No | - No | Master/Slave control power TPS65950<br> No | - No | -<br>No
|-
| 26 [[Peripherals Summary#I2C|I2C2]] | Yes, default configuration | No | nRESET No | - No | Read Reset Omap No, [[Connectors Summary#JC30_connector|via hardware]] | - No | -<br>No
|-
| 27 [[Peripherals Summary#I2C|I2C3]] | No | No | GND No | - No | GND No | - No | -<br>Yes, default configuration (DVI)
|-
| 28 [[Peripherals Summary#I2C|I2C4]] | No | No | GND No | - No | GND No | - No | -<br>No
|}
'''(1):''' To protect Omap pads from esternal signals configure Mux in mode=7 (safe_mode). With this mode, buffer is configured in high impedance == IGEP MODULE ===
'''(2):''' Disable TPS65950 go Next table pretends help you to file soundconfigure IGEP MODULE. First column shows some OMAP35xx/soc/codecs/twl4030DM37xx peripherals and first row shows all IGEP MODULE connectors. Read articles about connector and peripheral before use them. Each configuration can take different solutions.c change line 54 Code: <prebr>0x00There are some connectors than have more peripherals available, /* REG_VOICE_IF (0xF) */</pre> but they don't have all signals to Code: use it. <prebr>0x04, /* REG_VOICE_IF (0xF) */</pre> '''(3)Table shows four answers:''' Omap mux have 8 modes, somes modes are disable in some pads.
=== J960 connector ===*"'''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'''"
J960 connector can not use mux capabilities, because this connector is dedicated to use RS232 comunication. Default hardware/software configuration is:<span lang="en" id="result_box"><span class="hps"></span></span><br> {| cellspacing="1" cellpadding="1" border="1" style="width: 498px933px; height: 381px190px;"|-| <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
|-
| Pad | Connect to: [[Peripherals Summary#BSP| Default periphera: McBSP2]] | Other peripheral: No | Share with:<br> No | Default function:<br>No
|-
| 1 | - [[Peripherals Summary#BSP| - McBSP3]] | - Yes, not default configuration (disable UART2) | -<br> No | <br>No
|-
| 2 [[Peripherals Summary#BSP| RS232_RX2 McBSP4]] | UART3_RX No | UART2_RX Yes, not default configuration (disable GPMCs) | -<br> | Kernel console params'''(4)'''<br>No
|-
| 3 [[Peripherals Summary#BSP| RS232_TX2 McBSP5]] | UART3_TX No | UART2_TX Yes, not default configuration (disable GPIOs) | -<br> | Kernel console params'''(4)'''<br>No
|-
| 4 | - [[Peripherals Summary#MMC| - MMC1]] | - No | -<br> No | -<br>No
|-
| 5 | GND [[Peripherals Summary#MMC| - MMC2]] | - No | -<br> No | -<br>No
|-
| 6 | GND [[Peripherals Summary#MMC| - MMC3]] | - No | -<br> No | -<br>Yes, not default configuration (disable GPIOs)
|-
| 7 | - [[Peripherals Summary#I2C| - I2C1]] | - No | -<br> No | -<br>No
|-
| 8 | RS232_TX1 [[Peripherals Summary#I2C| UART1_TX I2C2]] | UART3_TX No | RS485 interface'''(5)'''<br> No | -<br>No
|-
| 9 [[Peripherals Summary#I2C| RS232_RX1 I2C3]] | UART1_RX Yes, default configuration (J5) | UART3_RX No | RS485 interface'''Yes, default configuration (5J1)'''<br> | -<br>
|-
| 10 | - [[Peripherals Summary#I2C| - I2C4]] | - No | -<br> No | -<br>No
|}
<br> - 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[[Category: Work_in_progress]] 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[Category://es.wikipedia.org/wiki/JTAG http://es.wikipedia.org/wiki/JTAGPeripherals]]. 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 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 datasheets. <br> === JC30 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 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 datasheets.
