• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 413 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM5716: Pinmux tool issue

Ondrej Kosta
Prodigy 20 points
Part Number: AM5716


Hi TI folks,

I would like to report an issue of the PinMux tool which caused me troubles during porting our application from the EVM to our custom board. I prepared PinMux tailored for our board, however the tool did not generated the output file "boardPadDelayInit.c" correctly for McASP AXR signals. The configuration table record is generated only for one AXR pin in "boardPadDelayInit.c". It caused me troubles because the McASP is quite complex interface and I did not suspect any issues caused by PinMux tool. The issue is not obvious from the GUI. The only clue is that the pin is checked and configured but no signal name is present for AXR1, see attached figure.

Best Regards

Ondrej

  • 0
    TI__Guru**** 393215 points
    The PMT team have been notified. They will respond here.
  • 0
    TI__Genius 13770 points
    Subtle, but you haven't configured the "Any of the following pins" menu. Right now I see you've set the GUI to use just one of the selected, and it exports the first one. Can you set it to 2 and try again?

    thanks,
    Alex
  • 0 in reply to Alex Bashkov
    Prodigy 20 points
    Hi Alex,

    yep, it works! :) However, frankly speaking, it is not very obvious at the first glance. It would be better if the PinMux tool didn't allow you to check any other signal when "Any of the following pins" is not set correctly.

    Anyway, thank you for your help!
    Ondrej
  • 0 in reply to Ondrej Kosta
    TI__Genius 13770 points

    Hi Ondrej,

    Thanks for verifying this thread and sure, I understand your point. However, that entire menu is based on and has something to do with the McASP module functionality itself. Apparently, on the actual board the configuration is dynamic, so you don't know the particular set of signals, thus the menu that explicitly states how many AXR signals are expected but not which one of the configured ones. On the other hand, if you configure more expected signals than the actual checked, the GUI shows an error. I just wanted to clarify that.

    thanks again,
    Alex