Gumstix User Wiki - User contributions [en]

Duovero Multiplexes

2014-09-26T13:24:43Z

Conor O'Rourke: Small address error (0x138+2 = 13A not 140)

[[Category:How_to_-_linux]]
[[Category:Connect_hardware]]

This wiki entry concentrates on the Duovero Parlor board and the Multiplexes available from the 40 pin connector.

[[File:Duovero parlor conn small.png]]

The ground pin is nearest the console connector port and the power pins are nearest the centre of the board. This is as of writing but it is highly recommended that you ''check'' before connecting! Use a voltmeter to check the 3.3V, 5V and 1.8V pins to familiarise yourself with the layout.

There are also two connections on the Parlor board:

<blockquote>
{| class="wikitable"
|-
! OMAP Pin !! GPIO # !! Purpose
|-
| AG24 || GPIO121 || user push button
|-
| AH24 || GPIO122 || user LED
|}
</blockquote>

You should start your journey [http://gumstix.org/hardware-design/duovero-coms.html here].

The primary reference for multiplexes and pin functions is the Texas Instruments OMAP4 technical reference manual. The short version of that 6000 page manual is the OMAP4430 datasheet which is easier to search. The primary source reference is in the Uboot [https://github.com/gumstix/u-boot/tree/v2013.07/board/duovero code], specifically <tt>duovero_mux_data.h</tt> which uses the defines from <tt>./arch/arm/include/asm/arch-omap4/mux_omap4.h</tt>.

== Software Muxing ==

A helpful post from Phil Lutz describes how multiplexing can be explored without kernel recompilation. The default multiplex for the user LED may not be set to GPIO in Uboot. It certainly is not set to GPIO by the OMAP itself. You can look at the OMAP datasheet on page 48 you can see that the official name for GPIO 122 pin is "abe_dmic_din3" (Mode 0 names are accepted pin names).

This information can also be found by searching for "gpio_122" in the board pinmuxing configuration stored in sysfs: <tt>/sys/kernel/debug/omap_mux/board/core</tt>. Every pin which can be configured as gpio has a hint about that.

So now just check which is the current pinmuxing configuration for this pin by:

<pre>
$ cat /sys/kernel/debug/omap_mux/abe_dmic_din3
name: abe_dmic_din3.abe_dmic_din3 (0x4a100116/0x116 = 0x0100), b ah24, t NA
mode: OMAP_PIN_INPUT | OMAP_MUX_MODE0
signals: abe_dmic_din3 | slimbus2_data | abe_dmic_clk2 | gpio_122 | NA | dmtimer9_pwm_evt | NA | safe_mode
</pre>

As the output suggests, the pin is configured in MODE0, this is 'abe_dmic_din3'. The other modes are listed in order as they appear in the OMAP data manual. gpio_122 is multiplex MODE 3. You can set it with:

$ echo 3 > /sys/kernel/debug/omap_mux/abe_dmic_din3

Now you can turn on and off the LED using the usual gpio configuration in /sys/class/gpio/ (google it!). Note that "echo 3" does more than set Mode 3. The number is a selection of bits that set various states for the pin. A quick summary is:
<blockquote>
{| class="wikitable"
|-
|width="100pt" |Bit 0,1,2 || Set the mode
|-
|Bit 3 || 0 = pull up/down disabled , 1 = enabled
|-
|Bit 4 || 0 = pull down, 1 = pull up
|-
|Bit 8 || 0 = Output only. 1 = input enable (bidirectional)
|}
</blockquote>

There are more but these are for sleep modes and wakeup. The manual has details. The defines in mux_omap4.h are useful for interpreting the duovero_mux_data.h file:

<blockquote>

{| class="wikitable"
|-
|IEN || 1 << 8 || Input enable (bidirectional)
|-
|IDIS || 0 << 8 || Output only
|-
|PTU   || 3 << 3   || Enable Pullup
|-
|PTD || 1 << 3 || Enable Pulldown
|-
|EN || 1 << 3 || PU/PD enable
|-
|DIS || 0 << 3 || PU/PD disable
|}

</blockquote>

== Parlor pin mux table ==

To assist in figuring out which pins on the Parlor board can be assigned to which duties, here's a table of functions. Mode 7 is "safe_mode" where the pin is effectively disconnected from any functionality. It's set to high impedance (Z) and is left out of the table. The bolded functions are those set by the current U-Boot duovero_mux_data.h. This file sets other parameters (eg: output only, disable pullup/pulldown, etc) and you must refer to the U-Boot file to know what the full state is. A partial indication of the state (wake mode) is indicated in the table by arrows (bidirectional, output, pullup, pulldown).

Underneath the Connector entries are the IOPAD mux address offsets and under each gpio entry is the corresponding GPIO register and bit offset. These numbers are useful for device tree purposes. The gpio numbers are calculated simply as: <tt>register = int(gpionumber / 32) + 1</tt> and <tt>offset = gpionumber % 32</tt>.

{| class="wikitable"
|-
! Connector Description !! OMAP Pin !! Reset state !! Mode 0 !! Mode 1 !! Mode 2 !! Mode 3 !! Mode 4 !! Mode 5 !! Mode 6
|-
| User LEDa 0x116 || AH24 || M7, Pulldown   || '''abe_dmic_din3''' ⇔ || slimbus2_data || abe_dmic_clk2 || gpio_122 GPIO4[26] || - || dmtimer9_pwm_evt || -
|-
| Buttona 0x114 || AG24 || M7, Pulldown || '''abe_dmic_din2''' ⇔ || slimbus2_clock || abe_mcasp_axr || gpio_121 GPIO4[25] || - || dmtimer11_pwm_evt || -
|-
| 04: MCSPI1_CS0 0x138 || AE23 || M7, Pulldown || '''mcspi1_cs0''' ⇔↓ || - || - || gpio_137 GPIO5[9] || - || - || -
|-
| 06: MCSPI1_CS1 0x13A || AF23 || M7, Pulldown || '''mcspi1_cs1''' ⇔↓ || uart1_rx || - || gpio_138 GPIO5[10] || - || - || -
|-
| 08: MCSPI1_CS2 0x13C || AG23 || M7, Pullup || mcspi1_cs2 || uart1_cts || slimbus2_clock || gpio_139 GPIO5[11] || - || - || -
|-
| 10: MCSPI1_CS3 0x13E || AH23 || M7, Pullup || mcspi1_cs3 || uart1_rts || slimbus2_data || gpio_140 GPIO5[12] || - || - || -
|-
| 03: MCSPI1_CLK 0x132 || AF22 || M7, Pulldown || '''mcspi1_clk''' ⇔ || - || - || gpio_134 GPIO5[6] || - || - || -
|-
| 05: MCSPI1_SIMO 0x136 || AG22 || M7, Pulldown || '''mcspi1_simo''' ⇔ || - || - || gpio_136 GPIO5[8] || - || - || -
|-
| 07: MCSPI1_SOMI 0x134 || AE22 || M7, Pulldown || '''mcspi1_somi''' ⇔ || - || - || gpio_135 GPIO5[7] || - || - || -
|-
| 09: HDQ_SIOb 0x120 || AA27 || M7, Z || '''hdq_sio''' ⇒ || i2c3_sccb || i2c2_sccb || gpio_127 GPIO4[31] || - || - || -
|-
| 12: I2C2_SCLc 0x126 || C26 || M7, Pullup || '''i2c2_scl''' ⇔↑ || uart1_rx || - || gpio_128 GPIO5[0] || - || - || -
|-
| 14: I2C2_SDAc 0x128 || D26 || M7, Pullup || '''i2c2_sda''' ⇔↑ || uart1_tx || - || gpio_129 GPIO5[1] || - || - || -
|-
| 11: SDMMC3_CMD 0x174 || AG10 || M7, Pullup || usbb2_ulpitll_dat6 || usbb2_ulpiphy_dat6 || sdmmc3_cmd || '''gpio_167''' ⇔↑ GPIO6[7] || mcspi3_simo || dispc2_data12 || rfbi_data12
|-
| 13: SDMMC3_CLK 0x176 || AE9 || M7, Pullup || usbb2_ulpitll_dat7 || usbb2_ulpiphy_dat7 || sdmmc3_clk || '''gpio_168''' ⇔↑ GPIO6[8] || mcspi3_clk || dispc2_data11 || rfbi_data11
|-
| 15: UART2_TX 0x11E || AA26 || M7, Pullup || '''uart2_tx''' ⇒ || sdmmc3_dat1 || - || gpio_126 GPIO4[30] || - || - || -
|-
| 17: UART2_RX 0x11C || AA25 || M7, Pullup || '''uart2_rx''' ⇔↑ || sdmmc3_dat0 || - || gpio_125 GPIO4[29] || - || - || -
|-
| 19: BSP2_CLKX 0x0F6 || AD27 || M7, Pulldown || '''abe_mcbsp2_clkx''' ⇔ || mcspi2_clk || abe_mcasp_ahclkx || gpio_110 GPIO4[14] || usbb2_mm_rxdm || - || -
|-
| 20: BSP2_FSX 0x0FC || AC28 || M7, Pulldown || '''abe_mcbsp2_fsx''' ⇔ || mcspi2_cs0 || abe_mcasp_afsx || gpio_113 GPIO4[17] || usbb2_mm_txen || - || -
|-
| 21: BSP2_DX 0x0FA || AD25 || M7, Pulldown || '''abe_mcbsp2_dx''' ⇒ || mcspi2_simo || abe_mcasp_amute || gpio_112 GPIO4[16] || usbb2_mm_rxrcv || - || -
|-
| 22: BSP2_DR 0x0F8 || AD26 || M7, Pulldown || '''abe_mcbsp2_dr''' ⇔ || mcspi2_somi || abe_mcasp_axr || gpio_111 GPIO4[15] || usbb2_mm_rxdp || - || -
|-
| 23: BSP_CLKS 0x10E || AH26 || M7, Pulldown || '''abe_clks''' ⇔↓ || - || - || gpio_118 GPIO4[22] || - || - || -
|-
| 25: MCSPI4_SOMI 0x158 || AF21 || M7, Pullup || '''mcspi4_somi''' ⇔ || sdmmc4_dat0 || kpd_row6 || gpio_153 GPIO5[25] || - || - || -
|-
| 27: MCSPI4_SIMO 0x156 || AF20 || M7, Pullup || '''mcspi4_simo''' ⇔ || sdmmc4_cmd || kpd_col7 || gpio_152 GPIO5[24] || - || - || -
|-
| 29: MCSPI4_CLK 0x154 || AE21 || M7, Pulldown || '''mcspi4_clk''' ⇔ || sdmmc4_clk || kpd_col6 || gpio_151 GPIO5[23] || - || - || -
|-
| 31: MCSPI4_CS0 0x15A || AE20 || M7, Pullup || '''mcspi4_cs0''' ⇔↓ || sdmmc4_dat3 || kpd_row7 || gpio_154 GPIO5[26] || - || - || -
|}

=== Notes ===

a) Assigned as such in u-boot but reassigned in the kernel board startup code to Mode 3 Outputs

b) There is a 10K pull up to 1.8V, internal to the DuoVero COM, on the HDQ_SIO line. Do not enable a pull down on this line. This will result in a non-logic output level (approximately 1V). This is currently considered to be a bug and may be removed in future COM revisions.

c) There are pullups on I2C2 and I2C3 of approximately 1K. S/C current is over 2mA.

Duovero Multiplexes

2014-09-26T13:21:27Z

Conor O'Rourke: Addition of OMAP4_IOPAD address offsets for DTS purposes

[[Category:How_to_-_linux]]
[[Category:Connect_hardware]]

This wiki entry concentrates on the Duovero Parlor board and the Multiplexes available from the 40 pin connector.

[[File:Duovero parlor conn small.png]]

The ground pin is nearest the console connector port and the power pins are nearest the centre of the board. This is as of writing but it is highly recommended that you ''check'' before connecting! Use a voltmeter to check the 3.3V, 5V and 1.8V pins to familiarise yourself with the layout.

There are also two connections on the Parlor board:

<blockquote>
{| class="wikitable"
|-
! OMAP Pin !! GPIO # !! Purpose
|-
| AG24 || GPIO121 || user push button
|-
| AH24 || GPIO122 || user LED
|}
</blockquote>

