• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 361 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

LP-MSPM0G3507: Error switching to new SDK and SysConfig 1.18

Keith Barkley
Guru 41995 points
Part Number: LP-MSPM0G3507
Other Parts Discussed in Thread: SYSCONFIG

I changed the dependencies to the latest SDK and sysconfig:

And got the following error:

  • +1
    TI__Guru 56685 points

    Hey Keith,

    Thank you for reporting this. I've conferred with internal MSPM0SDK team and they were able to spot the issue pretty quickly, and it seems to be related to the SYSCTL module specifically in Sysconfig. As a work around, you can utilize the ClockTree tool to setup your clocks and it should generate the correct pin defines. This is being filed internally to be fixed. 

    As a reminder, the ClockTree tool can be found in Sysconfig as a left side tab. MAke sure the "Use Clock Tree" button is selected within SYSCTL for the Clock Tree to override SYSCTL settings. You may need to take the extra step in disballing any Xtals in the SYSCTL portion of Sysconfig as it can sometimes conflict with ClockTree trying to set those pins. 

  • 0 in reply to Jace H
    Guru 41995 points

    Thanks, I have tried using the clock tree, but found the settings in the regular syscntrl to be easier to understand. I guess I will have to dive in and figure it out...