MSPM0G3507: Standalone Sysconfig error "Invalid argument '--product': No product with name "mspm0_sdk" and version "2.05.01.01" found" (2.05.01.01 can't be downloaded)

Ken Ayre

Part Number: MSPM0G3507
Other Parts Discussed in Thread: SYSCONFIG, , CCSTUDIO

Tool/software:

Greetings,

When I try to open a sysconfig file from stand-alone version, i get the message "Invalid argument '--product': No product with name "mspm0_sdk" and version "2.05.01.01" found". We know the file is good, since colleague/collaborator is able to open it.

- This is a new CCS install on a new laptop, and git repo's were simply duplicated into the same files structure.

- I tried to find SDK version 2.05.01.01. (I installed SDKs 2.05.01.00 and 2.06.00.05 with the fresh install.)

- I tried to simply edit the header to change the versioning

* 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" --part "Default" --package "LQFP-64(PM)" --product "mspm0_sdk@2.05.01.01"
* @v2CliArgs --device "MSPM0G3507" --package "LQFP-64(PM)" --product "mspm0_sdk@2.05.01.01"
* @versions {"tool":"1.25.0+4268"}

I see there a few similar issues in this forum, but none seemed to exactly match our scenario. Apologies if I've overlooked the solution.

Thank you.

Ken Ayre

4 days ago

0 Ken Ayre 4 days ago

Prodigy 50 points

Clue? In another article (in simplelink thread), it was suggested to comment out from c.project

I did this because the linker was reporting errors about the project may not build correctly. The sysconfig tool is not in our build path. We do make a link to stable ti_msp_dl_config.* projects in the build.

0 Pengfei Xie 3 days ago in reply to Ken Ayre

TI__Genius 9055 points

Hi Ken,

Sorry I'm out of office these two days. I will check this after I come back.

0 Ken Ayre 3 days ago in reply to Pengfei Xie

Prodigy 50 points

Greetings, and no worries.

I just worked through and resolved this issue. It really had very little to do with CCS directly.

These are things I discovered that "went bad" during install and configurations.

- Our IT department has HOME set to a network location. (ugh)

-Two other "APPS" had different ideas of where HOME was supposed to be, one of which re-mapped HOME to their project data folder.

- GIT was unhappy because it didn't have a solid HOME, and created a default configuration with bad info.

- "Some process" or "application" relocated project files (.thiea) to one of the other HOME folders, which was remapped (unknown to TI Tools).

General resolution (aside from blaming IT):

1. Resolved and/or reset HOME as c:\Users\Home and corrected the paths for where another app put its data was stored.

1a. Not directly related to this issue but I put a symbolic link for .gitconfig in that nasty network home just in case.

2. moved .thiea project files back to where they were before they got shuffled around. One larger multiproject workspace needed to be rebuilt.

3. after correcting paths and file locations, I had to play hide and seek for where the ssh tokens were for git, and move them to the "real HOME"

After completing the above corrections and adjustments the sysconfig tool was able to open all of my "*.syscfg" files.

Arm-based microcontrollers

Arm-based microcontrollers forum

MSPM0G3507: Standalone Sysconfig error "Invalid argument '--product': No product with name "mspm0_sdk" and version "2.05.01.01" found" (2.05.01.01 can't be downloaded)