I have this issue and it seems to be the same in the latest desktop and cloud based version of the Pinmux tool/
I'm creating a Pinmux configuration for the AM437x, and I have started locking various signals to specific balls on the package to insure that they don't move around after I have created my schematic. The problem I am encountering is that the "Peripheral" in the "Use Peripheral" field is acting very oddly for many of the peripherals in my configuration if I lock them down and then come back later during my final checks.
For example, I have DCAN signals:
rx(dcan0_rx) locked to J24
tx(dcan0_tx) locked to K25
I set "Use Peripheral" to "DCAN0" and a lock appears next to this as well.
Next, I want to assign DCAN1 to some balls and so I add a second DCAN and lock it to DCAN1 in "use peripheral", and then I set:
rx(dcan1_rx) locked to J25
tx(dcan1_tx) locked to L25
That's all good, correct?
Not so much, as if I revisit the DCAN0 peripheral setup, the pins are all locked as I did before, but the "Use Peripheral" field which I had locked to "DCAN0" now says "DCAN1". I see similar issues with the ADC and the UART and eCAP peripherals.
So, in my example above, the signal names still imply that DCAN0 is being used, but the "Use Peripheral" field seems to say otherwise.
Is this a bug or a feature? It has me concerned because the pins seem to be correctly assigned like I wanted, but the peripheral field displaying wrong has me worried that the generated files for Linux may be created with errors or be unworkable.
Does anyone have any suggestions on how to correct this?
Thanks.
