How to reconcile pinmux.h values generated by pinmux tool with code in U-Boot?

Sean:

The pin mux utility does not generate u-boot source code directly, but example code.  Its main use is to identify a pin mux

configuration that will bring out all the interfaces that are needed.  We do have good training for board porting here:

https://docs.google.com/file/d/0BzESOSf028mLTjlPYmVJTUlTODA/edit?usp=drive_web

The input enable defaults to IEN (InputEnabled) for Input and I/O signals and IDIS (Input disabled) for

output signals - based on the signal that is selected in the row.  You can change the Input Enable bit in the tool

by R clicking selected balls in the first column.  Input enable determines if the external signal gets enabled

into the connectted module.

MichaelT

Thanks for the response.

With the file pinmux.h auto generated from the pinmux tool, why is the transmit pin setup with input enabled:

MUX_VAL(CONTROL_PADCONF_UART0_RXD, (IEN | OFF | MODE0 )) /* UART0_RXD */\
MUX_VAL(CONTROL_PADCONF_UART0_TXD, (IEN | OFF | MODE0 )) /* UART0_TXD */\

Surely it should be setup as an output only?

Also I tried loading our board's pinmux .dat file into the pinmux tool, but am getting a bunch of errors such as:

INFO: At row 35 in GUI, Importing Mode 0 Name "GPMC_CSN3" for Mux Mode 1. "Reserved" in design file was changed to "Not Selected" to match current device model.
INFO: At row 35 in GUI, Importing Mode 0 Name "GPMC_CSN3" for Mux Mode 2. "Reserved" in design file was changed to "Not Selected" to match current device model.
INFO: At row 57 in GUI, Importing Mode 0 Name "LCD_VSYNC" for Mux Mode 2. "Reserved" in design file was changed to "Not Selected" to match current device model.
INFO: At row 58 in GUI, Importing Mode 0 Name "LCD_HSYNC" for Mux Mode 2. "Reserved" in design file was changed to "Not Selected" to match current device model.
Error: Ball with location string "2 ZCE E15 - ZCZ B15 - " with Mode 0 Name "PORZ" in design file was not found in the current device model.

Any ideas why I am getting these errors?  The file can be read OK by my co-worker.  I am using version 2.5 and he is using version 2.4.1, could that be the problem?

Sean:

You can ignore those errors.  If you scroll down in the release_notes.txt file (in Start menu) you will see discussion about that.

In v2.5.2 we have support for AM335x Rev 1.x and 2.x.  AM335xA is 2.x.  In v2.5.2 we removed ball locations from the tool where there

is not actual mode selection implemented - so if you import a file made with an earlier version of pin mux you will get those messages.

The "ExampleDesign_AM335x_Rev_2.x_GP_EVM_Profile_0.dat" file has Input Enabled for uart0_txd for some reason.  You can change the setting

in the tool.  Highlight the cell in the first column. R-Click and Edit Selected Pad Configs to change it.

MichaelT

Thanks, I was able to find a previous version of pin mux and that opened the design file without errors.

In the design the MMC1 data lines 0..7 are configured as IO IEN PD.  I assume PD means pull down?  If so, why would these lines be pull down when in the sample code in board/ti/am335x/mux.c for MMC1 they are configured pull up?  I would have expected a pull down in the pin mux tool to be configured as a pull down in the code too.

static struct module_pin_mux mmc1_pin_mux[] = {
        {OFFSET(gpmc_ad3), (MODE(1) | RXACTIVE | PULLUP_EN)},   /* MMC1_DAT3 */
        {OFFSET(gpmc_ad2), (MODE(1) | RXACTIVE | PULLUP_EN)},   /* MMC1_DAT2 */
        {OFFSET(gpmc_ad1), (MODE(1) | RXACTIVE | PULLUP_EN)},   /* MMC1_DAT1 */
        {OFFSET(gpmc_ad0), (MODE(1) | RXACTIVE | PULLUP_EN)},   /* MMC1_DAT0 */
        {OFFSET(gpmc_csn1), (MODE(2) | RXACTIVE | PULLUP_EN)},  /* MMC1_CLK */
        {OFFSET(gpmc_csn2), (MODE(2) | RXACTIVE | PULLUP_EN)},  /* MMC1_CMD */
        {OFFSET(gpmc_csn0), (MODE(7) | RXACTIVE | PULLUP_EN)},  /* MMC1_WP */
        {OFFSET(gpmc_advn_ale), (MODE(7) | RXACTIVE | PULLUP_EN)},      /* MMC1_CD */
        {-1},
};