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

MSPM0G3507: empty_mspm0g3507: Unable to load 64-pin sysconfig

David Linkh
Intellectual 885 points
Part Number: MSPM0G3507
Other Parts Discussed in Thread: , SYSCONFIG

Tool/software:

Hi MSP team,

I have a customer who is running into issues using SysConfig. They are using a 64-pin MSPM0G3507 Launchpad and are unable to open the GPIO to configure Pin1/PB13. When I opened the empty project file to see what is going on, I am greeted by the following errors, regardless if its the LP-MSPM0G3507 empty example or CUSTOM board MSPM0G3407 empty example:

I also noticed someone had a similar issue in this post, but they never followed-up once we responded. I am on the latest CCS and MSPM0 SDK, is there any reason obvious reasons as to why this is occurring?

If you need any additional information, please let me know.

Sincerely,

David

  • 0
    TI__Mastermind 18387 points

    I still can not find how to reproduce this issue.

    Maybe try to re-open the CCS/syscfg, or re-install the CCS/syscfg will fix this issue.

    Can you open other peripherals? such as UART/RTC, can you see this issue agagin?

    I will loop this ticked to CCS forum, get some comments from them.

  • 0
    TI__Guru**** 463871 points

    Hi David, what versions of CCS, SysConfig, and MSPM0 SDK are you using?

    Thanks

    ki

  • 0 in reply to Ki
    TI__Intellectual 885 points

    Hi Ki and Helic,

    Helic Chi said:
    Can you open other peripherals? such as UART/RTC, can you see this issue agagin?

    I am able to click on all other peripherals, its only happening with the GPIO tab. I tried restarting my PC and CCS/Sysconfig, but am still getting the errors. 

    Ki said:
    what versions of CCS, SysConfig, and MSPM0 SDK are you using?

    I am using the following versions

    Sysconfig: 1.22.0, 1.23.0, 1.23.1

    MSPM0 SDK: 2.02.00.05

    MSPM0 Feature Support: 1.13.00.02

    CCS: 20.1.1.8__1.7.1

    Default VS Code API: 1.92.2

    From what it looks like, the SDK required Sysconfig 1.21 to be installed, and this was causing the issue with the GPIO. I updated my MSPM0 SDK to 2.04.00.06 and this appeared to fix the problem. I am going to see with the customer what versions they are using as well. To my understanding, they were using the latest version of the SDK, but maybe not the latest Sysconfig tool. If I run into anymore issues, I'll create a separate thread.

    Sincerely,

    David