You should start your journey [http://gumstix.org/hardware-design/duovero-coms.html here].

The primary reference for multiplexes and pin functions is the Texas Instruments OMAP4 technical reference manual. The short version of that 6000 page manual is the OMAP4430 datasheet which is easier to search. The primary source reference is in the Uboot [https://github.com/gumstix/u-boot/tree/v2013.07/board/duovero code], specifically <tt>duovero_mux_data.h</tt> which uses the defines from <tt>./arch/arm/include/asm/arch-omap4/mux_omap4.h</tt>.

== Software Muxing ==

A helpful post from Phil Lutz describes how multiplexing can be explored without kernel recompilation. The default multiplex for the user LED may not be set to GPIO in Uboot. It certainly is not set to GPIO by the OMAP itself. You can look at the OMAP datasheet on page 48 you can see that the official name for GPIO 122 pin is "abe_dmic_din3" (Mode 0 names are accepted pin names).

This information can also be found by searching for "gpio_122" in the board pinmuxing configuration stored in sysfs: <tt>/sys/kernel/debug/omap_mux/board/core</tt>. Every pin which can be configured as gpio has a hint about that.

So now just check which is the current pinmuxing configuration for this pin by:

<pre>
$ cat /sys/kernel/debug/omap_mux/abe_dmic_din3
name: abe_dmic_din3.abe_dmic_din3 (0x4a100116/0x116 = 0x0100), b ah24, t NA
mode: OMAP_PIN_INPUT | OMAP_MUX_MODE0
signals: abe_dmic_din3 | slimbus2_data | abe_dmic_clk2 | gpio_122 | NA | dmtimer9_pwm_evt | NA | safe_mode
</pre>

As the output suggests, the pin is configured in MODE0, this is 'abe_dmic_din3'. The other modes are listed in order as they appear in the OMAP data manual. gpio_122 is multiplex MODE 3. You can set it with:

$ echo 3 > /sys/kernel/debug/omap_mux/abe_dmic_din3

Now you can turn on and off the LED using the usual gpio configuration in /sys/class/gpio/ (google it!). Note that "echo 3" does more than set Mode 3. The number is a selection of bits that set various states for the pin. A quick summary is:
<blockquote>
{| class="wikitable"
|-
|width="100pt" |Bit 0,1,2 || Set the mode
|-
|Bit 3 || 0 = pull up/down disabled , 1 = enabled
|-
|Bit 4 || 0 = pull down, 1 = pull up
|-
|Bit 8 || 0 = Output only. 1 = input enable (bidirectional)
|}
</blockquote>

There are more but these are for sleep modes and wakeup. The manual has details. The defines in mux_omap4.h are useful for interpreting the duovero_mux_data.h file:

<blockquote>

{| class="wikitable"
|-
|IEN || 1 << 8 || Input enable (bidirectional)
|-
|IDIS || 0 << 8 || Output only
|-
|PTU   || 3 << 3   || Enable Pullup
|-
|PTD || 1 << 3 || Enable Pulldown
|-
|EN || 1 << 3 || PU/PD enable
|-
|DIS || 0 << 3 || PU/PD disable
|}

</blockquote>

== Parlor pin mux table ==

To assist in figuring out which pins on the Parlor board can be assigned to which duties, here's a table of functions. Mode 7 is "safe_mode" where the pin is effectively disconnected from any functionality. It's set to high impedance (Z) and is left out of the table. The bolded functions are those set by the current U-Boot duovero_mux_data.h. This file sets other parameters (eg: output only, disable pullup/pulldown, etc) and you must refer to the U-Boot file to know what the full state is. A partial indication of the state (wake mode) is indicated in the table by arrows (bidirectional, output, pullup, pulldown).

Underneath the Connector entries are the IOPAD mux address offsets and under each gpio entry is the corresponding GPIO register and bit offset. These numbers are useful for device tree purposes. The gpio numbers are calculated simply as: <tt>register = int(gpionumber / 32) + 1</tt> and <tt>offset = gpionumber % 32</tt>.

{| class="wikitable"
|-
! Connector Description !! OMAP Pin !! Reset state !! Mode 0 !! Mode 1 !! Mode 2 !! Mode 3 !! Mode 4 !! Mode 5 !! Mode 6
|-
| User LEDa 0x116 || AH24 || M7, Pulldown   || '''abe_dmic_din3''' ⇔ || slimbus2_data || abe_dmic_clk2 || gpio_122 GPIO4[26] || - || dmtimer9_pwm_evt || -
|-
| Buttona 0x114 || AG24 || M7, Pulldown || '''abe_dmic_din2''' ⇔ || slimbus2_clock || abe_mcasp_axr || gpio_121 GPIO4[25] || - || dmtimer11_pwm_evt || -
|-
| 04: MCSPI1_CS0 0x138 || AE23 || M7, Pulldown || '''mcspi1_cs0''' ⇔↓ || - || - || gpio_137 GPIO5[9] || - || - || -
|-
| 06: MCSPI1_CS1 0x140 || AF23 || M7, Pulldown || '''mcspi1_cs1''' ⇔↓ || uart1_rx || - || gpio_138 GPIO5[10] || - || - || -
|-
| 08: MCSPI1_CS2 0x13C || AG23 || M7, Pullup || mcspi1_cs2 || uart1_cts || slimbus2_clock || gpio_139 GPIO5[11] || - || - || -
|-
| 10: MCSPI1_CS3 0x13E || AH23 || M7, Pullup || mcspi1_cs3 || uart1_rts || slimbus2_data || gpio_140 GPIO5[12] || - || - || -
|-
| 03: MCSPI1_CLK 0x132 || AF22 || M7, Pulldown || '''mcspi1_clk''' ⇔ || - || - || gpio_134 GPIO5[6] || - || - || -
|-
| 05: MCSPI1_SIMO 0x136 || AG22 || M7, Pulldown || '''mcspi1_simo''' ⇔ || - || - || gpio_136 GPIO5[8] || - || - || -
|-
| 07: MCSPI1_SOMI 0x134 || AE22 || M7, Pulldown || '''mcspi1_somi''' ⇔ || - || - || gpio_135 GPIO5[7] || - || - || -
|-
| 09: HDQ_SIOb 0x120 || AA27 || M7, Z || '''hdq_sio''' ⇒ || i2c3_sccb || i2c2_sccb || gpio_127 GPIO4[31] || - || - || -
|-
| 12: I2C2_SCLc 0x126 || C26 || M7, Pullup || '''i2c2_scl''' ⇔↑ || uart1_rx || - || gpio_128 GPIO5[0] || - || - || -
|-
| 14: I2C2_SDAc 0x128 || D26 || M7, Pullup || '''i2c2_sda''' ⇔↑ || uart1_tx || - || gpio_129 GPIO5[1] || - || - || -
|-
| 11: SDMMC3_CMD 0x174 || AG10 || M7, Pullup || usbb2_ulpitll_dat6 || usbb2_ulpiphy_dat6 || sdmmc3_cmd || '''gpio_167''' ⇔↑ GPIO6[7] || mcspi3_simo || dispc2_data12 || rfbi_data12
|-
| 13: SDMMC3_CLK 0x176 || AE9 || M7, Pullup || usbb2_ulpitll_dat7 || usbb2_ulpiphy_dat7 || sdmmc3_clk || '''gpio_168''' ⇔↑ GPIO6[8] || mcspi3_clk || dispc2_data11 || rfbi_data11
|-
| 15: UART2_TX 0x11E || AA26 || M7, Pullup || '''uart2_tx''' ⇒ || sdmmc3_dat1 || - || gpio_126 GPIO4[30] || - || - || -
|-
| 17: UART2_RX 0x11C || AA25 || M7, Pullup || '''uart2_rx''' ⇔↑ || sdmmc3_dat0 || - || gpio_125 GPIO4[29] || - || - || -
|-
| 19: BSP2_CLKX 0x0F6 || AD27 || M7, Pulldown || '''abe_mcbsp2_clkx''' ⇔ || mcspi2_clk || abe_mcasp_ahclkx || gpio_110 GPIO4[14] || usbb2_mm_rxdm || - || -
|-
| 20: BSP2_FSX 0x0FC || AC28 || M7, Pulldown || '''abe_mcbsp2_fsx''' ⇔ || mcspi2_cs0 || abe_mcasp_afsx || gpio_113 GPIO4[17] || usbb2_mm_txen || - || -
|-
| 21: BSP2_DX 0x0FA || AD25 || M7, Pulldown || '''abe_mcbsp2_dx''' ⇒ || mcspi2_simo || abe_mcasp_amute || gpio_112 GPIO4[16] || usbb2_mm_rxrcv || - || -
|-
| 22: BSP2_DR 0x0F8 || AD26 || M7, Pulldown || '''abe_mcbsp2_dr''' ⇔ || mcspi2_somi || abe_mcasp_axr || gpio_111 GPIO4[15] || usbb2_mm_rxdp || - || -
|-
| 23: BSP_CLKS 0x10E || AH26 || M7, Pulldown || '''abe_clks''' ⇔↓ || - || - || gpio_118 GPIO4[22] || - || - || -
|-
| 25: MCSPI4_SOMI 0x158 || AF21 || M7, Pullup || '''mcspi4_somi''' ⇔ || sdmmc4_dat0 || kpd_row6 || gpio_153 GPIO5[25] || - || - || -
|-
| 27: MCSPI4_SIMO 0x156 || AF20 || M7, Pullup || '''mcspi4_simo''' ⇔ || sdmmc4_cmd || kpd_col7 || gpio_152 GPIO5[24] || - || - || -
|-
| 29: MCSPI4_CLK 0x154 || AE21 || M7, Pulldown || '''mcspi4_clk''' ⇔ || sdmmc4_clk || kpd_col6 || gpio_151 GPIO5[23] || - || - || -
|-
| 31: MCSPI4_CS0 0x15A || AE20 || M7, Pullup || '''mcspi4_cs0''' ⇔↓ || sdmmc4_dat3 || kpd_row7 || gpio_154 GPIO5[26] || - || - || -
|}

=== Notes ===

a) Assigned as such in u-boot but reassigned in the kernel board startup code to Mode 3 Outputs

b) There is a 10K pull up to 1.8V, internal to the DuoVero COM, on the HDQ_SIO line. Do not enable a pull down on this line. This will result in a non-logic output level (approximately 1V). This is currently considered to be a bug and may be removed in future COM revisions.

c) There are pullups on I2C2 and I2C3 of approximately 1K. S/C current is over 2mA.

Duovero Multiplexes

2014-09-26T12:51:38Z

Conor O'Rourke: Add the calculation...

[[Category:How_to_-_linux]]
[[Category:Connect_hardware]]

This wiki entry concentrates on the Duovero Parlor board and the Multiplexes available from the 40 pin connector.

[[File:Duovero parlor conn small.png]]

The ground pin is nearest the console connector port and the power pins are nearest the centre of the board. This is as of writing but it is highly recommended that you ''check'' before connecting! Use a voltmeter to check the 3.3V, 5V and 1.8V pins to familiarise yourself with the layout.

There are also two connections on the Parlor board:

<blockquote>
{| class="wikitable"
|-
! OMAP Pin !! GPIO # !! Purpose
|-
| AG24 || GPIO121 || user push button
|-
| AH24 || GPIO122 || user LED
|}
</blockquote>

You should start your journey [http://gumstix.org/hardware-design/duovero-coms.html here].

The primary reference for multiplexes and pin functions is the Texas Instruments OMAP4 technical reference manual. The short version of that 6000 page manual is the OMAP4430 datasheet which is easier to search. The primary source reference is in the Uboot [https://github.com/gumstix/u-boot/tree/v2013.07/board/duovero code], specifically <tt>duovero_mux_data.h</tt> which uses the defines from <tt>./arch/arm/include/asm/arch-omap4/mux_omap4.h</tt>.

== Software Muxing ==

A helpful post from Phil Lutz describes how multiplexing can be explored without kernel recompilation. The default multiplex for the user LED may not be set to GPIO in Uboot. It certainly is not set to GPIO by the OMAP itself. You can look at the OMAP datasheet on page 48 you can see that the official name for GPIO 122 pin is "abe_dmic_din3" (Mode 0 names are accepted pin names).

This information can also be found by searching for "gpio_122" in the board pinmuxing configuration stored in sysfs: <tt>/sys/kernel/debug/omap_mux/board/core</tt>. Every pin which can be configured as gpio has a hint about that.

So now just check which is the current pinmuxing configuration for this pin by:

<pre>
$ cat /sys/kernel/debug/omap_mux/abe_dmic_din3
name: abe_dmic_din3.abe_dmic_din3 (0x4a100116/0x116 = 0x0100), b ah24, t NA
mode: OMAP_PIN_INPUT | OMAP_MUX_MODE0
signals: abe_dmic_din3 | slimbus2_data | abe_dmic_clk2 | gpio_122 | NA | dmtimer9_pwm_evt | NA | safe_mode
</pre>

As the output suggests, the pin is configured in MODE0, this is 'abe_dmic_din3'. The other modes are listed in order as they appear in the OMAP data manual. gpio_122 is multiplex MODE 3. You can set it with:

$ echo 3 > /sys/kernel/debug/omap_mux/abe_dmic_din3

Now you can turn on and off the LED using the usual gpio configuration in /sys/class/gpio/ (google it!). Note that "echo 3" does more than set Mode 3. The number is a selection of bits that set various states for the pin. A quick summary is:
<blockquote>
{| class="wikitable"
|-
|width="100pt" |Bit 0,1,2 || Set the mode
|-
|Bit 3 || 0 = pull up/down disabled , 1 = enabled
|-
|Bit 4 || 0 = pull down, 1 = pull up
|-
|Bit 8 || 0 = Output only. 1 = input enable (bidirectional)
|}
</blockquote>

There are more but these are for sleep modes and wakeup. The manual has details. The defines in mux_omap4.h are useful for interpreting the duovero_mux_data.h file:

<blockquote>

{| class="wikitable"
|-
|IEN || 1 << 8 || Input enable (bidirectional)
|-
|IDIS || 0 << 8 || Output only
|-
|PTU   || 3 << 3   || Enable Pullup
|-
|PTD || 1 << 3 || Enable Pulldown
|-
|EN || 1 << 3 || PU/PD enable
|-
|DIS || 0 << 3 || PU/PD disable
|}

</blockquote>

== Parlor pin mux table ==

To assist in figuring out which pins on the Parlor board can be assigned to which duties, here's a table of functions. Mode 7 is "safe_mode" where the pin is effectively disconnected from any functionality. It's set to high impedance (Z) and is left out of the table. The bolded functions are those set by the current U-Boot duovero_mux_data.h. This file sets other parameters (eg: output only, disable pullup/pulldown, etc) and you must refer to the U-Boot file to know what the full state is. A partial indication of the state (wake mode) is indicated in the table by arrows (bidirectional, output, pullup, pulldown).

Underneath the gpio entries are the GPIO register and bit offset. These numbers are useful for device tree purposes and are calculated simply as: <tt>register = int(gpionumber / 32) + 1</tt> and <tt>offset = gpionumber % 32</tt>.

{| class="wikitable"
|-
! Connector Description !! OMAP Pin !! Reset state !! Mode 0 !! Mode 1 !! Mode 2 !! Mode 3 !! Mode 4 !! Mode 5 !! Mode 6
|-
| User LEDa || AH24 || M7, Pulldown   || '''abe_dmic_din3''' ⇔ || slimbus2_data || abe_dmic_clk2 || gpio_122 GPIO4[26] || - || dmtimer9_pwm_evt || -
|-
| Buttona || AG24 || M7, Pulldown || '''abe_dmic_din2''' ⇔ || slimbus2_clock || abe_mcasp_axr || gpio_121 GPIO4[25] || - || dmtimer11_pwm_evt || -
|-
| 04: MCSPI1_CS0 || AE23 || M7, Pulldown || '''mcspi1_cs0''' ⇔↓ || - || - || gpio_137 GPIO5[9] || - || - || -
|-
| 06: MCSPI1_CS1 || AF23 || M7, Pulldown || '''mcspi1_cs1''' ⇔↓ || uart1_rx || - || gpio_138 GPIO5[10] || - || - || -
|-
| 08: MCSPI1_CS2 || AG23 || M7, Pullup || mcspi1_cs2 || uart1_cts || slimbus2_clock || gpio_139 GPIO5[11] || - || - || -
|-
| 10: MCSPI1_CS3 || AH23 || M7, Pullup || mcspi1_cs3 || uart1_rts || slimbus2_data || gpio_140 GPIO5[12] || - || - || -
|-
| 03: MCSPI1_CLK || AF22 || M7, Pulldown || '''mcspi1_clk''' ⇔ || - || - || gpio_134 GPIO5[6] || - || - || -
|-
| 05: MCSPI1_SIMO || AG22 || M7, Pulldown || '''mcspi1_simo''' ⇔ || - || - || gpio_136 GPIO5[8] || - || - || -
|-
| 07: MCSPI1_SOMI || AE22 || M7, Pulldown || '''mcspi1_somi''' ⇔ || - || - || gpio_135 GPIO5[7] || - || - || -
|-
| 09: HDQ_SIOb || AA27 || M7, Z || '''hdq_sio''' ⇒ || i2c3_sccb || i2c2_sccb || gpio_127 GPIO4[31] || - || - || -
|-
| 12: I2C2_SCLc || C26 || M7, Pullup || '''i2c2_scl''' ⇔↑ || uart1_rx || - || gpio_128 GPIO5[0] || - || - || -
|-
| 14: I2C2_SDAc || D26 || M7, Pullup || '''i2c2_sda''' ⇔↑ || uart1_tx || - || gpio_129 GPIO5[1] || - || - || -
|-
| 11: SDMMC3_CMD || AG10 || M7, Pullup || usbb2_ulpitll_dat6 || usbb2_ulpiphy_dat6 || sdmmc3_cmd || '''gpio_167''' ⇔↑ GPIO6[7] || mcspi3_simo || dispc2_data12 || rfbi_data12
|-
| 13: SDMMC3_CLK || AE9 || M7, Pullup || usbb2_ulpitll_dat7 || usbb2_ulpiphy_dat7 || sdmmc3_clk || '''gpio_168''' ⇔↑ GPIO6[8] || mcspi3_clk || dispc2_data11 || rfbi_data11
|-
| 15: UART2_TX || AA26 || M7, Pullup || '''uart2_tx''' ⇒ || sdmmc3_dat1 || - || gpio_126 GPIO4[30] || - || - || -
|-
| 17: UART2_RX || AA25 || M7, Pullup || '''uart2_rx''' ⇔↑ || sdmmc3_dat0 || - || gpio_125 GPIO4[29] || - || - || -
|-
| 19: BSP2_CLKX || AD27 || M7, Pulldown || '''abe_mcbsp2_clkx''' ⇔ || mcspi2_clk || abe_mcasp_ahclkx || gpio_110 GPIO4[14] || usbb2_mm_rxdm || - || -
|-
| 20: BSP2_FSX || AC28 || M7, Pulldown || '''abe_mcbsp2_fsx''' ⇔ || mcspi2_cs0 || abe_mcasp_afsx || gpio_113 GPIO4[17] || usbb2_mm_txen || - || -
|-
| 21: BSP2_DX || AD25 || M7, Pulldown || '''abe_mcbsp2_dx''' ⇒ || mcspi2_simo || abe_mcasp_amute || gpio_112 GPIO4[16] || usbb2_mm_rxrcv || - || -
|-
| 22: BSP2_DR || AD26 || M7, Pulldown || '''abe_mcbsp2_dr''' ⇔ || mcspi2_somi || abe_mcasp_axr || gpio_111 GPIO4[15] || usbb2_mm_rxdp || - || -
|-
| 23: BSP_CLKS || AH26 || M7, Pulldown || '''abe_clks''' ⇔↓ || - || - || gpio_118 GPIO4[22] || - || - || -
|-
| 25: MCSPI4_SOMI || AF21 || M7, Pullup || '''mcspi4_somi''' ⇔ || sdmmc4_dat0 || kpd_row6 || gpio_153 GPIO5[25] || - || - || -
|-
| 27: MCSPI4_SIMO || AF20 || M7, Pullup || '''mcspi4_simo''' ⇔ || sdmmc4_cmd || kpd_col7 || gpio_152 GPIO5[24] || - || - || -
|-
| 29: MCSPI4_CLK || AE21 || M7, Pulldown || '''mcspi4_clk''' ⇔ || sdmmc4_clk || kpd_col6 || gpio_151 GPIO5[23] || - || - || -
|-
| 31: MCSPI4_CS0 || AE20 || M7, Pullup || '''mcspi4_cs0''' ⇔↓ || sdmmc4_dat3 || kpd_row7 || gpio_154 GPIO5[26] || - || - || -
|}

=== Notes ===

a) Assigned as such in u-boot but reassigned in the kernel board startup code to Mode 3 Outputs

b) There is a 10K pull up to 1.8V, internal to the DuoVero COM, on the HDQ_SIO line. Do not enable a pull down on this line. This will result in a non-logic output level (approximately 1V). This is currently considered to be a bug and may be removed in future COM revisions.

