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/MSP430G2755: After importing a CCC 5.5 project into 7.1, nothing in the XML files indicates the new CCS version

Part Number: MSP430G2755

Tool/software: Code Composer Studio

I imported a project from CCS 5.5 into CCS 7.1. However, nothing in the XML files (.project,.cproject,.ccsproject) indicates the new CCS version. In fact, the XML files still indicate CCS 5.5 with the following line in .cproject:

---------------------------------------------

<listOptionValue builtIn="false" value="CCS_MBS_VERSION=5.5.0"/>

---------------------------------------------

This means that aside from careful notes in a revision control system, there is no way to know which tool version to use. Yes, the compiler version IS in the XML files but that is not enough. It still leaves the user guessing as to which CCS GUI this particular XML file-and-project in general is compatible with.

I found clues in the makefile:

---------------------------------------------

"C:/ti/ccsv7/ccs_base/msp430/include"

"C:/ti/ccsv7/tools/compiler/ti-cgt-msp430_16.9.2.LTS/lib"

... etc, etc....

---------------------------------------------

However, because the makefile is a generated file, it is not normally checked into version control. So, if this project were checked out, zipped up, and handed off, the XML file would lead the recipient to believe that CCS 5.5.0 should be used. When in-fact, the last build was done with CCS 7.1.0.

CCS should insert some benign tags to indicate the change of CCS version so the tool is self-documenting about that.

Regards,

Jim

  • Jim,

    CCS_MBS stands for Code Composer Studio Managed Build System. Basically the build system that we have implemented in Eclipse. This version is used to determine if a project migration is necessary. The MBS version doesn't actually change that frequently. I have CCSv7.2.0 installed (beta) and it still has a CCS_MBS version of 6.2.0. The team tries to keep changes to a minimum that would introduce the need to migrate projects.

    As of CCSv7.0 there is a field in the .ccsproject and indicates which version of CCS (instead of MBS) was used to create the project.

    <ccsVersion value="7.2.0"/>

    That doesn't get updated when you import it only gets set when you create the project.

    The MBS version on the other hand should update when you import and a migration is required. I will get back to you with more info on that.

    Regards,
    John