• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 87 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCSTUDIO: CCSv20 - Manage the project's target-configuration automatically

Scott Specker
Intellectual 310 points
Part Number: CCSTUDIO

Tool/software:

With CCSv18, CCS will automatically create the .ccxml file when I check the box for "Manage the project's target-configuration automatically" in a project's properties dialog. This happens right after saving & closing the project properties dialog.

While the same "checkbox" is there for this option under CCSv20.2.0, it doesn't create the .ccxml file for you upon saving and closing the project properties.

Oddly enough, if I close CCSv20 and then reopen it, the .ccxml file does appear to have been created.

This is the expected behavior for the new version of CCS? Or should the target config file be build right away?

Thanks,
Scott

  • 0
    TI__Guru**** 464411 points
    Scott Specker said:
    While the same "checkbox" is there for this option under CCSv20.2.0, it doesn't create the .ccxml file for you upon saving and closing the project properties.

    It should (re)generate the ccxml file. I tried this with my CCS 20.2.0 installation and this seems to work in my environment. It should generate a "targetConfigs" folder with the ccxml file in it (just like CCS Eclipse)/

    Can you provide more details on your scenario? Is there no ccxml file in the project and then when you select the checkbox with a valid connection type, no file is generated?

    Also, please note that due to the local holiday today responses may be delayed.

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 310 points

    I tested this - as I have done with Eclipse - by deleting the ccxml file from a project. (Or alternatively, deleting the whole targetConfigs folder.) 

    Then opening up the project properties and checking the checkbox to "handle it for me" while selecting a valid connection type.

    I ran across this in the old days because we had students not know what the ccxml file was for so they would just delete it. Doh! 

    In the v20.2.0, it obviously works, but for some reason, it's just hasn't populated it until I close and restart CCS. I tried this on both the CC1352 and MSPM0 targets.

  • +1 in reply to Scott Specker
    TI__Guru**** 464411 points

    I have been playing around with this a bit and I believe I found the root issue. It looks like when enabling that option, the setting will only get saved if you explicitly change the connection type. If you just use whatever default appears when you enable the check-box and then save the properties and exit, that setting is not preserved. If you check the properties again, it will still be un-checked. At least this is the behavior I noticed. But if the check-box is enabled and then the connection type is explicitly changed and then the settings saved, the setting is preserved and I see the ccxml get generated. Then I can go back and change it back to the original connection type and save that.

    I filed a bug for this. Tracking link: https://sir.ext.ti.com/jira/browse/EXT_EP-12801

    Thanks

    ki 

  • 0 in reply to Ki
    Intellectual 310 points

    Yep, that seems to work. That's a bit of an odd bug. Thanks for figuring it out!