• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 52 subscribers
  • Views 484 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CCS/MSP430FR5849: Changing compiler version defaults a number of settings in a project with a large number of build targets.

Joshua van Tol
Intellectual 725 points
Part Number: MSP430FR5849

Tool/software: Code Composer Studio

I have an MSP430 project with a large number (64) of build targets, each building a slightly different variation of a product.  The difference between each come down to part number, and a few configuration switches.

Recently I've run into a problem where switching the compiler version on ONE target causes the .cproject file to be re-written in such a way as to default almost all the individual settings for all of the build targets.

This means the linker command file is defaulted, the include paths are defaulted, the pre-defined symbols are defaulted. Additionally the linker paths and included libraries get defaulted as well. The MPU support gets turned on as well, and probably a few other changes I haven't caught yet.

Needless to say, with 64 targets, this is a humongous pain. I've tried with CCS V8.1 8.2 and 7.3, and the same thing happens with all of them. I suspect that something has become corrupted in my .cproject file, and that's triggering the issue, but I'm not sure what it could be.

Are there any logs I could look at or other troubleshooting techniques I could use to narrow down the cause of this?

Regards,

Josh - AFD Engineering.

  • 0
    TI__Guru**** 173310 points

    Josh,

    Could you share your original .cproject file (prior to switching the compiler version) and the one it gets updated to after the change? You can zip them up and attach them here. Or if you prefer to share them privately, you can send me a private message (by hovering over my forum ID).

    I'm not sure if that alone will be sufficient to root cause the issue but let us start there. 

  • 0 in reply to AartiG
    Intellectual 725 points
    It looks like I may have found the root cause of the issue.

    At the beginning of this issue, I had re-named a number of build targets. At some point while I was in the midst of doing this, CCS crashed. I though little of it and proceeded. However, it appears that what got saved was a melange of old and new names. In particular, at the end of the .cproject file, there's a number of entries like this:

    <storageModule moduleId="refreshScope" versionNumber="2">
    <configuration configurationName="Debug_Build"/>
    <configuration configurationName="PartNumber1/>

    // Many lines omitted for clarity, configurationNames changed to protect the guilty.

    <configuration configurationName="PartNumber_62"/>
    <configuration configurationName="PartNumber_63"/>
    </storageModule>

    Many of these entries had the old configurationName, despite the name having been changed elsewhere in the file. Fixing up this discrepancy seems to have restored CCS to proper operation.

    Regards,
    Josh
  • 0 in reply to Joshua van Tol
    TI__Guru**** 173310 points
    Glad to hear that you were able to identify and fix the issue.