c) There are pullups on I2C2 and I2C3 of approximately 1K. S/C current is over 2mA.

Duovero Multiplexes

2014-09-26T12:42:45Z

Conor O'Rourke: Addition of GPIO registers and offset for DTS

[[Category:How_to_-_linux]]
[[Category:Connect_hardware]]

This wiki entry concentrates on the Duovero Parlor board and the Multiplexes available from the 40 pin connector.

[[File:Duovero parlor conn small.png]]

The ground pin is nearest the console connector port and the power pins are nearest the centre of the board. This is as of writing but it is highly recommended that you ''check'' before connecting! Use a voltmeter to check the 3.3V, 5V and 1.8V pins to familiarise yourself with the layout.

There are also two connections on the Parlor board:

<blockquote>
{| class="wikitable"
|-
! OMAP Pin !! GPIO # !! Purpose
|-
| AG24 || GPIO121 || user push button
|-
| AH24 || GPIO122 || user LED
|}
</blockquote>

You should start your journey [http://gumstix.org/hardware-design/duovero-coms.html here].

The primary reference for multiplexes and pin functions is the Texas Instruments OMAP4 technical reference manual. The short version of that 6000 page manual is the OMAP4430 datasheet which is easier to search. The primary source reference is in the Uboot [https://github.com/gumstix/u-boot/tree/v2013.07/board/duovero code], specifically <tt>duovero_mux_data.h</tt> which uses the defines from <tt>./arch/arm/include/asm/arch-omap4/mux_omap4.h</tt>.

== Software Muxing ==

A helpful post from Phil Lutz describes how multiplexing can be explored without kernel recompilation. The default multiplex for the user LED may not be set to GPIO in Uboot. It certainly is not set to GPIO by the OMAP itself. You can look at the OMAP datasheet on page 48 you can see that the official name for GPIO 122 pin is "abe_dmic_din3" (Mode 0 names are accepted pin names).

This information can also be found by searching for "gpio_122" in the board pinmuxing configuration stored in sysfs: <tt>/sys/kernel/debug/omap_mux/board/core</tt>. Every pin which can be configured as gpio has a hint about that.

So now just check which is the current pinmuxing configuration for this pin by:

<pre>
$ cat /sys/kernel/debug/omap_mux/abe_dmic_din3
name: abe_dmic_din3.abe_dmic_din3 (0x4a100116/0x116 = 0x0100), b ah24, t NA
mode: OMAP_PIN_INPUT | OMAP_MUX_MODE0
signals: abe_dmic_din3 | slimbus2_data | abe_dmic_clk2 | gpio_122 | NA | dmtimer9_pwm_evt | NA | safe_mode
</pre>

As the output suggests, the pin is configured in MODE0, this is 'abe_dmic_din3'. The other modes are listed in order as they appear in the OMAP data manual. gpio_122 is multiplex MODE 3. You can set it with:

$ echo 3 > /sys/kernel/debug/omap_mux/abe_dmic_din3

Now you can turn on and off the LED using the usual gpio configuration in /sys/class/gpio/ (google it!). Note that "echo 3" does more than set Mode 3. The number is a selection of bits that set various states for the pin. A quick summary is:
<blockquote>
{| class="wikitable"
|-
|width="100pt" |Bit 0,1,2 || Set the mode
|-
|Bit 3 || 0 = pull up/down disabled , 1 = enabled
|-
|Bit 4 || 0 = pull down, 1 = pull up
|-
|Bit 8 || 0 = Output only. 1 = input enable (bidirectional)
|}
</blockquote>

There are more but these are for sleep modes and wakeup. The manual has details. The defines in mux_omap4.h are useful for interpreting the duovero_mux_data.h file:

<blockquote>

{| class="wikitable"
|-
|IEN || 1 << 8 || Input enable (bidirectional)
|-
|IDIS || 0 << 8 || Output only
|-
|PTU   || 3 << 3   || Enable Pullup
|-
|PTD || 1 << 3 || Enable Pulldown
|-
|EN || 1 << 3 || PU/PD enable
|-
|DIS || 0 << 3 || PU/PD disable
|}

</blockquote>

== Parlor pin mux table ==

To assist in figuring out which pins on the Parlor board can be assigned to which duties, here's a table of functions. Mode 7 is "safe_mode" where the pin is effectively disconnected from any functionality. It's set to high impedance (Z) and is left out of the table. The bolded functions are those set by the current U-Boot duovero_mux_data.h. This file sets other parameters (eg: output only, disable pullup/pulldown, etc) and you must refer to the U-Boot file to know what the full state is. A partial indication of the state (wake mode) is indicated in the table by arrows (bidirectional, output, pullup, pulldown).

Underneath the gpio entries are the GPIO register and bit offset. These numbers are useful for device tree purposes.

{| class="wikitable"
|-
! Connector Description !! OMAP Pin !! Reset state !! Mode 0 !! Mode 1 !! Mode 2 !! Mode 3 !! Mode 4 !! Mode 5 !! Mode 6
|-
| User LEDa || AH24 || M7, Pulldown   || '''abe_dmic_din3''' ⇔ || slimbus2_data || abe_dmic_clk2 || gpio_122 GPIO4[26] || - || dmtimer9_pwm_evt || -
|-
| Buttona || AG24 || M7, Pulldown || '''abe_dmic_din2''' ⇔ || slimbus2_clock || abe_mcasp_axr || gpio_121 GPIO4[25] || - || dmtimer11_pwm_evt || -
|-
| 04: MCSPI1_CS0 || AE23 || M7, Pulldown || '''mcspi1_cs0''' ⇔↓ || - || - || gpio_137 GPIO5[9] || - || - || -
|-
| 06: MCSPI1_CS1 || AF23 || M7, Pulldown || '''mcspi1_cs1''' ⇔↓ || uart1_rx || - || gpio_138 GPIO5[10] || - || - || -
|-
| 08: MCSPI1_CS2 || AG23 || M7, Pullup || mcspi1_cs2 || uart1_cts || slimbus2_clock || gpio_139 GPIO5[11] || - || - || -
|-
| 10: MCSPI1_CS3 || AH23 || M7, Pullup || mcspi1_cs3 || uart1_rts || slimbus2_data || gpio_140 GPIO5[12] || - || - || -
|-
| 03: MCSPI1_CLK || AF22 || M7, Pulldown || '''mcspi1_clk''' ⇔ || - || - || gpio_134 GPIO5[6] || - || - || -
|-
| 05: MCSPI1_SIMO || AG22 || M7, Pulldown || '''mcspi1_simo''' ⇔ || - || - || gpio_136 GPIO5[8] || - || - || -
|-
| 07: MCSPI1_SOMI || AE22 || M7, Pulldown || '''mcspi1_somi''' ⇔ || - || - || gpio_135 GPIO5[7] || - || - || -
|-
| 09: HDQ_SIOb || AA27 || M7, Z || '''hdq_sio''' ⇒ || i2c3_sccb || i2c2_sccb || gpio_127 GPIO4[31] || - || - || -
|-
| 12: I2C2_SCLc || C26 || M7, Pullup || '''i2c2_scl''' ⇔↑ || uart1_rx || - || gpio_128 GPIO5[0] || - || - || -
|-
| 14: I2C2_SDAc || D26 || M7, Pullup || '''i2c2_sda''' ⇔↑ || uart1_tx || - || gpio_129 GPIO5[1] || - || - || -
|-
| 11: SDMMC3_CMD || AG10 || M7, Pullup || usbb2_ulpitll_dat6 || usbb2_ulpiphy_dat6 || sdmmc3_cmd || '''gpio_167''' ⇔↑ GPIO6[7] || mcspi3_simo || dispc2_data12 || rfbi_data12
|-
| 13: SDMMC3_CLK || AE9 || M7, Pullup || usbb2_ulpitll_dat7 || usbb2_ulpiphy_dat7 || sdmmc3_clk || '''gpio_168''' ⇔↑ GPIO6[8] || mcspi3_clk || dispc2_data11 || rfbi_data11
|-
| 15: UART2_TX || AA26 || M7, Pullup || '''uart2_tx''' ⇒ || sdmmc3_dat1 || - || gpio_126 GPIO4[30] || - || - || -
|-
| 17: UART2_RX || AA25 || M7, Pullup || '''uart2_rx''' ⇔↑ || sdmmc3_dat0 || - || gpio_125 GPIO4[29] || - || - || -
|-
| 19: BSP2_CLKX || AD27 || M7, Pulldown || '''abe_mcbsp2_clkx''' ⇔ || mcspi2_clk || abe_mcasp_ahclkx || gpio_110 GPIO4[14] || usbb2_mm_rxdm || - || -
|-
| 20: BSP2_FSX || AC28 || M7, Pulldown || '''abe_mcbsp2_fsx''' ⇔ || mcspi2_cs0 || abe_mcasp_afsx || gpio_113 GPIO4[17] || usbb2_mm_txen || - || -
|-
| 21: BSP2_DX || AD25 || M7, Pulldown || '''abe_mcbsp2_dx''' ⇒ || mcspi2_simo || abe_mcasp_amute || gpio_112 GPIO4[16] || usbb2_mm_rxrcv || - || -
|-
| 22: BSP2_DR || AD26 || M7, Pulldown || '''abe_mcbsp2_dr''' ⇔ || mcspi2_somi || abe_mcasp_axr || gpio_111 GPIO4[15] || usbb2_mm_rxdp || - || -
|-
| 23: BSP_CLKS || AH26 || M7, Pulldown || '''abe_clks''' ⇔↓ || - || - || gpio_118 GPIO4[22] || - || - || -
|-
| 25: MCSPI4_SOMI || AF21 || M7, Pullup || '''mcspi4_somi''' ⇔ || sdmmc4_dat0 || kpd_row6 || gpio_153 GPIO5[25] || - || - || -
|-
| 27: MCSPI4_SIMO || AF20 || M7, Pullup || '''mcspi4_simo''' ⇔ || sdmmc4_cmd || kpd_col7 || gpio_152 GPIO5[24] || - || - || -
|-
| 29: MCSPI4_CLK || AE21 || M7, Pulldown || '''mcspi4_clk''' ⇔ || sdmmc4_clk || kpd_col6 || gpio_151 GPIO5[23] || - || - || -
|-
| 31: MCSPI4_CS0 || AE20 || M7, Pullup || '''mcspi4_cs0''' ⇔↓ || sdmmc4_dat3 || kpd_row7 || gpio_154 GPIO5[26] || - || - || -
|}

=== Notes ===

a) Assigned as such in u-boot but reassigned in the kernel board startup code to Mode 3 Outputs

b) There is a 10K pull up to 1.8V, internal to the DuoVero COM, on the HDQ_SIO line. Do not enable a pull down on this line. This will result in a non-logic output level (approximately 1V). This is currently considered to be a bug and may be removed in future COM revisions.

