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.

TMS320C6726B: Symbol 'IER' could not be resolved

Part Number: TMS320C6726B

Hi Team,

Customer use CCS7.4.0.00015 Compiler v7.3.23 for TI device TMS320C6726.

In the source code (C language), there is the processing of setting "IER".

IER |= 0x3102;

When Compiling, there is a message as below.

Multiple markers at this line
- main.c, line 85[S/W BP]
-Symbol 'IER' could not be resolved

do you know the reason and can you give me advice on the solution?

BTW, I found a thread e2e.ti.com/.../ccs-tms320f28069-ccsv730-shows-linker-errors-symbol-ier-could-not-be-resolved

Is this the real reason?

---------------------------------------------------------------------------------------

These errors are not build errors.

You can make sure - click "build" and then open Build Console -

you will see that build was successful.

These are errors of Eclipse code analysis system.

It doesn't work good in fact, so i usually turn analysis off.

-----------------------------------------------------------------------------

If so,  how to turn off Eclipse code analysis system?

Thanks.

Regards,

  • Hi,

    This does seem to be an issue with CCS/Eclipse. Let me loop in CCS expert to help.

    Regards,

    Jianzhong

  • Code Analysis can be turned on at the workspace level or on a per-project basis.  In general, it is off by default in newer CCS releases due to issues like this as it is a general code analysis tool and not aware of TI-specific symbols.

    If you bring up the preferences dialog.  Click on Show advanced settings at the bottom left.  Then Code Analysis can be found under C/C++ -> Code Analysis

    It can be a pain to turn it off.  You could just turn off the rule for unresolved symbols.  It is near the bottom of the list:

    Similarly I would check the project properties, show advanced settings... and see if the project is using the workspace level settings or project specific settings.  If it is using project specific setting then disable the rule there as well.

    Regards,
    john