CCSTUDIO-THEIA: Project properties cannot be modified

Part Number: CCSTUDIO-THEIA
Other Parts Discussed in Thread: C2000WARE

Hello Support Team,

It seems that under CCS 21, an invalid path in templateProperties.origin of .ccsproject causes the Project Properties window to be unable to save any changes. The button "Save and Close" does nothing on click (the window stays opened), even if no changes were made. No error message is displayed. The project builds correctly, however.

Fixing the origin path solved the issue. The path was invalid because the project was imported from another machine with a bit earlier version of CCS and C2000Ware installed; the origin pointed to the C2000Ware directory because the project was a reworked TI example project.

Best regards,

Michal

  • Hello Michal,

    I assume that you are referring to these two fields:

        <templateProperties value="id=led_ex1_blinky.projectspec.led_ex1_blinky"/>
        <origin value="C:\ti\c2000\C2000Ware_26_01_00_00\device_support\f28p55x\examples\led\CCS\led_ex1_blinky.projectspec"/>

    I tried to reproduce this issue with my CCS 21 installation. I manually changed the origin path to an invalid path. However, the project not only imports fine, but I can modify project properties without issue.

    Is there any specific project properties that you tried to change but it failed?

    And simply manually modifying the origin path to a valid path resolved the issue while the project was still in the workspace?

    Thanks

    ki

  • Actually I wanted to change compiler mode to C99, but I realized that even when I did not change any property, "Save and Close" was non-functional.

    And yes, fixing the path resolved the problem.

    The wrong path (which was valid on the source machine) started with "C:\ti\C2000Ware_26_00_00_00\...", the right path is "C:\ti\c2000\C2000Ware_26_01_00_00\...".

    No idea if it matters at all, but I did not import the project with copying files into the workspace, the files were left in their original folder on different disk.

  • Thank you for the added details. However I am still unable to reproduce despite attempts to mimic your system. I will discuss with engineering to see if they have any explanation.

    Thanks

    ki

  • I discussed with engineering and we are perplexed on how this issue is occurring. They mentioned that the origin path in the .ccsproject file is updated once on import if copied to the workspace and then never referenced again. If, after that, the path for it is no longer valid, it should not impact anything.