• Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 200 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.

CCSv5 Conversion issues

Ian Cyr
Intellectual 325 points


Hello-

So we just got our licenses for CCSv5, and now have it installed on our development machines.  There are 3 machines that we're using - 2 personal computers for engineers and a lab machine.

We've got a project tested and working under CCSv4, and are now trying to migrate it to CCSv5, and are running into some problems.  I'm sure I'll be back later with some of the bigger issues, but for now, I have a really frustrating one.

On the 2 personal computers, the projects seem to have migrated fairly well, at least to the point where we can get them to compile.  However, on the lab machine we're having some real issues.  It seems to be throwing an error anywhere we actually reference a specific register.  For example:

        __bis_SR_register(LPM1_bits + GIE);

A fairly common piece of code for an MSP430, yet the compiler seems to be having a problem with accessing both the LPM1_bits and the GIE register.  CCSv4 never had this issue, and we've verified that msp430x54x.h is included in multiple locations in the project.  In fact, if we select one of the registers, such as GIE, and ask it to open the declaration, it correctly opens up msp430x54x.h and highlights the register definition, but it still complains that it's a syntax error.

Any idea what's causing this error, and how we fix it?

  • TI__Guru**** 173310 points

    Ian,

    I assume the syntax error is only an indexer error displayed in the editor and not a compiler error thrown during build.

    Did you directly open a CCSv4 workspace in CCSv5? This is generally not recommended and could cause these types of issues due to changes we had to make to the indexer settings when we moved to v5.

    Try opening a new clean workspace in CCSv5, and import the v4 project into it. Also check the following settings in your CCSv5:
    Right-click on the project, go to Properties->C/C++ General->Launching, and make sure that "Run with build" and "Run as you type" boxes are unchecked.

    If you have ensured these settings are correct and have tried a new clean workspaces and continue to see the problem, please attach a screenshot of the problem.