CCSTUDIO: How to update SYSCFG and SDK in CCS20.0.0.12

Tool/software:

Hey there,

when merging my and my colleagues project branch I found out in diff view that there is a new sysconfig version

 * @versions {"tool":"1.23.0+4000"}  -- HIS NEW VERSION
 * @versions {"tool":"1.21.0+3721"}  -- MY OLD VERSION

So I downloaded the newest version of sysconfig and installed it.

Then, I struggled a bit, how to activate it in CSS20.

But I found out that I have to Refresh the "discovered Products" in the "Code Composer Studio Settings" - General - Products.

And then I have to got to "Project Properties" - General - Dependencies - Product Dependencies and edit the sysconfig version.

At the same point, I also directly updated the SDK used to the latest release.

Then I closed CSS20, rebooted my computer, restarted CCS20 and reopened the sysconfig tab/file.

After rebuilding my project the sysconfig file still stays the same..

/**
 * 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-48(PT)" --product "mspm0_sdk@2.02.00.05"
 * @v2CliArgs --device "MSPM0G3507" --package "LQFP-48(PT)" --product "mspm0_sdk@2.02.00.05"
 * @versions {"tool":"1.21.0+3721"}
 */

It looks to me as if CCS20 still uses the old Sysconfig and the old SDK.

Even though the build output window says:

[10]Building file: "../main_mspm0g3507.syscfg"
[11]Invoking: SysConfig
[12]"C:/ti/sysconfig_1.23.0/sysconfig_cli.bat" --script "C:/Users/matthias.hein/Documents/GIT/WiPro3_facelift/wiproIII_facelift.sw.pcb010206/wiproiii_facelift/main_mspm0g3507.syscfg" -o "syscfg" -s "C:/ti/mspm0_sdk_2_04_00_06/.metadata/product.json" --compiler ticlang
[13]Running script...
[14]Validatin

This actually indicates that the latest sysconfig is being used.

The .cproject-file changed from

                                <listOptionValue value="PRODUCTS=MSPM0-SDK:2.2.0.05;sysconfig:1.21.0;"/>

 to

                                <listOptionValue value="PRODUCTS=MSPM0-SDK:2.4.0.06;sysconfig:1.23.0;"/>

So it looks like everything is right there again.

But my impression from the diff view of my GIT is also that the sysconfig file is reordered during compilation as it was with the old sysconfig version and not as it is with the new sysconfig version that my work colleague uses.

Please help me and give me clarity. So, with this uncertainty, it's somehow no fun to work with...

Thanks for your help in advance!

Matze