• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 653 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.

MSPM0-SDK: SDK sysconfig files don't specify SDK version

Munan Xu
Expert 4920 points
Part Number: MSPM0-SDK
Other Parts Discussed in Thread: SYSCONFIG

Hello,

For some reason standalone sysconfig will not open .sysconfig files without an SDK version in the options header.

I have tried multiple sysconfig files that will give me some very cryptic javascript error:

And when I compare to a sysconfig file that will open, the only difference is adding the "--product "mspm0_sdk@1.10.00.05"

designator and then the files will open fine. 

Is this a sysconfig bug or is do we need to just start including the product version in the sdk sysconfig files? Or can we just have sysconfig default to opening with the latest SDK?

Munan

  • 0
    TI__Guru 56685 points

    Munan,

    Let me get back to you on this, by Thursday. 

  • 0 in reply to Jace H
    TI__Guru 56685 points

    Munan,

    This is currently not a bug, but how the current implementation is designed. The current intended flow is for a user to go through the IDE for examples. 

    We can confirm that the standalone Sysconfig tool does need a "--product" in order to read a Sysconfig file. Basically, the standalone tool needs to know what version of the SDK the Sysconfig file is from. So adding this to the sysconfig file is a valid workaround. 

    There are some backend compatibility reasons for not having this designator in the sysconfig files found within examples in the SDK. That being said, we do see the benefits for having seamless compatibility, and it has been added to our backlog to address at some point in the future.