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: LP-MSPM0G3507

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

Hi, My problem is that when I open an already existing syscfg file(for example," gpio_toggle_output.syscfg " in mspm SDK (version is  1-30_00_03))with sysconfig(version 1.19.0 ) software, I get an error as follows:

Error running C:\ti\mspm0_sdk_1_30_00_03\examples\nortos\LP_MSPM0G3507\driverlib\gpio_toggle_output\gpio_toggle_output.syscfg

Error: Exception occurred calling scripting.addModule(): No such resource: /ti/driverlib/GPIO.syscfg.js
Hide Details...

Paths searched: /ti/driverlib/GPIO.syscfg.js /ti/driverlib/.meta/GPIO.syscfg.js /ti/.meta/driverlib/GPIO.syscfg.js /.meta/ti/driverlib/GPIO.syscfg.js /ti/driverlib/GPIO.syscfg.js /ti/driverlib/.meta/GPIO.syscfg.js /ti/.meta/driverlib/GPIO.syscfg.js /.meta/ti/driverlib/GPIO.syscfg.js at Object.addModule (webpack:///src/pinmux/services/scripting/scriptingGuard.ts:46:10) at scriptFunc (C:\ti\mspm0_sdk_1_30_00_03\examples\nortos\LP_MSPM0G3507\driverlib\gpio_toggle_output\gpio_toggle_output.syscfg:11:26) at cb (webpack:///src/pinmux/services/scripting/runScript.ts:112:7) at withDeprecatedAccess (webpack:///src/pinmux/services/deprecatedAccessGuard.ts:14:10) at runAsUserScript (webpack:///src/pinmux/services/scripting/scriptingGuard.ts:61:3) at iteratee (webpack:///src/pinmux/services/scripting/runScript.ts:110:5) at baseEach (webpack:///node_modules/lodash/lodash.js:530:11) at Function.each (webpack:///node_modules/lodash/lodash.js:9409:52) at iteratee (webpack:///src/pinmux/services/scripting/runScript.ts:108:6) at st (webpack:///node_modules/lodash/lodash.js:530:11)

Would you like to re-try in compatibility mode?

How can i solve it ? Thanks.

  • Hi Guohua,

    #1 you can open the syscfg in the CCS12.6.

    #2 due to the header of the SDK syscfg is different from standalone sysconfig. You can save an empty file by sysconfig 1.19, and then open the empty syscfg file, copy the header to replace the one of SDK, and then it can be opened by sysconfig 1.19.

    B.R.

    Sal