c) There are pullups on I2C2 and I2C3 of approximately 1K. S/C current is over 2mA.

Category:How to - Known Issues

2014-03-29T17:32:22Z

Conor O'Rourke:

If you have fixed a problem while setting up your gumstix board that you feel other people are likely to encounter, please document your solution here.

== Network Problems ==

===Network Services Do Not Come Up===

'''Symptom:''' Network services do not come up. LAN link lights blink for a couple of seconds during bootup, but then remain out. This has been observed with the connex board with the netCF expansion module running a fresh install of OpenEmbedded.

'''Solution:''' The file /etc/network/interfaces contains network interface definitions for several classes of devices. If you are not using the wireless ethernet expansion module, comment out the wlan0 interface section and reboot the unit.

===Wired Ethernet Does Not Come Up===
'''Symptom:''' When booting an Overo with Tobi expansion board, the wired Ethernet eth0 interface does not come up. No IP address is acquired via DHCP, even though eth0 is configured to use DHCP.

'''Solution:''' The solution is documented here: [[Overo Tobi Ethernet]].

== Issues with prebuilt DuoVero images ==

The serial port on Uart2 is /dev/ttyO1. This is interfered with by the Bluetooth systemd service which isn't necessary on this board. Disable this systemd service to get proper access to /dev/ttyO1.

<tt>systemctl disable bluetooth</tt>

and rebooting is a good start.

== Issues with prebuild overo images ==

Images are here: http://www.sakoman.com/feeds/omap3/glibc/images/overo/

=== Overo fire with Palo35 ===
{| border="0" cellpadding="2" cellspacing="1" style="background:#e2e2e2;" class="sortable wikitable"
! Version || Bootup || Login || LCD || Touchscreen
|- bgcolor="#f8f8ff"
| 201004220807 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}}
|- bgcolor="#f8f8ff"
| 201004141106 || {{Yes}} || {{Yes}} || {{No}} || {{No}}
|- bgcolor="#f8f8ff"
| 201002031857 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}}
|}

Category:How to - Known Issues

2014-03-29T17:31:16Z

Conor O'Rourke: Add duovero section

If you have fixed a problem while setting up your gumstix board that you feel other people are likely to encounter, please document your solution here.

== Network Problems ==

===Network Services Do Not Come Up===

'''Symptom:''' Network services do not come up. LAN link lights blink for a couple of seconds during bootup, but then remain out. This has been observed with the connex board with the netCF expansion module running a fresh install of OpenEmbedded.

'''Solution:''' The file /etc/network/interfaces contains network interface definitions for several classes of devices. If you are not using the wireless ethernet expansion module, comment out the wlan0 interface section and reboot the unit.

===Wired Ethernet Does Not Come Up===
'''Symptom:''' When booting an Overo with Tobi expansion board, the wired Ethernet eth0 interface does not come up. No IP address is acquired via DHCP, even though eth0 is configured to use DHCP.

'''Solution:''' The solution is documented here: [[Overo Tobi Ethernet]].

== Issues with prebuilt DuoVero images ==

The serial port on Uart2 is /dev/ttyO1. This is interfered with by the Bluetooth systemd service which isn't necessary on this board. Disable this systemd service to get access to /dev/ttyO2.

<tt>systemctl disable bluetooth</tt>

and rebooting is a good start.

== Issues with prebuild overo images ==

Images are here: http://www.sakoman.com/feeds/omap3/glibc/images/overo/

=== Overo fire with Palo35 ===
{| border="0" cellpadding="2" cellspacing="1" style="background:#e2e2e2;" class="sortable wikitable"
! Version || Bootup || Login || LCD || Touchscreen
|- bgcolor="#f8f8ff"
| 201004220807 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}}
|- bgcolor="#f8f8ff"
| 201004141106 || {{Yes}} || {{Yes}} || {{No}} || {{No}}
|- bgcolor="#f8f8ff"
| 201002031857 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}}
|}

Duovero Multiplexes

2013-12-10T09:32:46Z

Conor O'Rourke:

[[Category:How_to_-_linux]]
[[Category:Connect_hardware]]

This wiki entry concentrates on the Duovero Parlor board and the Multiplexes available from the 40 pin connector.

[[File:Duovero parlor conn small.png]]

The ground pin is nearest the console connector port and the power pins are nearest the centre of the board. This is as of writing but it is highly recommended that you ''check'' before connecting! Use a voltmeter to check the 3.3V, 5V and 1.8V pins to familiarise yourself with the layout.

There are also two connections on the Parlor board:

<blockquote>
{| class="wikitable"
|-
! OMAP Pin !! GPIO # !! Purpose
|-
| AG24 || GPIO121 || user push button
|-
| AH24 || GPIO122 || user LED
|}
</blockquote>

You should start your journey [http://gumstix.org/hardware-design/duovero-coms.html here].

The primary reference for multiplexes and pin functions is the Texas Instruments OMAP4 technical reference manual. The short version of that 6000 page manual is the OMAP4430 datasheet which is easier to search. The primary source reference is in the Uboot [https://github.com/gumstix/u-boot/tree/v2013.07/board/duovero code], specifically <tt>duovero_mux_data.h</tt> which uses the defines from <tt>./arch/arm/include/asm/arch-omap4/mux_omap4.h</tt>.

== Software Muxing ==

A helpful post from Phil Lutz describes how multiplexing can be explored without kernel recompilation. The default multiplex for the user LED may not be set to GPIO in Uboot. It certainly is not set to GPIO by the OMAP itself. You can look at the OMAP datasheet on page 48 you can see that the official name for GPIO 122 pin is "abe_dmic_din3" (Mode 0 names are accepted pin names).

This information can also be found by searching for "gpio_122" in the board pinmuxing configuration stored in sysfs: <tt>/sys/kernel/debug/omap_mux/board/core</tt>. Every pin which can be configured as gpio has a hint about that.

So now just check which is the current pinmuxing configuration for this pin by:

<pre>
$ cat /sys/kernel/debug/omap_mux/abe_dmic_din3
name: abe_dmic_din3.abe_dmic_din3 (0x4a100116/0x116 = 0x0100), b ah24, t NA
mode: OMAP_PIN_INPUT | OMAP_MUX_MODE0
signals: abe_dmic_din3 | slimbus2_data | abe_dmic_clk2 | gpio_122 | NA | dmtimer9_pwm_evt | NA | safe_mode
</pre>

As the output suggests, the pin is configured in MODE0, this is 'abe_dmic_din3'. The other modes are listed in order as they appear in the OMAP data manual. gpio_122 is multiplex MODE 3. You can set it with:

$ echo 3 > /sys/kernel/debug/omap_mux/abe_dmic_din3

Now you can turn on and off the LED using the usual gpio configuration in /sys/class/gpio/ (google it!). Note that "echo 3" does more than set Mode 3. The number is a selection of bits that set various states for the pin. A quick summary is:
<blockquote>
{| class="wikitable"
|-
|width="100pt" |Bit 0,1,2 || Set the mode
|-
|Bit 3 || 0 = pull up/down disabled , 1 = enabled
|-
|Bit 4 || 0 = pull down, 1 = pull up
|-
|Bit 8 || 0 = Output only. 1 = input enable (bidirectional)
|}
</blockquote>

There are more but these are for sleep modes and wakeup. The manual has details. The defines in mux_omap4.h are useful for interpreting the duovero_mux_data.h file:

<blockquote>

{| class="wikitable"
|-
|IEN || 1 << 8 || Input enable (bidirectional)
|-
|IDIS || 0 << 8 || Output only
|-
|PTU   || 3 << 3   || Enable Pullup
|-
|PTD || 1 << 3 || Enable Pulldown
|-
|EN || 1 << 3 || PU/PD enable
|-
|DIS || 0 << 3 || PU/PD disable
|}

</blockquote>

== Parlor pin mux table ==

To assist in figuring out which pins on the Parlor board can be assigned to which duties, here's a table of functions. Mode 7 is "safe_mode" where the pin is effectively disconnected from any functionality. It's set to high impedance (Z) and is left out of the table. The bolded functions are those set by the current U-Boot duovero_mux_data.h. This file sets other parameters (eg: output only, disable pullup/pulldown, etc) and you must refer to the U-Boot file to know what the full state is. A partial indication of the state (wake mode) is indicated in the table by arrows (bidirectional, output, pullup, pulldown).

{| class="wikitable"
|-
! Connector Description !! OMAP Pin !! Reset state !! Mode 0 !! Mode 1 !! Mode 2 !! Mode 3 !! Mode 4 !! Mode 5 !! Mode 6
|-
| User LEDa || AH24 || M7, Pulldown   || '''abe_dmic_din3''' ⇔ || slimbus2_data || abe_dmic_clk2 || gpio_122 || - || dmtimer9_pwm_evt || -
|-
| Buttona || AG24 || M7, Pulldown || '''abe_dmic_din2''' ⇔ || slimbus2_clock || abe_mcasp_axr || gpio_121 || - || dmtimer11_pwm_evt || -
|-
| 04: MCSPI1_CS0 || AE23 || M7, Pulldown || '''mcspi1_cs0''' ⇔↓ || - || - || gpio_137 || - || - || -
|-
| 06: MCSPI1_CS1 || AF23 || M7, Pulldown || '''mcspi1_cs1''' ⇔↓ || uart1_rx || - || gpio_138 || - || - || -
|-
| 08: MCSPI1_CS2 || AG23 || M7, Pullup || mcspi1_cs2 || uart1_cts || slimbus2_clock || gpio_139 || - || - || -
|-
| 10: MCSPI1_CS3 || AH23 || M7, Pullup || mcspi1_cs3 || uart1_rts || slimbus2_data || gpio_140 || - || - || -
|-
| 03: MCSPI1_CLK || AF22 || M7, Pulldown || '''mcspi1_clk''' ⇔ || - || - || gpio_134 || - || - || -
|-
| 05: MCSPI1_SIMO || AG22 || M7, Pulldown || '''mcspi1_simo''' ⇔ || - || - || gpio_136 || - || - || -
|-
| 07: MCSPI1_SOMI || AE22 || M7, Pulldown || '''mcspi1_somi''' ⇔ || - || - || gpio_135 || - || - || -
|-
| 09: HDQ_SIOb || AA27 || M7, Z || '''hdq_sio''' ⇒ || i2c3_sccb || i2c2_sccb || gpio_127 || - || - || -
|-
| 12: I2C2_SCLc || C26 || M7, Pullup || '''i2c2_scl''' ⇔↑ || uart1_rx || - || gpio_128 || - || - || -
|-
| 14: I2C2_SDAc || D26 || M7, Pullup || '''i2c2_sda''' ⇔↑ || uart1_tx || - || gpio_129 || - || - || -
|-
| 11: SDMMC3_CMD || AG10 || M7, Pullup || usbb2_ulpitll_dat6 || usbb2_ulpiphy_dat6 || sdmmc3_cmd || '''gpio_167''' ⇔↑ || mcspi3_simo || dispc2_data12 || rfbi_data12
|-
| 13: SDMMC3_CLK || AE9 || M7, Pullup || usbb2_ulpitll_dat7 || usbb2_ulpiphy_dat7 || sdmmc3_clk || '''gpio_168''' ⇔↑ || mcspi3_clk || dispc2_data11 || rfbi_data11
|-
| 15: UART2_TX || AA26 || M7, Pullup || '''uart2_tx''' ⇒ || sdmmc3_dat1 || - || gpio_126 || - || - || -
|-
| 17: UART2_RX || AA25 || M7, Pullup || '''uart2_rx''' ⇔↑ || sdmmc3_dat0 || - || gpio_125 || - || - || -
|-
| 19: BSP2_CLKX || AD27 || M7, Pulldown || '''abe_mcbsp2_clkx''' ⇔ || mcspi2_clk || abe_mcasp_ahclkx || gpio_110 || usbb2_mm_rxdm || - || -
|-
| 20: BSP2_FSX || AC28 || M7, Pulldown || '''abe_mcbsp2_fsx''' ⇔ || mcspi2_cs0 || abe_mcasp_afsx || gpio_113 || usbb2_mm_txen || - || -
|-
| 21: BSP2_DX || AD25 || M7, Pulldown || '''abe_mcbsp2_dx''' ⇒ || mcspi2_simo || abe_mcasp_amute || gpio_112 || usbb2_mm_rxrcv || - || -
|-
| 22: BSP2_DR || AD26 || M7, Pulldown || '''abe_mcbsp2_dr''' ⇔ || mcspi2_somi || abe_mcasp_axr || gpio_111 || usbb2_mm_rxdp || - || -
|-
| 23: BSP_CLKS || AH26 || M7, Pulldown || '''abe_clks''' ⇔↓ || - || - || gpio_118 || - || - || -
|-
| 25: MCSPI4_SOMI || AF21 || M7, Pullup || '''mcspi4_somi''' ⇔ || sdmmc4_dat0 || kpd_row6 || gpio_153 || - || - || -
|-
| 27: MCSPI4_SIMO || AF20 || M7, Pullup || '''mcspi4_simo''' ⇔ || sdmmc4_cmd || kpd_col7 || gpio_152 || - || - || -
|-
| 29: MCSPI4_CLK || AE21 || M7, Pulldown || '''mcspi4_clk''' ⇔ || sdmmc4_clk || kpd_col6 || gpio_151 || - || - || -
|-
| 31: MCSPI4_CS0 || AE20 || M7, Pullup || '''mcspi4_cs0''' ⇔↓ || sdmmc4_dat3 || kpd_row7 || gpio_154 || - || - || -
|}

=== Notes ===

a) Assigned as such in u-boot but reassigned in the kernel board startup code to Mode 3 Outputs

b) There is a 10K pull up to 1.8V, internal to the DuoVero COM, on the HDQ_SIO line. Do not enable a pull down on this line. This will result in a non-logic output level (approximately 1V). This is currently considered to be a bug and may be removed in future COM revisions.

c) There are pullups on I2C2 and I2C3 of approximately 1K. S/C current is over 2mA.

Duovero Multiplexes

2013-12-10T09:30:35Z

Conor O'Rourke: Added notes on pins

[[Category:How_to_-_linux]]
[[Category:Connect_hardware]]

This wiki entry concentrates on the Duovero Parlor board and the Multiplexes available from the 40 pin connector.

[[File:Duovero parlor conn small.png]]

The ground pin is nearest the console connector port and the power pins are nearest the centre of the board. This is as of writing but it is highly recommended that you ''check'' before connecting! Use a voltmeter to check the 3.3V, 5V and 1.8V pins to familiarise yourself with the layout.

There are also two connections on the Parlor board:

<blockquote>
{| class="wikitable"
|-
! OMAP Pin !! GPIO # !! Purpose
|-
| AG24 || GPIO121 || user push button
|-
| AH24 || GPIO122 || user LED
|}
</blockquote>

