• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 52 subscribers
  • Views 887 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.1.1 ioport not working

David Ryan
Intellectual 295 points

I just upgraded to CCSv5.1.1 from CCSv4.

In my code, I have a bunch of lines that look like this:
volatile ioport uint16_t * ACS2CR1 = (volatile uint16_t *) 0x1010;

Those now get flagged as syntax errors by the Eclipse CDT parser (see this post).

However, it seems that in my CCSv5.1.1, it ALSO gives me compile errors when I try to use that variable. Therefore, I can't build.

Error: Symbol 'ACS2CR1' could not be resolved
Type: Semantic Error

That error occurs on this line:
*ACS2CR1 = 0x0501;

  • 0
    Intellectual 295 points

    Also, perhaps you should make it more obvious on the wiki that CCSv5.1.1 is still in beta testing.

    It wasn't until I encountered problems that I went back and noticed that the "Latest production release is 5.1.0.09000" rather than the most recent version (5.1.1.00028).

  • 0 in reply to David Ryan
    Intellectual 295 points

    I uninstalled, then installed the "production release" (CCS 5.1.0). That didn't fix the problem.

    Turns out you have to go to Window>Preferences.

    Then select C/C++>Code Analysis. Then uncheck all of the boxes. Click Apply, OK. Then restart CCS.
    I guess the Eclipes static code analysis prevents valid code from compiling when there are errors. Seems like this should be turned off by default.