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

Original question:

MSPM0C1103: Standalone Sysconfig can't open examples from MSPM0 SDK

MSPM0-SDK: Working with MSPM0-SDK and IAR Embedded workbench.

A B
Prodigy 40 points

Part Number: MSPM0-SDK
Other Parts Discussed in Thread: SYSCONFIG, MSPM0G3507

Hi, 

I'm currently evaulating IAR-Embedded workbench for ARM. I'm trying to set it up with MSPM0-SDK (mspm0_sdk_2_09_00_01), I followed the following guides - MSPM0 SDK QuickStart Guide for IAR — MSPM0 SDK Quick Start Guides 2.09.00.01 documentation  & IAR Embedded Workbench IDE Version 9.70.2+ for MSPM0 MCUs — IAR Embedded Workbench IDE for MSPM0 MCUs Documentation 2.09.00.01 documentation to set things up. 

Using a non-sysconfig project was stragiht forward but when I import a sysconfig project into my workspace I'm not able to view the sysconfig tool directly. I used the sysconfig application to open my sysconfig project but, it throws up the following error :

Would you like to re-try in compatibility mode?

Error: Exception occurred calling scripting.addModule(): No such resource: /ti/driverlib/SYSCTL.syscfg.js Paths searched: /ti/driverlib/.meta/SYSCTL.syscfg.js /ti/.meta/driverlib/SYSCTL.syscfg.js /.meta/ti/driverlib/SYSCTL.syscfg.js /ti/driverlib/SYSCTL.syscfg.js /ti/driverlib/.meta/SYSCTL.syscfg.js /ti/.meta/driverlib/SYSCTL.syscfg.js /.meta/ti/driverlib/SYSCTL.syscfg.js /ti/driverlib/SYSCTL.syscfg.js

I have also retried it in comptaiblity mode but it doesn't open. 

I came across this MSPM0C1103: Standalone Sysconfig can't open examples from MSPM0 SDK - Arm-based microcontrollers forum - Arm-based microcontrollers - TI E2E support forums in E2E but I'm not sure which .js file to edit, don't want to edit the wrong one and break anything. 

Thank you. 

  • 0
    Prodigy 40 points

    my .syscfg file had this initially

    /** * These arguments were used when this file was generated. They will be automatically applied on subsequent loads * via the GUI or CLI. Run CLI with '--help' for additional information on how to override these arguments. */

    //@cliArgs --device "MSPM0G350X" --package "LQFP-64(PM)" --part "Default"

    //@v2CliArgs --device "MSPM0G3507" --package "LQFP-64(PM)"

    // @cliArgs --board /ti/boards/LP_MSPM0G3507 --rtos nortos

    I replaced it with the following

    /**
    * These arguments were used when this file was generated. They will be automatically applied on subsequent loads
    * via the GUI or CLI. Run CLI with '--help' for additional information on how to override these arguments.
    * @cliArgs --board "/ti/boards/LP_MSPM0G3507" --product "mspm0_sdk@2.09.00.01"
    * @v2CliArgs --board "/ti/boards/LP_MSPMG03507" --product "mspm0_sdk@2.09.00.01"
    * @versions {"tool":"1.26.2+4477"}
    */

    now when I open, I get the following

    Invalid argument '--product': No product with name "mspm0_sdk" and version "2.09.00.01" found

  • 0 in reply to A B
    Prodigy 40 points

    Okay, I just noticed an error in the v2CliArgs line. Changing it to LP_MSPM0G3507 helped, and although the installed folder shows that the SDK version is 2.09.00.01, the product.json file shows the version number as 2.09.00.02.

    /**
    * These arguments were used when this file was generated. They will be automatically applied on subsequent loads
    * via the GUI or CLI. Run CLI with '--help' for additional information on how to override these arguments.
    * @cliArgs --board "/ti/boards/LP_MSPM0G3507" --product "mspm0_sdk@2.09.00.02"
    * @v2CliArgs --board "/ti/boards/LP_MSPM0G3507" --product "mspm0_sdk@2.09.00.02"
    * @versions {"tool":"1.26.2+4477"}
    */

    This works.