MSPM0G3519: CCS 20.x: base sysconfig for all MSPM0Gx?

AnBer

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

Team,
Customer would like to have a common sysconfig base for MSPM0Gx (like G350x/G351x) and then add the device specific features to it depending on the project the exact device (like G3519, G3507) will be used.
-What is the best starting point in order to achieve this?
Apparently all the empty projects like (https://dev.ti.com/tirex/explore/node?isTheia=false&node=A__AOGua-kqg9ZhIuWFR5cxrA__MSPM0-SDK__a3PaaoK__LATEST ) are target specific.
Is there a way to create a general MSPM0Gx platform sysconfig? How?

We have found out so far that you can debug different syscfg under ‘Project -> Build configuration’. However, we have not been able to configure this for different targets there.
Unfortunately, setting the respective M0 as “active” in the ‘targetconfigs’ folder does not help much either.
It seems that when switching between active targets, the .ccsproject and .cproject files still contain remnants of the last (or first) selected target. This means that you always have to go through these files manually and make changes there...
Surely there must be a more elegant solution? (with the Eclipse-based CCS, it was more reliable)

Thanks in advance,

Anthony

7 months ago

0 Zoey Wei 7 months ago

TI__Genius 15051 points

Hi AnBer ,

From my experience, I will add couples sysconfig in the same project like this. For example, if customer would like to use L1306, then exclude G3507 sysconfig file from build. This is the most convenience way I can think of.

Regards,

Zoey

0 Benjamin Schütte 7 months ago

Prodigy 80 points

Hi Zoey Wei.

Could you please open the "targetConfigs" folder and post another screenshot?

And is it possible that you're using the "old" CodeComposerStudio, and not the new version 20?

0 Zoey Wei 7 months ago in reply to Benjamin Schütte

TI__Genius 15051 points

Hi,

No CCS20 is also support have multiply sysconfig file in the same project, but be sure, you need to exclude other sysocnfig and only reserve on to buil

0 Benjamin Schütte 7 months ago in reply to Zoey Wei

Prodigy 80 points

That's exactly what we're doing. You can see it in the image.

The correct target is selected in "targetConfigs".

However, the wrong one (MSPM0G3507) is being used under project->properties, and it can't be changed there.

The correct one (MSPM03519) is configured in main_ucm2.syscfg.

0 Zoey Wei 7 months ago in reply to Benjamin Schütte

TI__Genius 15051 points

Hi,

You can ignore the project->properties info, and check if the current project can download into G3519 EVM.

0 Benjamin Schütte 7 months ago in reply to Zoey Wei

Prodigy 80 points

Hi. 
Okay, thank you very much! 
We'll try this out with the different projects and see what happens. 

So far, we've noticed that when we check the box for "Manage the project's target configuration automatically" in the properties, some strange things happen. 
We'll just ignore properties for now and test our projects. 

Thanks again!

Arm-based microcontrollers

Arm-based microcontrollers forum

MSPM0G3519: CCS 20.x: base sysconfig for all MSPM0Gx?