You should start your journey [http://gumstix.org/hardware-design/duovero-coms.html here].

The primary reference for multiplexes and pin functions is the Texas Instruments OMAP4 technical reference manual. The short version of that 6000 page manual is the OMAP4430 datasheet which is easier to search. The primary source reference is in the Uboot [https://github.com/gumstix/u-boot/tree/v2013.07/board/duovero code], specifically <tt>duovero_mux_data.h</tt> which uses the defines from <tt>./arch/arm/include/asm/arch-omap4/mux_omap4.h</tt>.

== Software Muxing ==

A helpful post from Phil Lutz describes how multiplexing can be explored without kernel recompilation. The default multiplex for the user LED may not be set to GPIO in Uboot. It certainly is not set to GPIO by the OMAP itself. You can look at the OMAP datasheet on page 48 you can see that the official name for GPIO 122 pin is "abe_dmic_din3" (Mode 0 names are accepted pin names).

This information can also be found by searching for "gpio_122" in the board pinmuxing configuration stored in sysfs: <tt>/sys/kernel/debug/omap_mux/board/core</tt>. Every pin which can be configured as gpio has a hint about that.

So now just check which is the current pinmuxing configuration for this pin by:

<pre>
$ cat /sys/kernel/debug/omap_mux/abe_dmic_din3
name: abe_dmic_din3.abe_dmic_din3 (0x4a100116/0x116 = 0x0100), b ah24, t NA
mode: OMAP_PIN_INPUT | OMAP_MUX_MODE0
signals: abe_dmic_din3 | slimbus2_data | abe_dmic_clk2 | gpio_122 | NA | dmtimer9_pwm_evt | NA | safe_mode
</pre>

As the output suggests, the pin is configured in MODE0, this is 'abe_dmic_din3'. The other modes are listed in order as they appear in the OMAP data manual. gpio_122 is multiplex MODE 3. You can set it with:

$ echo 3 > /sys/kernel/debug/omap_mux/abe_dmic_din3

Now you can turn on and off the LED using the usual gpio configuration in /sys/class/gpio/ (google it!). Note that "echo 3" does more than set Mode 3. The number is a selection of bits that set various states for the pin. A quick summary is:
<blockquote>
{| class="wikitable"
|-
|width="100pt" |Bit 0,1,2 || Set the mode
|-
|Bit 3 || 0 = pull up/down disabled , 1 = enabled
|-
|Bit 4 || 0 = pull down, 1 = pull up
|-
|Bit 8 || 0 = Output only. 1 = input enable (bidirectional)
|}
</blockquote>

There are more but these are for sleep modes and wakeup. The manual has details. The defines in mux_omap4.h are useful for interpreting the duovero_mux_data.h file:

<blockquote>

{| class="wikitable"
|-
|IEN || 1 << 8 || Input enable (bidirectional)
|-
|IDIS || 0 << 8 || Output only
|-
|PTU   || 3 << 3   || Enable Pullup
|-
|PTD || 1 << 3 || Enable Pulldown
|-
|EN || 1 << 3 || PU/PD enable
|-
|DIS || 0 << 3 || PU/PD disable
|}

</blockquote>

== Parlor pin mux table ==

To assist in figuring out which pins on the Parlor board can be assigned to which duties, here's a table of functions. Mode 7 is "safe_mode" where the pin is effectively disconnected from any functionality. It's set to high impedance (Z) and is left out of the table. The bolded functions are those set by the current U-Boot duovero_mux_data.h. This file sets other parameters (eg: output only, disable pullup/pulldown, etc) and you must refer to the U-Boot file to know what the full state is. A partial indication of the state (wake mode) is indicated in the table by arrows (bidirectional, output, pullup, pulldown).

{| class="wikitable"
|-
! Connector Description !! OMAP Pin !! Reset state !! Mode 0 !! Mode 1 !! Mode 2 !! Mode 3 !! Mode 4 !! Mode 5 !! Mode 6
|-
| User LEDa || AH24 || M7, Pulldown   || '''abe_dmic_din3''' ⇔ || slimbus2_data || abe_dmic_clk2 || gpio_122 || - || dmtimer9_pwm_evt || -
|-
| Buttona || AG24 || M7, Pulldown || '''abe_dmic_din2''' ⇔ || slimbus2_clock || abe_mcasp_axr || gpio_121 || - || dmtimer11_pwm_evt || -
|-
| 04: MCSPI1_CS0 || AE23 || M7, Pulldown || '''mcspi1_cs0''' ⇔↓ || - || - || gpio_137 || - || - || -
|-
| 06: MCSPI1_CS1 || AF23 || M7, Pulldown || '''mcspi1_cs1''' ⇔↓ || uart1_rx || - || gpio_138 || - || - || -
|-
| 08: MCSPI1_CS2 || AG23 || M7, Pullup || mcspi1_cs2 || uart1_cts || slimbus2_clock || gpio_139 || - || - || -
|-
| 10: MCSPI1_CS3 || AH23 || M7, Pullup || mcspi1_cs3 || uart1_rts || slimbus2_data || gpio_140 || - || - || -
|-
| 03: MCSPI1_CLK || AF22 || M7, Pulldown || '''mcspi1_clk''' ⇔ || - || - || gpio_134 || - || - || -
|-
| 05: MCSPI1_SIMO || AG22 || M7, Pulldown || '''mcspi1_simo''' ⇔ || - || - || gpio_136 || - || - || -
|-
| 07: MCSPI1_SOMI || AE22 || M7, Pulldown || '''mcspi1_somi''' ⇔ || - || - || gpio_135 || - || - || -
|-
| 09: HDQ_SIOb || AA27 || M7, Z || '''hdq_sio''' ⇒ || i2c3_sccb || i2c2_sccb || gpio_127 || - || - || -
|-
| 12: I2C2_SCLc || C26 || M7, Pullup || '''i2c2_scl''' ⇔↑ || uart1_rx || - || gpio_128 || - || - || -
|-
| 14: I2C2_SDAc || D26 || M7, Pullup || '''i2c2_sda''' ⇔↑ || uart1_tx || - || gpio_129 || - || - || -
|-
| 11: SDMMC3_CMD || AG10 || M7, Pullup || usbb2_ulpitll_dat6 || usbb2_ulpiphy_dat6 || sdmmc3_cmd || '''gpio_167''' ⇔↑ || mcspi3_simo || dispc2_data12 || rfbi_data12
|-
| 13: SDMMC3_CLK || AE9 || M7, Pullup || usbb2_ulpitll_dat7 || usbb2_ulpiphy_dat7 || sdmmc3_clk || '''gpio_168''' ⇔↑ || mcspi3_clk || dispc2_data11 || rfbi_data11
|-
| 15: UART2_TX || AA26 || M7, Pullup || '''uart2_tx''' ⇒ || sdmmc3_dat1 || - || gpio_126 || - || - || -
|-
| 17: UART2_RX || AA25 || M7, Pullup || '''uart2_rx''' ⇔↑ || sdmmc3_dat0 || - || gpio_125 || - || - || -
|-
| 19: BSP2_CLKX || AD27 || M7, Pulldown || '''abe_mcbsp2_clkx''' ⇔ || mcspi2_clk || abe_mcasp_ahclkx || gpio_110 || usbb2_mm_rxdm || - || -
|-
| 20: BSP2_FSX || AC28 || M7, Pulldown || '''abe_mcbsp2_fsx''' ⇔ || mcspi2_cs0 || abe_mcasp_afsx || gpio_113 || usbb2_mm_txen || - || -
|-
| 21: BSP2_DX || AD25 || M7, Pulldown || '''abe_mcbsp2_dx''' ⇒ || mcspi2_simo || abe_mcasp_amute || gpio_112 || usbb2_mm_rxrcv || - || -
|-
| 22: BSP2_DR || AD26 || M7, Pulldown || '''abe_mcbsp2_dr''' ⇔ || mcspi2_somi || abe_mcasp_axr || gpio_111 || usbb2_mm_rxdp || - || -
|-
| 23: BSP_CLKS || AH26 || M7, Pulldown || '''abe_clks''' ⇔↓ || - || - || gpio_118 || - || - || -
|-
| 25: MCSPI4_SOMI || AF21 || M7, Pullup || '''mcspi4_somi''' ⇔ || sdmmc4_dat0 || kpd_row6 || gpio_153 || - || - || -
|-
| 27: MCSPI4_SIMO || AF20 || M7, Pullup || '''mcspi4_simo''' ⇔ || sdmmc4_cmd || kpd_col7 || gpio_152 || - || - || -
|-
| 29: MCSPI4_CLK || AE21 || M7, Pulldown || '''mcspi4_clk''' ⇔ || sdmmc4_clk || kpd_col6 || gpio_151 || - || - || -
|-
| 31: MCSPI4_CS0 || AE20 || M7, Pullup || '''mcspi4_cs0''' ⇔↓ || sdmmc4_dat3 || kpd_row7 || gpio_154 || - || - || -
|}

=== Notes ===

a) Assigned as such in u-boot but reassigned in the kernel board startup code to Mode 3 Outputs

b) A design error resulted in an internal 10K pull up to 1.8 internal to the DuoVero on the HDQ_SIO line. Do not enable a pull down on this line. This will result in a non-logic output level (approximately 1V).

c) There are pullups on I2C2 and I2C3 of approximately 1K. S/C current is over 2mA.

Duovero Multiplexes

2013-11-25T14:14:37Z

Conor O'Rourke: Add an indication of current U-Boot settings with bold and arrows.

[[Category:How_to_-_linux]]
[[Category:Connect_hardware]]

This wiki entry concentrates on the Duovero Parlor board and the Multiplexes available from the 40 pin connector.

[[File:Duovero parlor conn small.png]]

The ground pin is nearest the console connector port and the power pins are nearest the centre of the board. This is as of writing but it is highly recommended that you ''check'' before connecting! Use a voltmeter to check the 3.3V, 5V and 1.8V pins to familiarise yourself with the layout.

There are also two connections on the Parlor board:

<blockquote>
{| class="wikitable"
|-
! OMAP Pin !! GPIO # !! Purpose
|-
| AG24 || GPIO121 || user push button
|-
| AH24 || GPIO122 || user LED
|}
</blockquote>

