Am335x Pinmux problems

Hi,

b.buettner said:

mmc2_dat7_mux0/rmii2_crs_dv_mux2 (U16) shall be used as mmc2_dat7. This was asked before in this forum and the violation can be ignored.

This violation occurs because the same pin is selected both in GEMAC CPSW and MMC2 I/O set. If you intend to use it as MMC2 function you should remove it from the GEMAC CPSW I/O set.

b.buettner said:

I must have two CS with SPI1. My setting produces a violation with spi1_cs1_mux2 (A15). Is this a suggestion/warning not to use the setting or does it really not work?

Do you need RTS/CTS on UART0? If this is used as the Linux debug UART only TXD/RXD are used. In this case you can use I/O set #14 for SPI1.

If I remove the selection from GEMAC CPSW it will be removed from the MMC2 I/O set too and the Linux sources show it as GPIO pin.
I can use I/O set #14 and I think I have to. But my question was, what happens if I try to set spi1_cs1_mux2 on A15?

What is about my remarks for utility 3

Ah yes, I see what you mean about MMC2. I think you can safely ignore this error, provided you take care of the additional pinmuxing needed (Note 10 after Table 4-1 in the AM335X Datasheet Rev. G).

About spi1_cs1_mux2 on ball A15, obviously an I/O violation occurs. This happens when the selected pins have not been timing closed for the chosen function. This must be avoided as proper functionality cannot be guaranteed for such a combination of pins.

About Pinmux Tool v3, it works for the AM437X processor, no support for AM335X is available there. This tool is supported on the Code Composer forum, you can ask there for more details.

Thank you, I understand now. My desired setting for spi1 may work or may not. That means I cannot use it, ok.
With Pinmux Tool V3 I disagree with you. You can select AM335x as device, but there is no selection for Rev.1/2. And there is no selection for mmc2 to use pin U16 and you cannot import data from Tool V2.