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.

CCSv5: Sticky .ccxml Target Configuration file

Other Parts Discussed in Thread: TMS320DM6437

Hi,

I recently created a new project with the latest CCSv5 version 5.1.1.00031 and I am having a problem I never had in the past.

I am usually having custom Target Configuration files in a sub-directory that I manually specify which one is active. Since the creation of my new project under the latest CCSv5 version, there is a "TMS320DM6437.ccxml" file automatically created and set to "Active" each time I close and re-open my project. Even if I delete the file, it just gets back each time I re-open the project.

Is this a bug with the latest CCSv5 version, or is there an option somewhere that is causing that?

Thanks

Franck

  • Hi Franck,

    can you describe a bit further details on your setup?  For C6000 devices, a ccxml file is not automatically generated unless you have something doing this yourself in the background.  I have tried 3 or 4 projects and not a single one (CCS v5.1.1) was created with a ccxml.

    Did you modify or set any options in your project regarding the launches?  In Window->Preferences->Debug .. there are a few options in this section ... for example ..."Always launch last configuration".  Do you have something like this set?  Under Window->PReferences->Code COmposer Studio->Debug .. in these settings you can modify the default shared ccxml directory.  Did you do anything special or different here?

    Is this happening with any new example or project you try to create?  Have you tried a fresh workspace?

    Best Regards,
    Lisa

  • Hi Lisa,

    I investigated the points you mentioned, and could get the way to recreate that behavior.

    Here is exactly the sequence that leads to the automatic ccxml file creation:

    1. File -> New -> CCS Project
    2. Set Project name
    3. Select TMS320DM6437 device variant
    4. Select Spectrum Digital XDS510USB Emulator Connection
    5. Select Empty Project
    6. Finish

    In that case, the ccxml file is automatically created and I can't get rid of it. On the other hand, if you repeat the sequence but leave the Connection box empty, you won't get that behavior.

    In my currently existing project, the only way I could solve the issue was by removing that line from the .ccsproject file:

    <connection value="common/targetdb/connections/SD510USB_Connection.xml"/>

    Base on these details, are you able to reproduce that on your side? Is this a normal expected behavior or I misunderstand the Connection box purpose?

    Thanks

    Franck

  • Hi Franck,

    ok, first of all if you keep your own repository of ccxml files, then I would for sure leave the connection box blank. 

    Confusing or not, this is the default behaviour.  When you fill in the connection box, CCS puts in a ccxml file into the default shared location (set in Window->Preferences->Code COmposer Studio->Debug).  

    So what you can do is one of two things

    - leave the connection box blank

    - right-click on your ccxml file and select "Set as default configuration".  This will set it do the default and I have verified you can open and close the workspace and it remains the default.  So you could give this a try.

    Does this help?

    Best Regards,
    Lisa

  • Thanks Lisa for the clarification.

    In my opinion, it is actually confusing, but at least it is explained.

    Your recommendation of selecting "Set as default configuration" does not prevent the "wrong" ccxml file to re-become the "Active" Target Configuration after I re-open the project even if my own ccxml file was tagged as "Default" and "Active" before I close. Is this also what you see?

  • Hi Franck,

    I see the same behaviour.  Although the "Default" is kept, CCS keeps reverting the active configuration to the automatically generated one.

    I have filed a bug against this with ID SDSCM00043435.

    You can track it at the following link

    https://cqweb.ext.ti.com/cqweb/main?command=GenerateMainFrame&service=CQ&schema=SDO-Web&contextid=SDOWP&username=readonly&password=readonly

    Best Regards and sorry for any inconvenience,

    Lisa