You should start your journey [http://gumstix.org/hardware-design/duovero-coms.html here].

The primary reference for multiplexes and pin functions is the Texas Instruments OMAP4 technical reference manual. The short version of that 6000 page manual is the OMAP4430 datasheet which is easier to search. The primary source reference is in the Uboot [https://github.com/gumstix/u-boot/tree/v2013.07/board/duovero code], specifically <tt>duovero_mux_data.h</tt> which uses the defines from <tt>./arch/arm/include/asm/arch-omap4/mux_omap4.h</tt>.

== Software Muxing ==

A helpful post from Phil Lutz describes how multiplexing can be explored without kernel recompilation. The default multiplex for the user LED may not be set to GPIO in Uboot. It certainly is not set to GPIO by the OMAP itself. You can look at the OMAP datasheet on page 48 you can see that the official name for GPIO 122 pin is "abe_dmic_din3" (Mode 0 names are accepted pin names).

This information can also be found by searching for "gpio_122" in the board pinmuxing configuration stored in sysfs: <tt>/sys/kernel/debug/omap_mux/board/core</tt>. Every pin which can be configured as gpio has a hint about that.

So now just check which is the current pinmuxing configuration for this pin by:

<pre>
$ cat /sys/kernel/debug/omap_mux/abe_dmic_din3
name: abe_dmic_din3.abe_dmic_din3 (0x4a100116/0x116 = 0x0100), b ah24, t NA
mode: OMAP_PIN_INPUT | OMAP_MUX_MODE0
signals: abe_dmic_din3 | slimbus2_data | abe_dmic_clk2 | gpio_122 | NA | dmtimer9_pwm_evt | NA | safe_mode
</pre>

As the output suggests, the pin is configured in MODE0, this is 'abe_dmic_din3'. The other modes are listed in order as they appear in the OMAP data manual. gpio_122 is multiplex MODE 3. You can set it with:

$ echo 3 > /sys/kernel/debug/omap_mux/abe_dmic_din3

Now you can turn on and off the LED using the usual gpio configuration in /sys/class/gpio/ (google it!). Note that "echo 3" does more than set Mode 3. The number is a selection of bits that set various states for the pin. A quick summary is:
<blockquote>
{| class="wikitable"
|-
|width="100pt" |Bit 0,1,2 || Set the mode
|-
|Bit 3 || 0 = pull up/down disabled , 1 = enabled
|-
|Bit 4 || 0 = pull down, 1 = pull up
|-
|Bit 8 || 0 = Output only. 1 = input enable (bidirectional)
|}
</blockquote>

There are more but these are for sleep modes and wakeup. The manual has details. The defines in mux_omap4.h are useful for interpreting the duovero_mux_data.h file:

<blockquote>

{| class="wikitable"
|-
|IEN || 1 << 8 || Input enable (bidirectional)
|-
|IDIS || 0 << 8 || Output only
|-
|PTU   || 3 << 3   || Enable Pullup
|-
|PTD || 1 << 3 || Enable Pulldown
|-
|EN || 1 << 3 || PU/PD enable
|-
|DIS || 0 << 3 || PU/PD disable
|}

</blockquote>

== Parlor pin mux table ==

To assist in figuring out which pins on the Parlor board can be assigned to which duties, here's a table of functions. Mode 7 is "safe_mode" where the pin is effectively disconnected from any functionality. It's set to high impedance (Z) and is left out of the table. The bolded functions are those set by the current U-Boot duovero_mux_data.h. This file sets other parameters (eg: output only, disable pullup/pulldown, etc) and you must refer to the U-Boot file to know what the full state is. A partial indication of the state (wake mode) is indicated in the table by arrows (bidirectional, output, pullup, pulldown).

{| class="wikitable"
|-
! Connector Description !! OMAP Pin !! Reset state !! Mode 0 !! Mode 1 !! Mode 2 !! Mode 3 !! Mode 4 !! Mode 5 !! Mode 6
|-
| User LED || AH24 || M7, Pulldown   || '''abe_dmic_din3''' ⇔ || slimbus2_data || abe_dmic_clk2 || gpio_122 || - || dmtimer9_pwm_evt || -
|-
| Button || AG24 || M7, Pulldown || '''abe_dmic_din2''' ⇔ || slimbus2_clock || abe_mcasp_axr || gpio_121 || - || dmtimer11_pwm_evt || -
|-
| 04: MCSPI1_CS0 || AE23 || M7, Pulldown || '''mcspi1_cs0''' ⇔↓ || - || - || gpio_137 || - || - || -
|-
| 06: MCSPI1_CS1 || AF23 || M7, Pulldown || '''mcspi1_cs1''' ⇔↓ || uart1_rx || - || gpio_138 || - || - || -
|-
| 08: MCSPI1_CS2 || AG23 || M7, Pullup || mcspi1_cs2 || uart1_cts || slimbus2_clock || gpio_139 || - || - || -
|-
| 10: MCSPI1_CS3 || AH23 || M7, Pullup || mcspi1_cs3 || uart1_rts || slimbus2_data || gpio_140 || - || - || -
|-
| 03: MCSPI1_CLK || AF22 || M7, Pulldown || '''mcspi1_clk''' ⇔ || - || - || gpio_134 || - || - || -
|-
| 05: MCSPI1_SIMO || AG22 || M7, Pulldown || '''mcspi1_simo''' ⇔ || - || - || gpio_136 || - || - || -
|-
| 07: MCSPI1_SOMI || AE22 || M7, Pulldown || '''mcspi1_somi''' ⇔ || - || - || gpio_135 || - || - || -
|-
| 09: HDQ_SIO || AA27 || M7, Z || '''hdq_sio''' ⇒ || i2c3_sccb || i2c2_sccb || gpio_127 || - || - || -
|-
| 12: I2C2_SCL || C26 || M7, Pullup || '''i2c2_scl''' ⇔↑ || uart1_rx || - || gpio_128 || - || - || -
|-
| 14: I2C2_SDA || D26 || M7, Pullup || '''i2c2_sda''' ⇔↑ || uart1_tx || - || gpio_129 || - || - || -
|-
| 11: SDMMC3_CMD || AG10 || M7, Pullup || usbb2_ulpitll_dat6 || usbb2_ulpiphy_dat6 || sdmmc3_cmd || '''gpio_167''' ⇔↑ || mcspi3_simo || dispc2_data12 || rfbi_data12
|-
| 13: SDMMC3_CLK || AE9 || M7, Pullup || usbb2_ulpitll_dat7 || usbb2_ulpiphy_dat7 || sdmmc3_clk || '''gpio_168''' ⇔↑ || mcspi3_clk || dispc2_data11 || rfbi_data11
|-
| 15: UART2_TX || AA26 || M7, Pullup || '''uart2_tx''' ⇒ || sdmmc3_dat1 || - || gpio_126 || - || - || -
|-
| 17: UART2_RX || AA25 || M7, Pullup || '''uart2_rx''' ⇔↑ || sdmmc3_dat0 || - || gpio_125 || - || - || -
|-
| 19: BSP2_CLKX || AD27 || M7, Pulldown || '''abe_mcbsp2_clkx''' ⇔ || mcspi2_clk || abe_mcasp_ahclkx || gpio_110 || usbb2_mm_rxdm || - || -
|-
| 20: BSP2_FSX || AC28 || M7, Pulldown || '''abe_mcbsp2_fsx''' ⇔ || mcspi2_cs0 || abe_mcasp_afsx || gpio_113 || usbb2_mm_txen || - || -
|-
| 21: BSP2_DX || AD25 || M7, Pulldown || '''abe_mcbsp2_dx''' ⇒ || mcspi2_simo || abe_mcasp_amute || gpio_112 || usbb2_mm_rxrcv || - || -
|-
| 22: BSP2_DR || AD26 || M7, Pulldown || '''abe_mcbsp2_dr''' ⇔ || mcspi2_somi || abe_mcasp_axr || gpio_111 || usbb2_mm_rxdp || - || -
|-
| 23: BSP_CLKS || AH26 || M7, Pulldown || '''abe_clks''' ⇔↓ || - || - || gpio_118 || - || - || -
|-
| 25: MCSPI4_SOMI || AF21 || M7, Pullup || '''mcspi4_somi''' ⇔ || sdmmc4_dat0 || kpd_row6 || gpio_153 || - || - || -
|-
| 27: MCSPI4_SIMO || AF20 || M7, Pullup || '''mcspi4_simo''' ⇔ || sdmmc4_cmd || kpd_col7 || gpio_152 || - || - || -
|-
| 29: MCSPI4_CLK || AE21 || M7, Pulldown || '''mcspi4_clk''' ⇔ || sdmmc4_clk || kpd_col6 || gpio_151 || - || - || -
|-
| 31: MCSPI4_CS0 || AE20 || M7, Pullup || '''mcspi4_cs0''' ⇔↓ || sdmmc4_dat3 || kpd_row7 || gpio_154 || - || - || -
|}

Kernel Build

2013-11-25T12:14:27Z

Conor O'Rourke:

This wiki entry adds a few details on building the Gumstix Linux kernel and bootloader from source.

Start by installing the [http://wiki.gumstix.org/index.php?title=Toolchain toolchain].

You will also need the U-boot 'mkimage' utility. Debian and Ubuntu users can install it from their respective repositories. It's also compiled when U-boot is built if you can't get it otherwise. On top of that you will need 'git' and 'make'.
$ sudo apt-get install uboot-mkimage git make

The official kernel build [http://gumstix.org/basic-cross-compilation.html instructions] are the best source to describe building a kernel and are up to date. The gumstix kernels are stored on [https://github.com/gumstix/linux github] and are in different branches for differing platforms. There is a table of branches against platforms on the [http://gumstix.org/access-source-code.html gumstix.org website].

The most usual way to pull the source code is using git:

$ git clone --branch omap-3.6 git://github.com/gumstix/linux.git linux

will clone the entire source tree to your machine and checkout the omap-3.6 branch into the "linux" directory. You can also use <tt>https</tt> instead of <tt>git</tt>. There are plenty of guides online to using git but a few timesaving methods are worth mentioning:

=== Cloning a shallow tree ===

You can clone just the tip of the relevant branch using a shallow clone. This has some restrictions but saves time and bandwidth:

<nowiki>$ git clone --depth 1 --branch omap-3.6 https://github.com/gumstix/linux.git omap-3.6</nowiki>

As of November 2013, this will pull 190MB from the server instead of over a gigabyte.

You can also pull a zip file of this branch, either using the [https://github.com/gumstix/linux website] or by finding the appropriate link (use the website!) and using curl or wget.

<nowiki>$ wget https://github.com/gumstix/linux/archive/omap-3.6.zip</nowiki>

(this will do a 301 redirect so be aware of this - you might get a very small file with html in it!)

For the 3.6 branch, this will pull approximately 123MB from the github server.

=== Subtleties ===

There is absolutely no difference in result aside from the presence of the ".git" directory, but this has a few subtle consequences. If you build with the zip file, you will get kernel and module versions stamped "3.6.0". If you build from the git repository, the make process:

* detects the git repository presence
* see that the checkout is not stamped with a tag (eg: "3.6.0").
* adds a + to all versions to show that the repository is not officially 3.6.0.

Thus you will get kernel and module version stamped with "3.6.0+". If you try and load a 3.6.0+ module into a 3.6.0 kernel, it will fail with an "invalid module format" error. You can force it with "modprobe -f" but that isn't really a recommended action generally. The normal procedure is to install the kernel and modules together (see the [http://gumstix.org/basic-cross-compilation.html website] for details.

You can override the version modification by setting LOCALVERSION (to anything) before running make.

== U-Boot ==

The source for U-Boot is held in [https://github.com/gumstix/u-boot github]. The branch that the Yocto recipes are using is currently 2013.07 (although there is a 2013.10 branch too). You can checkout the branch with:

$ git clone --branch v2013.07 git://github.com/gumstix/u-boot.git

or some variation of same (see above). You can also pull the zip file directly in the same way as above. You can configure U-Boot for:

Overo:
$ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- omap3_overo_config

Duovero:
$ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- omap4_duovero_config

Then build u-boot:
$ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- all

This should create MLO, u-boot.bin and u-boot.img in your u-boot directory.

Kernel Build

2013-11-25T12:13:31Z

Conor O'Rourke: Add U-Boot details

This wiki entry adds a few details on building the Gumstix Linux kernel and bootloader from source.

Start by installing the [http://wiki.gumstix.org/index.php?title=Toolchain toolchain].

You will also need the U-boot 'mkimage' utility. Debian and Ubuntu users can install it from their respective repositories. It's also compiled when U-boot is built if you can't get it otherwise. On top of that you will need 'git' and 'make'.
$ sudo apt-get install uboot-mkimage git make

The official kernel build [http://gumstix.org/basic-cross-compilation.html instructions] are the best source to describe building a kernel and are up to date. The gumstix kernels are stored on [https://github.com/gumstix/linux github] and are in different branches for differing platforms. There is a table of branches against platforms on the [http://gumstix.org/access-source-code.html gumstix.org website].

The most usual way to pull the source code is using git:

$ git clone --branch omap-3.6 git://github.com/gumstix/linux.git linux

will clone the entire source tree to your machine and checkout the omap-3.6 branch into the "linux" directory. You can also use <tt>https</tt> instead of <tt>git</tt>. There are plenty of guides online to using git but a few timesaving methods are worth mentioning:

=== Cloning a shallow tree ===

You can clone just the tip of the relevant branch using a shallow clone. This has some restrictions but saves time and bandwidth:

<nowiki>$ git clone --depth 1 --branch omap-3.6 https://github.com/gumstix/linux.git omap-3.6</nowiki>

As of November 2013, this will pull 190MB from the server instead of over a gigabyte.

You can also pull a zip file of this branch, either using the [https://github.com/gumstix/linux website] or by finding the appropriate link (use the website!) and using curl or wget.

<nowiki>$ wget https://github.com/gumstix/linux/archive/omap-3.6.zip</nowiki>

(this will do a 301 redirect so be aware of this - you might get a very small file with html in it!)

For the 3.6 branch, this will pull approximately 123MB from the github server.

=== Subtleties ===

There is absolutely no difference in result aside from the presence of the ".git" directory, but this has a few subtle consequences. If you build with the zip file, you will get kernel and module versions stamped "3.6.0". If you build from the git repository, the make process:

* detects the git repository presence
* see that the checkout is not stamped with a tag (eg: "3.6.0").
* adds a + to all versions to show that the repository is not officially 3.6.0.

Thus you will get kernel and module version stamped with "3.6.0+". If you try and load a 3.6.0+ module into a 3.6.0 kernel, it will fail with an "invalid module format" error. You can force it with "modprobe -f" but that isn't really a recommended action generally. The normal procedure is to install the kernel and modules together (see the [http://gumstix.org/basic-cross-compilation.html website] for details.

You can override the version modification by setting LOCALVERSION (to anything) before running make.

=== U-Boot ===

The source for U-Boot is held in [https://github.com/gumstix/u-boot github]. The branch that the Yocto recipes are using is currently 2013.07 (although there is a 2013.10 branch too). You can checkout the branch with:

$ git clone --branch v2013.07 git://github.com/gumstix/u-boot.git

or some variation of same (see above). You can also pull the zip file directly in the same way as above. You can configure U-Boot for:

Overo:
$ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- omap3_overo_config

Duovero:
$ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- omap4_duovero_config

Then build u-boot:
$ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- all

This should create MLO, u-boot.bin and u-boot.img in your u-boot directory.

Duovero Multiplexes

2013-11-19T16:00:58Z

Conor O'Rourke: Add into categories

[[Category:How_to_-_linux]]
[[Category:Connect_hardware]]

This wiki entry concentrates on the Duovero Parlor board and the Multiplexes available from the 40 pin connector.

[[File:Duovero parlor conn small.png]]

The ground pin is nearest the console connector port and the power pins are nearest the centre of the board. This is as of writing but it is highly recommended that you ''check'' before connecting! Use a voltmeter to check the 3.3V, 5V and 1.8V pins to familiarise yourself with the layout.

There are also two connections on the Parlor board:

<blockquote>
{| class="wikitable"
|-
! OMAP Pin !! GPIO # !! Purpose
|-
| AG24 || GPIO121 || user push button
|-
| AH24 || GPIO122 || user LED
|}
</blockquote>

You should start your journey [http://gumstix.org/hardware-design/duovero-coms.html here].

The primary reference for multiplexes and pin functions is the Texas Instruments OMAP4 technical reference manual. The short version of that 6000 page manual is the OMAP4430 datasheet which is easier to search. The primary source reference is in the Uboot [https://github.com/gumstix/u-boot/tree/v2013.07/board/duovero code], specifically <tt>duovero_mux_data.h</tt> which uses the defines from <tt>./arch/arm/include/asm/arch-omap4/mux_omap4.h</tt>.

== Software Muxing ==

A helpful post from Phil Lutz describes how multiplexing can be explored without kernel recompilation. The default multiplex for the user LED may not be set to GPIO in Uboot. It certainly is not set to GPIO by the OMAP itself. You can look at the OMAP datasheet on page 48 you can see that the official name for GPIO 122 pin is "abe_dmic_din3" (Mode 0 names are accepted pin names).

This information can also be found by searching for "gpio_122" in the board pinmuxing configuration stored in sysfs: <tt>/sys/kernel/debug/omap_mux/board/core</tt>. Every pin which can be configured as gpio has a hint about that.

So now just check which is the current pinmuxing configuration for this pin by:

<pre>
$ cat /sys/kernel/debug/omap_mux/abe_dmic_din3
name: abe_dmic_din3.abe_dmic_din3 (0x4a100116/0x116 = 0x0100), b ah24, t NA
mode: OMAP_PIN_INPUT | OMAP_MUX_MODE0
signals: abe_dmic_din3 | slimbus2_data | abe_dmic_clk2 | gpio_122 | NA | dmtimer9_pwm_evt | NA | safe_mode
</pre>

As the output suggests, the pin is configured in MODE0, this is 'abe_dmic_din3'. The other modes are listed in order as they appear in the OMAP data manual. gpio_122 is multiplex MODE 3. You can set it with:

$ echo 3 > /sys/kernel/debug/omap_mux/abe_dmic_din3

Now you can turn on and off the LED using the usual gpio configuration in /sys/class/gpio/ (google it!). Note that "echo 3" does more than set Mode 3. The number is a selection of bits that set various states for the pin. A quick summary is:
<blockquote>
{| class="wikitable"
|-
|width="100pt" |Bit 0,1,2 || Set the mode
|-
|Bit 3 || 0 = pull up/down disabled , 1 = enabled
|-
|Bit 4 || 0 = pull down, 1 = pull up
|-
|Bit 8 || 0 = Output only. 1 = input enable (bidirectional)
|}
</blockquote>

There are more but these are for sleep modes and wakeup. The manual has details. The defines in mux_omap4.h are useful for interpreting the duovero_mux_data.h file:

<blockquote>

{| class="wikitable"
|-
|IEN || 1 << 8 || Input enable (bidirectional)
|-
|IDIS || 0 << 8 || Output only
|-
|PTU   || 3 << 3   || Enable Pullup
|-
|PTD || 1 << 3 || Enable Pulldown
|-
|EN || 1 << 3 || PU/PD enable
|-
|DIS || 0 << 3 || PU/PD disable
|}

</blockquote>

== Parlor pin mux table ==

To assist in figuring out which pins on the Parlor board can be assigned to which duties, here's a table of functions. Mode 7 is "safe_mode" where the pin is effectively disconnected from any functionality. It's set to high impedance (Z). I leave it out of the following table:

{| class="wikitable"
|-
! Connector Description !! OMAP Pin !! Reset state !! Mode 0 !! Mode 1 !! Mode 2 !! Mode 3 !! Mode 4 !! Mode 5 !! Mode 6
|-
| User LED || AH24 || M7, Pulldown   || abe_dmic_din3 || slimbus2_data || abe_dmic_clk2 || gpio_122 || - || dmtimer9_pwm_evt || -
|-
| Button || AG24 || M7, Pulldown || abe_dmic_din2 || slimbus2_clock || abe_mcasp_axr || gpio_121 || - || dmtimer11_pwm_evt || -
|-
| 04: MCSPI1_CS0 || AE23 || M7, Pulldown || mcspi1_cs0 || - || - || gpio_137 || - || - || -
|-
| 06: MCSPI1_CS1 || AF23 || M7, Pulldown || mcspi1_cs1 || uart1_rx || - || gpio_138 || - || - || -
|-
| 08: MCSPI1_CS2 || AG23 || M7, Pullup || mcspi1_cs2 || uart1_cts || slimbus2_clock || gpio_139 || - || - || -
|-
| 10: MCSPI1_CS3 || AH23 || M7, Pullup || mcspi1_cs3 || uart1_rts || slimbus2_data || gpio_140 || - || - || -
|-
| 03: MCSPI1_CLK || AF22 || M7, Pulldown || mcspi1_clk || - || - || gpio_134 || - || - || -
|-
| 05: MCSPI1_SIMO || AG22 || M7, Pulldown || mcspi1_simo || - || - || gpio_136 || - || - || -
|-
| 07: MCSPI1_SOMI || AE22 || M7, Pulldown || mcspi1_somi || - || - || gpio_135 || - || - || -
|-
| 09: HDQ_SIO || AA27 || M7, Z || hdq_sio || i2c3_sccb || i2c2_sccb || gpio_127 || - || - || -
|-
| 12: I2C2_SCL || C26 || M7, Pullup || i2c2_scl || uart1_rx || - || gpio_128 || - || - || -
|-
| 14: I2C2_SDA || D26 || M7, Pullup || i2c2_sda || uart1_tx || - || gpio_129 || - || - || -
|-
| 11: SDMMC3_CMD || AG10 || M7, Pullup || usbb2_ulpitll_dat6 || usbb2_ulpiphy_dat6 || sdmmc3_cmd || gpio_167 || mcspi3_simo || dispc2_data12 || rfbi_data12
|-
| 13: SDMMC3_CLK || AE9 || M7, Pullup || usbb2_ulpitll_dat7 || usbb2_ulpiphy_dat7 || sdmmc3_clk || gpio_168 || mcspi3_clk || dispc2_data11 || rfbi_data11
|-
| 15: UART2_TX || AA26 || M7, Pullup || uart2_tx || sdmmc3_dat1 || - || gpio_126 || - || - || -
|-
| 17: UART2_RX || AA25 || M7, Pullup || uart2_rx || sdmmc3_dat0 || - || gpio_125 || - || - || -
|-
| 19: BSP2_CLKX || AD27 || M7, Pulldown || abe_mcbsp2_clkx || mcspi2_clk || abe_mcasp_ahclkx || gpio_110 || usbb2_mm_rxdm || - || -
|-
| 20: BSP2_FSX || AC28 || M7, Pulldown || abe_mcbsp2_fsx || mcspi2_cs0 || abe_mcasp_afsx || gpio_113 || usbb2_mm_txen || - || -
|-
| 21: BSP2_DX || AD25 || M7, Pulldown || abe_mcbsp2_dx || mcspi2_simo || abe_mcasp_amute || gpio_112 || usbb2_mm_rxrcv || - || -
|-
| 22: BSP2_DR || AD26 || M7, Pulldown || abe_mcbsp2_dr || mcspi2_somi || abe_mcasp_axr || gpio_111 || usbb2_mm_rxdp || - || -
|-
| 23: BSP_CLKS || AH26 || M7, Pulldown || abe_clks || - || - || gpio_118 || - || - || -
|-
| 25: MCSPI4_SOMI || AF21 || M7, Pullup || mcspi4_somi || sdmmc4_dat0 || kpd_row6 || gpio_153 || - || - || -
|-
| 27: MCSPI4_SIMO || AF20 || M7, Pullup || mcspi4_simo || sdmmc4_cmd || kpd_col7 || gpio_152 || - || - || -
|-
| 29: MCSPI4_CLK || AE21 || M7, Pulldown || mcspi4_clk || sdmmc4_clk || kpd_col6 || gpio_151 || - || - || -
|-
| 31: MCSPI4_CS0 || AE20 || M7, Pullup || mcspi4_cs0 || sdmmc4_dat3 || kpd_row7 || gpio_154 || - || - || -
|}

Duovero Multiplexes

2013-11-19T15:08:24Z

Conor O'Rourke: Duovero hardware and pin muxes

This wiki entry concentrates on the Duovero Parlor board and the Multiplexes available from the 40 pin connector.

[[File:Duovero parlor conn small.png]]

The ground pin is nearest the console connector port and the power pins are nearest the centre of the board. This is as of writing but it is highly recommended that you ''check'' before connecting! Use a voltmeter to check the 3.3V, 5V and 1.8V pins to familiarise yourself with the layout.

There are also two connections on the Parlor board:

<blockquote>
{| class="wikitable"
|-
! OMAP Pin !! GPIO # !! Purpose
|-
| AG24 || GPIO121 || user push button
|-
| AH24 || GPIO122 || user LED
|}
</blockquote>

You should start your journey [http://gumstix.org/hardware-design/duovero-coms.html here].

The primary reference for multiplexes and pin functions is the Texas Instruments OMAP4 technical reference manual. The short version of that 6000 page manual is the OMAP4430 datasheet which is easier to search. The primary source reference is in the Uboot [https://github.com/gumstix/u-boot/tree/v2013.07/board/duovero code], specifically <tt>duovero_mux_data.h</tt> which uses the defines from <tt>./arch/arm/include/asm/arch-omap4/mux_omap4.h</tt>.

== Software Muxing ==

A helpful post from Phil Lutz describes how multiplexing can be explored without kernel recompilation. The default multiplex for the user LED may not be set to GPIO in Uboot. It certainly is not set to GPIO by the OMAP itself. You can look at the OMAP datasheet on page 48 you can see that the official name for GPIO 122 pin is "abe_dmic_din3" (Mode 0 names are accepted pin names).

This information can also be found by searching for "gpio_122" in the board pinmuxing configuration stored in sysfs: <tt>/sys/kernel/debug/omap_mux/board/core</tt>. Every pin which can be configured as gpio has a hint about that.

So now just check which is the current pinmuxing configuration for this pin by:

<pre>
$ cat /sys/kernel/debug/omap_mux/abe_dmic_din3
name: abe_dmic_din3.abe_dmic_din3 (0x4a100116/0x116 = 0x0100), b ah24, t NA
mode: OMAP_PIN_INPUT | OMAP_MUX_MODE0
signals: abe_dmic_din3 | slimbus2_data | abe_dmic_clk2 | gpio_122 | NA | dmtimer9_pwm_evt | NA | safe_mode
</pre>

As the output suggests, the pin is configured in MODE0, this is 'abe_dmic_din3'. The other modes are listed in order as they appear in the OMAP data manual. gpio_122 is multiplex MODE 3. You can set it with:

$ echo 3 > /sys/kernel/debug/omap_mux/abe_dmic_din3

Now you can turn on and off the LED using the usual gpio configuration in /sys/class/gpio/ (google it!). Note that "echo 3" does more than set Mode 3. The number is a selection of bits that set various states for the pin. A quick summary is:
<blockquote>
{| class="wikitable"
|-
|width="100pt" |Bit 0,1,2 || Set the mode
|-
|Bit 3 || 0 = pull up/down disabled , 1 = enabled
|-
|Bit 4 || 0 = pull down, 1 = pull up
|-
|Bit 8 || 0 = Output only. 1 = input enable (bidirectional)
|}
</blockquote>

There are more but these are for sleep modes and wakeup. The manual has details. The defines in mux_omap4.h are useful for interpreting the duovero_mux_data.h file:

<blockquote>

{| class="wikitable"
|-
|IEN || 1 << 8 || Input enable (bidirectional)
|-
|IDIS || 0 << 8 || Output only
|-
|PTU   || 3 << 3   || Enable Pullup
|-
|PTD || 1 << 3 || Enable Pulldown
|-
|EN || 1 << 3 || PU/PD enable
|-
|DIS || 0 << 3 || PU/PD disable
|}

</blockquote>

== Parlor pin mux table ==

To assist in figuring out which pins on the Parlor board can be assigned to which duties, here's a table of functions. Mode 7 is "safe_mode" where the pin is effectively disconnected from any functionality. It's set to high impedance (Z). I leave it out of the following table:

{| class="wikitable"
|-
! Connector Description !! OMAP Pin !! Reset state !! Mode 0 !! Mode 1 !! Mode 2 !! Mode 3 !! Mode 4 !! Mode 5 !! Mode 6
|-
| User LED || AH24 || M7, Pulldown   || abe_dmic_din3 || slimbus2_data || abe_dmic_clk2 || gpio_122 || - || dmtimer9_pwm_evt || -
|-
| Button || AG24 || M7, Pulldown || abe_dmic_din2 || slimbus2_clock || abe_mcasp_axr || gpio_121 || - || dmtimer11_pwm_evt || -
|-
| 04: MCSPI1_CS0 || AE23 || M7, Pulldown || mcspi1_cs0 || - || - || gpio_137 || - || - || -
|-
| 06: MCSPI1_CS1 || AF23 || M7, Pulldown || mcspi1_cs1 || uart1_rx || - || gpio_138 || - || - || -
|-
| 08: MCSPI1_CS2 || AG23 || M7, Pullup || mcspi1_cs2 || uart1_cts || slimbus2_clock || gpio_139 || - || - || -
|-
| 10: MCSPI1_CS3 || AH23 || M7, Pullup || mcspi1_cs3 || uart1_rts || slimbus2_data || gpio_140 || - || - || -
|-
| 03: MCSPI1_CLK || AF22 || M7, Pulldown || mcspi1_clk || - || - || gpio_134 || - || - || -
|-
| 05: MCSPI1_SIMO || AG22 || M7, Pulldown || mcspi1_simo || - || - || gpio_136 || - || - || -
|-
| 07: MCSPI1_SOMI || AE22 || M7, Pulldown || mcspi1_somi || - || - || gpio_135 || - || - || -
|-
| 09: HDQ_SIO || AA27 || M7, Z || hdq_sio || i2c3_sccb || i2c2_sccb || gpio_127 || - || - || -
|-
| 12: I2C2_SCL || C26 || M7, Pullup || i2c2_scl || uart1_rx || - || gpio_128 || - || - || -
|-
| 14: I2C2_SDA || D26 || M7, Pullup || i2c2_sda || uart1_tx || - || gpio_129 || - || - || -
|-
| 11: SDMMC3_CMD || AG10 || M7, Pullup || usbb2_ulpitll_dat6 || usbb2_ulpiphy_dat6 || sdmmc3_cmd || gpio_167 || mcspi3_simo || dispc2_data12 || rfbi_data12
|-
| 13: SDMMC3_CLK || AE9 || M7, Pullup || usbb2_ulpitll_dat7 || usbb2_ulpiphy_dat7 || sdmmc3_clk || gpio_168 || mcspi3_clk || dispc2_data11 || rfbi_data11
|-
| 15: UART2_TX || AA26 || M7, Pullup || uart2_tx || sdmmc3_dat1 || - || gpio_126 || - || - || -
|-
| 17: UART2_RX || AA25 || M7, Pullup || uart2_rx || sdmmc3_dat0 || - || gpio_125 || - || - || -
|-
| 19: BSP2_CLKX || AD27 || M7, Pulldown || abe_mcbsp2_clkx || mcspi2_clk || abe_mcasp_ahclkx || gpio_110 || usbb2_mm_rxdm || - || -
|-
| 20: BSP2_FSX || AC28 || M7, Pulldown || abe_mcbsp2_fsx || mcspi2_cs0 || abe_mcasp_afsx || gpio_113 || usbb2_mm_txen || - || -
|-
| 21: BSP2_DX || AD25 || M7, Pulldown || abe_mcbsp2_dx || mcspi2_simo || abe_mcasp_amute || gpio_112 || usbb2_mm_rxrcv || - || -
|-
| 22: BSP2_DR || AD26 || M7, Pulldown || abe_mcbsp2_dr || mcspi2_somi || abe_mcasp_axr || gpio_111 || usbb2_mm_rxdp || - || -
|-
| 23: BSP_CLKS || AH26 || M7, Pulldown || abe_clks || - || - || gpio_118 || - || - || -
|-
| 25: MCSPI4_SOMI || AF21 || M7, Pullup || mcspi4_somi || sdmmc4_dat0 || kpd_row6 || gpio_153 || - || - || -
|-
| 27: MCSPI4_SIMO || AF20 || M7, Pullup || mcspi4_simo || sdmmc4_cmd || kpd_col7 || gpio_152 || - || - || -
|-
| 29: MCSPI4_CLK || AE21 || M7, Pulldown || mcspi4_clk || sdmmc4_clk || kpd_col6 || gpio_151 || - || - || -
|-
| 31: MCSPI4_CS0 || AE20 || M7, Pullup || mcspi4_cs0 || sdmmc4_dat3 || kpd_row7 || gpio_154 || - || - || -
|}

Duovero Multiplexes

2013-11-19T14:34:49Z

Conor O'Rourke: Still in progress!

This wiki entries concentrates on the Duovero Parlor board and the Multiplexes available from the 40 pin connector.

[[File:Duovero parlor conn small.png]]

The ground pin is nearest the console connector port and the power pins are nearest the centre of the board. This is as of writing but it is highly recommended that you ''check'' before connecting! Use a voltmeter to check the 3.3V, 5V and 1.8V pins to familiarise yourself with the layout.

There are also two connections on the Parlor board:

<blockquote>
{| class="wikitable"
|-
! OMAP Pin !! GPIO # !! Purpose
|-
| AG24 || GPIO121 || user push button
|-
| AH24 || GPIO122 || user LED
|}
</blockquote>

You should start your journey [http://gumstix.org/hardware-design/duovero-coms.html here].

The primary reference for multiplexes and pin functions is the Texas Instruments OMAP4 technical reference manual. The short version of that 6000 page manual is the OMAP4430 datasheet which is easier to search. The primary source reference is in the Uboot [https://github.com/gumstix/u-boot/tree/v2013.07/board/duovero code], specifically <tt>duovero_mux_data.h</tt> which uses the defines from <tt>./arch/arm/include/asm/arch-omap4/mux_omap4.h</tt>.

== Software Muxing ==

A helpful post from Phil Lutz describes how multiplexing can be explored without kernel recompilation. The default multiplex for the user LED may not be set to GPIO in Uboot. It certainly is not set to GPIO by the OMAP itself. You can look at the OMAP datasheet on page 48 you can see that the official name for GPIO 122 pin is "abe_dmic_din3" (Mode 0 names are accepted pin names).

This information can also be found by searching for "gpio_122" in the board pinmuxing configuration stored in sysfs: <tt>/sys/kernel/debug/omap_mux/board/core</tt>. Every pin which can be configured as gpio has a hint about that.

So now just check which is the current pinmuxing configuration for this pin by:

<pre>
$ cat /sys/kernel/debug/omap_mux/abe_dmic_din3
name: abe_dmic_din3.abe_dmic_din3 (0x4a100116/0x116 = 0x0100), b ah24, t NA
mode: OMAP_PIN_INPUT | OMAP_MUX_MODE0
signals: abe_dmic_din3 | slimbus2_data | abe_dmic_clk2 | gpio_122 | NA | dmtimer9_pwm_evt | NA | safe_mode
</pre>

As the output suggests, the pin is configured in MODE0, this is 'abe_dmic_din3'. The other modes are listed in order as they appear in the OMAP data manual. gpio_122 is multiplex MODE 3. You can set it with:

$ echo 3 > /sys/kernel/debug/omap_mux/abe_dmic_din3

Now you can turn on and off the LED using the usual gpio configuration in /sys/class/gpio/ (google it!). Note that "echo 3" does more than set Mode 3. The number is a selection of bits that set various states for the pin. A quick summary is:
<blockquote>
{|
|-
|width="100pt" |Bit 0,1,2 || Set the mode
|-
|Bit 3 || 0 = pull up/down disabled , 1 = enabled
|-
|Bit 4 || 0 = pull down, 1 = pull up
|-
|Bit 8 || 0 = Output only. 1 = input enable (bidirectional)
|}
</blockquote>

There are more but these are for sleep modes and wakeup. The manual has details. The defines in mux_omap4.h are useful for interpreting the duovero_mux_data.h file:

<blockquote>

{|
|-
! Define !! Set to      !! Purpose
|-
|IEN || 1 << 8 || Input enable (bidirectional)
|-
|IDIS || 0 << 8 || Output only
|-
|PTU || 3 << 3 || Enable Pullup
|-
|PTD || 1 << 3 || Enable Pulldown
|-
|EN || 1 << 3 || PU/PD enable
|-
|DIS || 0 << 3 || PU/PD disable
|}

</blockquote>

== Parlor pin mux table ==

To assist in figuring out which pins on the Parlor board can be assigned to which duties, here's a table of functions. Mode 7 is "safe_mode" where the pin is effectively disconnected from any functionality. It's set to high impedance (Z). I leave it out of the following table:

{| class="wikitable"
|-
! Connector Description !! OMAP Pin !! Reset state !! Mode 0 !! Mode 1 !! Mode 2 !! Mode 3 !! Mode 4 !! Mode 5 !! Mode 6
|-
| User LED || AH24 || M7, Pulldown || abe_dmic_din3 || slimbus2_data || abe_dmic_clk2 || gpio_122 || - || dmtimer9_pwm_evt || -
|-
| Button || AG24 || M7, Pulldown || abe_dmic_din2 || slimbus2_clock || abe_mcasp_axr || gpio_121 || - || dmtimer11_pwm_evt || -
|-
| 04: MCSPI1_CS0 || AE23 || M7, Pulldown || mcspi1_cs0 || - || - || gpio_137 || - || - || -
|-
| 06: MCSPI1_CS1 || AF23 || M7, Pulldown || mcspi1_cs1 || uart1_rx || - || gpio_138 || - || - || -
|-
| 08: MCSPI1_CS2 || AG23 || M7, Pullup || mcspi1_cs2 || uart1_cts || slimbus2_clock || gpio_139 || - || - || -
|-
| 10: MCSPI1_CS3 || AH23 || M7, Pullup || mcspi1_cs3 || uart1_rts || slimbus2_data || gpio_140 || - || - || -
|-
| 03: MCSPI1_CLK || AF22 || M7, Pulldown || mcspi1_clk || - || - || gpio_134 || - || - || -
|-
| 05: MCSPI1_SIMO || AG22 || M7, Pulldown || mcspi1_simo || - || - || gpio_136 || - || - || -
|-
| 07: MCSPI1_SOMI || AE22 || M7, Pulldown || mcspi1_somi || - || - || gpio_135 || - || - || -
|-
| 09: HDQ_SIO || AA27 || M7, Z || hdq_sio || i2c3_sccb || i2c2_sccb || gpio_127 || - || - || -
|-
| 12: I2C2_SCL || C26 || M7, Pullup || i2c2_scl || uart1_rx || - || gpio_128 || - || - || -
|-
| 14: I2C2_SDA || D26 || M7, Pullup || i2c2_sda || uart1_tx || - || gpio_129 || - || - || -
|-
| 11: SDMMC3_CMD || AG10 || M7, Pullup || usbb2_ulpitll_dat6 || usbb2_ulpiphy_dat6 || sdmmc3_cmd || gpio_167 || mcspi3_simo || dispc2_data12 || rfbi_data12
|-
| 13: SDMMC3_CLK || AE9 || M7, Pullup || usbb2_ulpitll_dat7 || usbb2_ulpiphy_dat7 || sdmmc3_clk || gpio_168 || mcspi3_clk || dispc2_data11 || rfbi_data11
|-
| 15: UART2_TX || AA26 || M7, Pullup || uart2_tx || sdmmc3_dat1 || - || gpio_126 || - || - || -
|-
| 17: UART2_RX || AA25 || M7, Pullup || uart2_rx || sdmmc3_dat0 || - || gpio_125 || - || - || -
|}

In progress...!

Duovero Multiplexes

2013-11-19T12:17:42Z

Conor O'Rourke: Page in progress...

File:Duovero parlor conn small.png

2013-11-19T11:33:33Z

Conor O'Rourke: Small version of File:duovero_parlor_conn.png

Small version of [[File:duovero_parlor_conn.png]]

File:Duovero parlor conn.png

2013-11-19T11:28:43Z

Conor O'Rourke: Duovero connector taken as a screenshot of the official circuit diagram pdf. This is copyright Gumstix.

Duovero connector taken as a screenshot of the official circuit diagram pdf. This is copyright Gumstix.

Kernel Build

2013-11-19T11:16:15Z

Conor O'Rourke:

This wiki entry adds a few details on building the Gumstix Linux kernel from source.

Start by installing the [http://wiki.gumstix.org/index.php?title=Toolchain toolchain].

You will also need the U-boot 'mkimage' utility. Debian and Ubuntu users can install it from their respective repositories. It's also compiled when U-boot is built if you can't get it otherwise. On top of that you will need 'git' and 'make'.
$ sudo apt-get install uboot-mkimage git make

The official kernel build [http://gumstix.org/basic-cross-compilation.html instructions] are the best source to describe building a kernel and are up to date. The gumstix kernels are stored on [https://github.com/gumstix/linux github] and are in different branches for differing platforms. There is a table of branches against platforms on the [http://gumstix.org/access-source-code.html gumstix.org website].

The most usual way to pull the source code is using git:

$ git clone --branch omap-3.6 git://github.com/gumstix/linux.git Linux

will clone the entire source tree to your machine and checkout the omap-3.6 branch into the "linux" directory. There are plenty of guides online to using git but a few timesaving methods are worth mentioning:

=== Cloning a shallow tree ===

You can clone just the tip of the relevant branch using a shallow clone. This has some restrictions but saves time and bandwidth:

<nowiki>$ git clone --depth 1 --branch omap-3.6 https://github.com/gumstix/linux.git omap-3.6</nowiki>

As of November 2013, this will pull 190MB from the server instead of over a gigabyte.

You can also pull a zip file of this branch, either using the [https://github.com/gumstix/linux website] or by finding the appropriate link (use the website!) and using curl or wget.

<nowiki>$ wget https://github.com/gumstix/linux/archive/omap-3.6.zip</nowiki>

(this will do a 301 redirect so be aware of this - you might get a very small file with html in it!)

For the 3.6 branch, this will pull approximately 123MB from the github server.

=== Subtleties ===

There is absolutely no difference in result aside from the presence of the ".git" directory, but this has a few subtle consequences. If you build with the zip file, you will get kernel and module versions stamped "3.6.0". If you build from the git repository, the make process:

* detects the git repository presence
* see that the checkout is not stamped with a tag (eg: "3.6.0").
* adds a + to all versions to show that the repository is not officially 3.6.0.

Thus you will get kernel and module version stamped with "3.6.0+". If you try and load a 3.6.0+ module into a 3.6.0 kernel, it will fail with an "invalid module format" error. You can force it with "modprobe -f" but that isn't really a recommended action generally. The normal procedure is to install the kernel and modules together (see the [http://gumstix.org/basic-cross-compilation.html website] for details.

You can override the version modification by setting LOCALVERSION (to anything) before running make.

Kernel Build

2013-11-19T11:15:46Z

Conor O'Rourke:

This wiki entry adds a few details on building the Gumstix Linux kernel from source.

Start by installing the [http://wiki.gumstix.org/index.php?title=Toolchain toolchain].

You will also need the U-boot 'mkimage' utility. Debian and Ubuntu users can install it from their respective repositories. It's also compiled when U-boot is built if you can't get it otherwise. On top of that you will need 'git' and 'make'.
$ sudo apt-get install uboot-mkimage git make

The official kernel build [http://gumstix.org/basic-cross-compilation.html instructions] are the best source to describe building a kernel and are up to date. The gumstix kernels are stored on [https://github.com/gumstix/linux github] and are in different branches for differing platforms. There is a table of branches against platforms on the [http://gumstix.org/access-source-code.html gumstix.org website].

The most usual way to pull the source code is using git:

$ git clone --branch omap-3.6 git://github.com/gumstix/linux.git Linux

will clone the entire source tree to your machine and checkout the omap-3.6 branch into the "linux" directory. There are plenty of guides online to using git but a few timesaving methods are worth mentioning:

=== Cloning a shallow tree ===

You can clone just the tip of the relevant branch using a shallow clone. This has some restrictions but saves time and bandwidth:

<nowiki>$ git clone --depth 1 --branch omap-3.6 https://github.com/gumstix/linux.git omap-3.6</nowiki>

As of November 2013, this will pull 190MB from the server instead of over a gigabyte.

You can also pull a zip file of this branch, either using the [https://github.com/gumstix/linux website] or by finding the appropriate link (use the website!) and using curl or wget.

<nowiki>$ wget https://github.com/gumstix/linux/archive/omap-3.6.zip</nowiki>

(this will do a 301 redirect so be aware of this - you might get a very small file with html in it!)

For the 3.6 branch, this will pull approximately 123MB from the github server.

== Subtleties ===

There is absolutely no difference in result aside from the presence of the ".git" directory, but this has a few subtle consequences. If you build with the zip file, you will get kernel and module versions stamped "3.6.0". If you build from the git repository, the make process:

* detects the git repository presence
* see that the checkout is not stamped with a tag (eg: "3.6.0").
* adds a + to all versions to show that the repository is not officially 3.6.0.

Thus you will get kernel and module version stamped with "3.6.0+". If you try and load a 3.6.0+ module into a 3.6.0 kernel, it will fail with an "invalid module format" error. You can force it with "modprobe -f" but that isn't really a recommended action generally. The normal procedure is to install the kernel and modules together (see the [http://gumstix.org/basic-cross-compilation.html website] for details.

You can override the version modification by setting LOCALVERSION (to anything) before running make.

Kernel Build

2013-11-19T11:14:39Z

Conor O'Rourke: Main website is up to date so just add hints and tips to this entry

This wiki entry adds a few details on building the Gumstix Linux kernel from source.

Start by installing the [http://wiki.gumstix.org/index.php?title=Toolchain toolchain].

You will also need the U-boot 'mkimage' utility. Debian and Ubuntu users can install it from their respective repositories. It's also compiled when U-boot is built if you can't get it otherwise. On top of that you will need 'git' and 'make'.
$ sudo apt-get install uboot-mkimage git make

The official kernel build [http://gumstix.org/basic-cross-compilation.html instructions] are the best source to describe building a kernel and are up to date. The gumstix kernels are stored on [https://github.com/gumstix/linux github] and are in different branches for differing platforms. There is a table of branches against platforms on the [http://gumstix.org/access-source-code.html gumstix.org website].

The most usual way to pull the source code is using git:

$ git clone --branch omap-3.6 git://github.com/gumstix/linux.git Linux

will clone the entire source tree to your machine and checkout the omap-3.6 branch into the "linux" directory. There are plenty of guides online to using git but a few timesaving methods are worth mentioning:

=== Cloning a shallow tree ===

You can clone just the tip of the relevant branch using a shallow clone. This has some restrictions but saves time and bandwidth:

<nowiki>$ git clone --depth 1 --branch omap-3.6 https://github.com/gumstix/linux.git omap-3.6</nowiki>

As of November 2013, this will pull 190MB from the server instead of over a gigabyte.

You can also pull a zip file of this branch, either using the [https://github.com/gumstix/linux website] or by finding the appropriate link (use the website!) and using curl or wget.

<nowiki>$ wget https://github.com/gumstix/linux/archive/omap-3.6.zip</nowiki>

(this will do a 301 redirect so be aware of this - you might get a very small file with html in it!)

For the 3.6 branch, this will and pull approximately 123MB from the github server.

There is absolutely no difference in result aside from the presence of the ".git" directory, but this has a few subtle consequences. If you build with the zip file, you will get kernel and module versions stamped "3.6.0". If you build from the git repository, the make process:

* detects the git repository presence
* see that the checkout is not stamped with a tag (eg: "3.6.0").
* adds a + to all versions to show that the repository is not officially 3.6.0.

Thus you will get kernel and module version stamped with "3.6.0+". If you try and load a 3.6.0+ module into a 3.6.0 kernel, it will fail with an "invalid module format" error. You can force it with "modprobe -f" but that isn't really a recommended action generally. The normal procedure is to install the kernel and modules together (see the [http://gumstix.org/basic-cross-compilation.html website] for details.

You can override the version modification by setting LOCALVERSION (to anything) before running make.