• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 30 subscribers
  • Views 241 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.

AM2634: GPIO peripheral selection in Sysconfig

Jeeuk Chang
Prodigy 240 points
Part Number: AM2634
Other Parts Discussed in Thread: SYSCONFIG

Code Composer Studio version : 12.6.0.00008

SysConfig version : 1.19.0

MCU+ SDK for AM263x version : 9.1.0.41

At GPIO settings of Sysconfig, the items of "GPIO Peripheral" are just two items.

(Actually just one - GPIO0)

But, I can select the GPIO pins that I wanted to use at "GPIO Pin" setting.

This Sysconfig setting makes some confusions at "ti_pinmux_config.c" which is an auto-generated file.

(Annotations of GPIO pins are "GPIO0")

Please check this result.

  • 0
    TI__Guru*** 135355 points

    Hello Jeeuk,

    I'm not following the feedback here entirely. The naming matches the GPIO bank you've selected?

    Best Regards,

    Ralph Jacobi

  • 0 in reply to Ralph Jacobi
    Prodigy 240 points

    Hi. Sorry for my late response.

    In "ti_pinmux_config.c" code, only the comments of "GPIO0" are wrong.

    I configured GPIO71, GPIO47 and GPIO48.

    In my captures, I can not change the items of GPIO Peripheral.

    They are always "GPIO0".

  • 0 in reply to Jeeuk Chang
    TI__Guru*** 135355 points

    Hello Jeeuk,

    The GPIO0 field value is populated based on the "GPIO Peripheral" selected, not the "GPIO PIN" selected.

    Right below the GPIO0 comment are comments for "GPIO PIN" -> "Device PinMux Mapping" which have your GPIO71, GPIO47 and GPIO48 values listed.

    Best Regards,

    Ralph Jacobi

  • 0 in reply to Jeeuk Chang
    TI__Guru*** 135355 points

    Hello Jeeuk,

    I see you rejected my last answer but unfortunately there is nothing else I can do here - I understand you don't agree with the chosen format for generation of those comments, but it is consistent with our approach for SysConfig generation where the Peripheral selected is the initial header followed by specific pin details.

    I will be closing this post on my end unless you have further feedback to provide.

    Best Regards,

    Ralph Jacobi

  • 0 in reply to Ralph Jacobi
    Prodigy 240 points

    Hi.

    If the selection of "GPIO Peripheral" is meaningless, it would be better to delete the option. And I suggest SysConfig program make comments of "GPIOn" or "GPIOx" instead of "GPIO0" at "ti_pinmux_config.c"

    I also know this issue is not important and bearable. But It would be better to edit it a little more clearly.

    Thank you for your kind response.

  • +1 in reply to Jeeuk Chang
    TI__Guru*** 135355 points

    Hello Jeeuk,

    The reason we can't delete the option is that the logic has to be applied universally, so for while GPIO it is a meaningless output, it is used across a lot of other peripherals. The real core issue is that the GPIO0 is a poor way to reflect the GPIO peripheral as a whole and we are looking into improving that piece and if there is a better way aligned then the generated output will make more sense.

    Best Regards,

    Ralph Jacobi