• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 1038 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.

CCS/CCSTUDIO: Indexer issue with C/C++ projects

Andre de Castro
Prodigy 180 points
Part Number: CCSTUDIO


Tool/software: Code Composer Studio

I have observed an issue with the indexer on CCS 8.3.0.00009 both on Windows and on macOS.

"Open Declaration", "Open Type Hierarchy" and "Open Call Hierarchy" do not work.

Editor colors for class namespace in method signatures are wrong, as are editor colors in the name of the class from which one inherits. The following pictures show what I mean.

Rebuilding the index seems to not do anything, as I see no progress bar in the lower right corner when using it.

Please also find attached a minimal project that reproduces this issue.

0160.test_project.zip

  • 0
    TI__Guru**** 473271 points
    Hi Andre,
    It is a known issue that impacts standard (non-CCS) Eclipse CDT projects using GCC. The tracking ID is: CCSIDE-3466

    It will be fixed in the upcoming CCS 9.0 release (ETA: e/o the month)

    Thanks
    ki
  • 0 in reply to Ki
    Prodigy 180 points

    Understood. Thank you, Ki.

  • 0 in reply to Ki
    Intellectual 260 points

    Hi,

    I am experiencing the same problem (Windows 10 64-bit, CCS 8.2.0.00007).

    However, I am somewhat alarmed at the fix not being available until CCS 9.0. I have recently spend days porting a simplelink (EasyLink) application to CCS8 from CCS7 which is still not working as it did before, due to updates in the EasyLink software that are not backwardly compatible. Will CCS9 introduce similar backward incompatibilities.

    I had a working multi-node - collector network running with CCS7.4.00015 on a Win8.1 Macbook Pro bootcamp and now I need to add a new node and I am struggling to get it working on CCS8.2.0 on my new Lenovo desktop. XDS110 debugger requires firmware update for CCS8 and so I cannot back track to CCS7.

    Even CCS7 on my new desktop is failing to build my legacy application.

    So, you can understand why I am not keen to waste more time getting things working only to have to redo it all again in CCS9.

    Best Regards

    Martin

  • 0 in reply to Martin Knott10
    TI__Guru**** 473271 points

    Martin Knott10 said:
    I have recently spend days porting a simplelink (EasyLink) application to CCS8 from CCS7 which is still not working as it did before, due to updates in the EasyLink software that are not backwardly compatible. Will CCS9 introduce similar backward incompatibilities.

    I'm not sure how updating the IDE version would impact the EasyLink software compatibility. Note that you can always use the same compiler and ti-rtos versions you used in CCSv7 with CCSv8. the IDE should have minimal impact IMHO.

    Martin Knott10 said:
    XDS110 debugger requires firmware update for CCS8 and so I cannot back track to CCS7.

    It is true that the new emu pack that comes in v8 will require a firmware update for the debug probe. But should still be able to use the target/probe with CCSv7

    ki