• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 55 subscribers
  • Views 3435 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 5.1 Semantic Errors, but still compiling and linking

Vitaliy V.
Prodigy 135 points
Other Parts Discussed in Thread: TMS320C6678

Hello,

I've got some strange issues with Code Composer Studio.

I am working on some projects for the C6678 evaluation board. Every time I open the main.c file in CCS the Problems view becomes full with semantic errors and error markers are generated in the editor:

Type 'Error_Block' could not be resolved
Type 'IHeap_Handle' could not be resolved
Type 'HeapMem_Handle' could not be resolved
Type 'HeapMem_Params' could not be resolved

However, the necessary headers are all there. The Projects are also compiled and linked to binary without a problem. The CDT build console prints no errors or warnings. I can even run and debug the projects using JTAG on the evaluation board.

So why does the editor generate those Errors?

The RTSC configuration is:

XDCtools version: 3.23.2.47
IPC version: 1.24.2.27
MCSDK PDK TMS320C6678 version: 1.0.0.20
Sys/Bios version: 6.33.4.39
System Analyzer version: 1.1.0.04

The compiler version is 7.3.5

OS is Windows7 x64. All files are installed into C:\ti\

  • 0
    Intellectual 840 points

    Hello Vitaliy,

    If I get you correctly, then It means When You make any project and when you create or import any main.c file to it, It will automatically giving you many such type of errors, but Once you build it then it builds fine and after that you can debug it as well and it is also going great. If I have understood correctly then can you please check in properties under debug option whether block is checked in front of Automatically program halt on debug See after that. If you don't mind can you attach your project we can see what actually is the problem. And one more thing Are you creating RTSC projects or sys/bios one? 

  • 0 in reply to Arun
    Prodigy 135 points

    Hi Arun,

    Thanks for your answer.

    The issue is not specific to ‘main.c’. If I create additional source files and include the necessary headers I get error markers for some of the types, too. Even after a successful build, the error markers stay where they were.

    I didn't find the block you mentioned in the debug options. However, my program halts at main after it is loaded to the DSP and I have to resume all cores manually in the debugger to start analysis.

    In my opinion it’s a problem with the Eclipse CDT part, which parses the code. It’s out of sync with the compiler options somehow.
    I can't publish the current project. Probably I can create a small one-file demo project to reproduce the error. Will post it here then.

    My projects are all RTSC projects.

  • 0
    TI__Guru**** 173310 points

    Vitaliy V. said:

    I am working on some projects for the C6678 evaluation board. Every time I open the main.c file in CCS the Problems view becomes full with semantic errors and error markers are generated in the editor:

    Type 'Error_Block' could not be resolved
    Type 'IHeap_Handle' could not be resolved
    Type 'HeapMem_Handle' could not be resolved
    Type 'HeapMem_Params' could not be resolved

    The errors you are seeing are syntax errors reported by the CDT Indexer and not by the TI code generation tools. Are you using a workspace that was created with an older version of CCS? We have seen these issues few times before when users were working with older workspaces, and hence the settings we changed in CCS to "fix" these indexer issues were not picked up.

    I am assuming you are using CCS 5.1.0 or 5.1.1. If so, try opening a new clean workspace and import your project into it and let us know if the errors persist.

  • 0 in reply to AartiG
    Prodigy 135 points

    Thank You AartiG, it worked.

    I tried creating new workspaces previously, but I always used "Import->General->Existing Projects into Workspace".

    Now I tried "Import->Code Composer Studio->Existing CCS/CCE Eclipse Projects" and the error markers are not reappearing so far :)

    Regards
    Vitaliy

  • 0 in reply to Vitaliy V.
    Mastermind 6240 points

    Hi,

    Just to add another strange problem that had the same solution:

    I made some small changes to my code (like add one System_printf) and my project just wouldn't build anymore with the semantic error:

    Type 'Error_Block' could not be resolved

    so I undid the changes but the error message kept showing up, I even restored my project from the SVN repository, but the error didn't disappear.

    Then the solution was also to create other workspace and import the project like Vitaliy suggested.

    Regards

  • 0 in reply to AartiG
    Intellectual 300 points

    It takes my weekend. Now it works,

    Thank you AartiG

  • 0 in reply to Johannes
    Guru 35565 points

    Johannes said:
    the solution was also to create other workspace

    The seems to be a general Eclipse feature.

    Just like the default answer for any Windows problem is, "have you tried restarting winodws" - so the default answer for any Eclipse problem is, "have you tried a new Workspace".

    I don't use CCS, but I have seen this on other Eclipse-based IDEs