• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Subscribers 54 subscribers
  • Views 2223 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/CCSTUDIO: Error highlighting and jumping to the error position in the source code with CCS 7.4 or CCS 8.0

Milan Bajza
Expert 1396 points
Part Number: CCSTUDIO
Other Parts Discussed in Thread: MSP430F67771

Tool/software: Code Composer Studio

Hello,

I am working with CCS 7.4 and with an imported makefile project. The target is an ARM M4 of the TDA3. The Project uses the compiler ti-cgt-arm_5.2.5 from VSDK 2.8. In the build options the error parsers are activated.

If a compiler error occures, there is no error highlightning in the console and therefore no jump to the apropriate source position is possible. Same project with CCS 5.5 recognizes the errors and a jump is possible.

Is it a bug or do I have to configure something?

Best regards,
Milan

  • 0
    TI__Guru**** 421380 points
    Hi Milan,
    Just so I understand clearly, this is not a CCS project but an external makefile project that you are working with correct? And it was the same in CCSV5.5 but in there the error parser was working correctly for the external makefile project?

    Thanks
    ki
  • 0 in reply to Ki
    Expert 1396 points

    Hi Ki,

    yes, you understood the question correctly. The same external makefile project is working with CCS 5.5 correctly and with CCS 7.4 and 8.0 the error parser is not working.

    Best reagrds,
    Milan

  • 0 in reply to Milan Bajza
    Expert 1396 points

    Hi Ki,

    I checked the CCS 7.3. The error parser is working with this version.
    So it seems that the last two versions of CCS have a bug and I hope that there is a workaround.

    Best regards,
    Milan

  • 0 in reply to Milan Bajza
    TI__Guru**** 421380 points
    That is interesting since the Eclipse and CDT version has not changed between the two versions and no changes were made in that area by the CCS development team. Would it be possible provide a small test case that is reproducible in your environment (works in 7.3, does not work in 7.4)? It can be as simple as a one source file makefile project.

    Thanks
    ki
  • 0 in reply to Ki
    TI__Guru**** 421380 points
    Hello,
    I haven’t heard back from you, I’m assuming you were able to resolve your issue. If not, please post a reply with an update below (or create a new thread).

    thanks,
    ki
  • 0 in reply to Ki
    Expert 1396 points

    Hi Ki,

    the problem is not resolved.

    Please see attached example project 8713.errorParser.7z It is a makefile project is is based on cmake. I tested this project with CCS 7.3 and 7.4 (CCS 8 seems to be same as CCS7.4). I can't send the original project from the customer. It is based on makefiles, too.

    I tried to import the project in two ways: "Existing Code as Makefile Project" and "Existing Projects into Workspace". Both import variations seems to work different in relation to error parsing.

    Existing Projects into Workspace

    Set folder "errorParser" to import and build the project. In both CCS versions error pasing doesn't work.

    Existing Code as Makefile Project

    Set folder "errorParser\build" to import and build the project.

    CCS 7.3

    The error parsing and the jump to the source file is working.

    CCS 7.4

    The error parsing is not working

    Ki, as you wrote in last mail, the CCS 7.3 and 7.4 are not identical in relation to error parsing. How does error parsing works? Is it realy text parsing of the compiler output, only? It does not seem like that. It seems, that there is a dependency of the project file or someting else. 

    What is the difference between the two import modes in detail?

    Best regards,

    Milan

  • 0 in reply to Milan Bajza
    Expert 1396 points

    Hello Ki or everybody,

    does anyone have a solution for this problem?

    Best regards,
    Milan

  • 0
    TI__Guru**** 421380 points
    Hello Milan,
    My apologies for the long delay. Thank you for the test case. I will able to simulate the environment and reproduce the issue. The settings appear fine in 7.4 so it looks like a regression of some sort.

    I have filed a bug for this issue. Tracking ID: CCSIDE-3338. If the bug is from Eclipse/CDT, then it will be more challenging to address since it will require a fix from the Eclipse community. We will review this bug later this week and I will have more details then.

    Thanks
    ki
  • 0 in reply to Ki
    TI__Expert 8395 points

    Hi Milan,

    The TI error parsers are now context-sensitive - they rely on knowing the current compilation context (source-file and tool).  They infer this information from the lines highlighted below:

    **** Build of configuration Debug for project a ****

    "C:\\CCS\\8.1.0.00008\\ccsv8\\utils\\bin\\gmake" -k -j 8 all -O

    Building file: "../main.c"
    Invoking: MSP430 Compiler
    "C:/CCS/8.1.0.00008/ccsv8/tools/compiler/ti-cgt-msp430_18.1.2.LTS/bin/cl430" -vmspx --data_model=restricted --use_hw_mpy=F5 --include_path="C:/CCS/8.1.0.00008/ccsv8/ccs_base/msp430/include" --include_path="C:/CCS/8.1.0.00008/ccsv8/eclipse/workspace/a" --include_path="C:/CCS/8.1.0.00008/ccsv8/tools/compiler/ti-cgt-msp430_18.1.2.LTS/include" --advice:power=all --define=__MSP430F67771__ -g --printf_support=minimal --diag_warning=225 --diag_wrap=off --display_error_number --silicon_errata=CPU21 --silicon_errata=CPU22 --silicon_errata=CPU40 --preproc_with_compile --preproc_dependency="main.d_raw" "../main.c"
    Finished building: "../main.c"

    To work-around this, could you modify your makefile to include those two lines before each compile rule?

    Thanks,

    - Baltasar

  • 0 in reply to Ki
    TI__Guru**** 421380 points

    Ki-Soo Lee said:
    I have filed a bug for this issue. Tracking ID: CCSIDE-3338.

    We plan on addressing this bug with the CCSv8.2.0 release (August). Thank you for your patience

    ki

  • 0 in reply to Ki
    Expert 1396 points

    Thank you Ki,

    we will try to use the workaround and await the CCS 8.2 release.

    BR,

    Milan