Pin Mux Utility support for AM3517

Hi Mike,

thanks for your support. Now I've found the files. I've just searched at the wrong place. It's good news to me that the new version of the pin mux utility will be available soon.

Regards,

Oli

The Pin Mux Utility for ARM MPU Microprocessors v1.0.1.0 is now available via the AM3715 and AM3703 product pages.  Go to "Tools and Software", then "PinMux Utility for Sitara Devices", then "Get Software".   You should see one file to download named "Pin_Mux_Utility_v1_00_01_00".  This supports AM37xx, AM35xx and OMAP35xx devices.

Best Regards,

Mike Tadyshak

ARM MPU SW Applications Engr.

NOTE: Here is a special case regarding USB0 / UART3 muxing on AM3517 & AM3505:

The F24 and F25 balls are an unusual case.  They have USB0 and UART3 signals muxed as shown in the Mux Table, but there

is no pad configuration register defined for them - so they do not show up in the tool.  Pin Mux Utility generates U-BOOT source code

for programming the pad configuration registers.

This mux control is programmed in a separate register:

Register Name: CONTROL_DEVCONF2 

Physical Addr: 0x4800 2580

Access: R/W

Bit 23: USBPHY_GPIO_MODE

            Selects the GPIO mode of the USB PHY

                        0 = USB PHY normal mode of operation

                        1 = UART3 signals on usb0_dm and usb0_dp balls

                                    F24 = uart3_rx_irrx

                                    F25 = uart3_tx_irtx

This bit defaults to 0, so if not programmed F24 and F25 will be defined as usb0_dm and usb0_dp.

Michael:

Are there any other  special cases using the AM3517 pin mux utility ?.  My customer wants to make sure he is not missing any conflicts.

Thanks,

Pradhyum

Pradhyun:

The tool generates header files that configure all pad configuration registers that are defined in

the TRM and are programmed in the UBOOT source file am3517evm.c. 

With regard to pad configuration registers, I consider four cases:

1) Pad configuration register exists and mux mode field is programmable (normal case)

2) Pad configuration register exists but mux mode field is NOT programmable

         For example: most of the SDRC, GPMC and JTAG signals

         These balls are shown in the tool.  If double-clicked on they cannot be deselected.

         Other pad configuration bits for these balls can be configured using the tool.

3) Pad configuration register does NOT exist.  Only Mux Mode 0 signal is defined.

        For example, sys_xtalin, tv_out1.

        There is no mux mode field or other pad configuration bits to program so these balls are not shown in tool.

 4) Pad configuration register does NOT exist.   More than one mux mode defined.

        For example, usb0_dp and usb0_dm as described above.   This is the only case of this kind.

       This selection is made by programming a register within the peripheral module.  The pin mux tool and UBOOT header files do not include this.

       These are left at default USB0 selection by UBOOT.

NOTE:

There are some restrictions to which mux modes can be used when signals within a peripheral interface are muxed to multiple balls.

For example, UART2 signals are muxed as Mux Mode 0 and as Mux Mode 1.  You cannot use some signals from Mux Mode 0 and some signals

from Mux Mode 1 for the same peripheral interface or timing issues could occur.   

Rules Violation status is shown in the legend to flag this condition, but is not yet implemented in the software.

Michael T

hello 

I am using AM3517 and I am configuring pins using Pinmux Utility but I don't see all the pins in software like SDRC_A0(A11) to SDRC_A14(D8),SDRC_BA0(A12),SDRC_BA1(C13),SDRC_BA2(D13).

Also pin count is not complete according ZCN package which has  491 but in software its showing   353

The Pin Mux Utility only shows device balls that are multiplexed.

regards,

Michael T

I see that UART3 also appears on pins P1 and P2. Does USB0 configuration affect these also in the same way as F24 and F25.

Thanks for your help

Glenn