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.

Project library building and eclipse errors

Other Parts Discussed in Thread: SYSBIOS

I have two CCS-5 projects that are very similar but have a couple differences I can't find.

They are for the DM8148 DSP and are based on the syslink messageQ_DSP examples.  Both projects produce a working executable.

The first project is based directly on the messageQ_DSP example.  It links to the IPC library.  Eclipse is able to resolve symbols.

The second project is an existing SysBios project that has had the messageQ_DSP functionality merged in.  When it builds, it seems to recompile the IPC and sysbios libraries and create a "Src" directory in the project.  Also eclipse is flooded with "symbol ... could not be resolved" and some other errors.  These are not actual compiler errors, the build is clean but the errors appear when the file is opened.

I've been unable to find any difference in the projects to cause this.

What controls if the library is rebuilt?

What does eclipse need to work correctly? (not show false errors)

  • David,

    I think your SYS/BIOS project's config file has this line in it:

        BIOS.libType = BIOS.LibType_Custom;

    This setting causes application specific SYS/BIOS and IPC libraries to be generated in the 'src' directory.

    I'm not sure I understand the error messages you're getting.

    They seem like linker errors but you say they "appear when the file is opened". Can you clarify what you mean?

    Have you performed a 'clean' of the project?

    You might also try manually deleting the 'src' directory after a 'clean' before rebuilding.

    Alan

  • Yes, that is the difference in building the library.

    I added the line above to the "good" project and now it builds a library like the other one.

    I did not change the actual problem.

    The "errors" I'm speaking of appear in the CCS "Problems" window (not the "console" compiler output).  I can disable the errors by selecting "configure contents" in the drop down box and then unchecking  "semantic error".

    Although they sound like linker errors, they are not from the real compiler.  They are from an eclipse tool.

    If I have all editor windows closed, there are no errors.  As I open a file, eclipse then looks at it and fills the "problem" box with errors.

    Some examples are below.

    Description Resource Path Location Type
    Symbol 'BIOS_WAIT_FOREVER' could not be resolved MessageQApp.c /sysBiosDemoPrj line 194 Semantic Error
    Symbol 'Cache_Type_ALL' could not be resolved MessageQApp.c /sysBiosDemoPrj line 382 Semantic Error
    Symbol 'Cache_Type_ALL' could not be resolved MessageQApp.c /sysBiosDemoPrj line 413 Semantic Error

    It's not just the error messages that are a problem, the debugger also can't find these symbols.

    Thanks,

    David

  • I understand now.

    It seems that the include file search path doesn't have an entry for the SYS/BIOS installation.

    Have a look at the following forum post and see if the suggestion resolves your issue:

        http://e2e.ti.com/support/embedded/bios/f/355/p/200594/714280.aspx#714280

    Alan

  • Alan,

    That post seems to describe a very similar issue (on the ARM compiler).

    I've tried add every path I can think of but to no avail.

    The "good" project does not have any entries other than the tool chain.

    Some of what I added

    "${CG_TOOL_ROOT}/include"
    "${workspace_loc:/${ProjName}/SourceLinks}"
    "C:\ti2\bios_6_33_04_39\packages"
    "C:\ti2\ipc_1_24_03_32\packages"
    "C:\ti2\syslink_2_10_05_26\packages"
    "${workspace_loc:/${ProjName}/src}"

    Thanks,

    David

  • You can never distrust Eclipse enough.

    Deleting the .metadata folder and re-imported the project got rid of the problem.  

    I should have thought of that sooner, it fixes many things on Eclipse based products.

  • I'm glad you figured that out.

    I don't think I would have ever suggested deleting the .metadata folder.

    Alan