• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 83 subscribers
  • Views 181 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.

TMS320F28P550SJ: Syscfg "lock" feature confusion

Hang Yang
Expert 3676 points

Part Number: TMS320F28P550SJ
Other Parts Discussed in Thread: SYSCONFIG

Hi Experts,

I am using syscfg to configure the pinmux for MCAN, there is a lock icon in the pinmux, but it's function is confusing.

image.png

When it's "locked", I can still change the settings. When unlocks, the value returns to "Any", as it says in the description. 

Looks like this is a "reset" instead of "lock"

Is it a bug or feature? If it's feature what's the point of this function?

Regards,

Hang

  • 0
    TI__Genius 10101 points

    Hi Hang,

    Let me loop pinmux experts on this.

    Thanks

    Aswin

  • +1 in reply to Aswin P
    TI__Mastermind 20380 points

    Hello,

    The function of the Lock feature is to lock the given pinmux configuration for a pin or peripheral, such that if another peripheral (or even another MCAN instance) is added, the SysConfig solver doesn't automatically go ahead and change the pin configuration to avoid pinmux conflicts. When "Any" is selected, this means that there are no hard requirements for peripheral pinmuxing i.e. the solver can change the pin configuration as needed.

    When "Unlock" is selected, this returns the pin/peripheral selection to "Any". This allows the solver in SysConfig to find new pinmux combinations that fit the peripheral requirements as configured by the user. 

    Best,
    Matt

  • 0 in reply to Matt Kukucka
    TI__Expert 3676 points

    Hi Matt,

    Understood.

    Though I'd like to suggest that not returning the "any" when "unlock" is selected. Customer may mistaken the lock as "locking and setup so user won't chang it accidently" and plays with the lock icon, which is inevitable, but, we can avoid this behavior destroying their existing configuration.