• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 54 subscribers
  • Views 1682 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.

What's wrong with CCS-5.4 in using macro __DATE__ for C674x of OMAP-L138

Duy-Ky Nguyen88210
Expert 2250 points

Other Parts Discussed in Thread: OMAP-L138, AM1808

Hello,

I was adviced to upgrade CCS-5.2 to 5.4 as 5.2 does not display option to choose config file XML

Now I run into problem using CCS-5.4 as it handle macro __DATE__ not properly in C674x core of OMAP-L138, but it's OK with AM1808 core of this chip.

It seems compiling fine, but it reports so many errors in "Problems" windows, so it displays RED mark all over the place in IDE.

Any idea what wrong with CCS-5.4

Thanks,

~Duy-Ky

  • 0
    TI__Guru**** 484151 points

    Hi Duy-Ky,

    Duy-Ky Nguyen88210 said:
    It seems compiling fine, but it reports so many errors in "Problems" windows, so it displays RED mark all over the place in IDE.

    Sounds like these are "errors" from the built in CDT code analysis tool that comes with CCS. The tool sometimes has issues resolving built-in TI macros. You can ignore this or turn off the coverage tool if it bothers you

    Thanks

    ki

  • 0 in reply to Ki
    Expert 2250 points

    Hi Ki,

    It happens to the DSP core only, not the ARM one !?

    It really bothers me as RED marks all over the place of the project in IDE!

    How to turn it off?

    Thanks,

    ~Duy-Ky

  • 0 in reply to Duy-Ky Nguyen88210
    TI__Guru**** 484151 points

    Can you send me a small test case? A small project that can reproduce the issue.

    Thanks

  • 0 in reply to Ki
    Expert 2250 points

    Hi Ki,

     Below are my findings:

    1) There's NO problem in a simple C674x project using OMAP-L138 using CCS-5.4

    2) I have no such problem so far using CCS-5.2

    3) But the problem occurs in ONE of my C674x projects (NOT ALL), even such project has no problem with CCS-5.2

    So, it's hard for me to duplicate the problem in small project.

    I can zip and send that problematic project if you send me an email to "duykyng@unitedthc.com"

    Below is a capture from "Problems Window" even after a successful compilation!

    Thanks,

    ~Duy-Ky

    Description    Resource    Path    Location    Type
    Type 'HST_Obj' could not be resolved    mimocfg.h    /blueMoon_DSP_1b5e/Debug    line 24    Semantic Error
    Type 'PRD_Obj' could not be resolved    mimocfg.h    /blueMoon_DSP_1b5e/Debug    line 23    Semantic Error
    Symbol '__LINE__' could not be resolved    UPPinputDriver.c    /blueMoon_DSP_1b5e/src    line 406    Semantic Error
    Type 'PRD_Obj' could not be resolved    mimocfg.h    /blueMoon_DSP_1b5e/Debug    line 22    Semantic Error
    Symbol '__LINE__' could not be resolved    UPPinputDriver.c    /blueMoon_DSP_1b5e/src    line 405    Semantic Error
    Type 'PRD_Obj' could not be resolved    mimocfg.h    /blueMoon_DSP_1b5e/Debug    line 21    Semantic Error
    Type 'Arg' could not be resolved    UPPinputDriver.c    /blueMoon_DSP_1b5e/src    line 402    Semantic Error
    Type 'TSK_Obj' could not be resolved    mimocfg.h    /blueMoon_DSP_1b5e/Debug    line 28    Semantic Error
    Type 'SWI_Obj' could not be resolved    mimocfg.h    /blueMoon_DSP_1b5e/Debug    line 27    Semantic Error
    Type 'SWI_Obj' could not be resolved    mimocfg.h    /blueMoon_DSP_1b5e/Debug    line 26    Semantic Error
    Type 'HST_Obj' could not be resolved    mimocfg.h    /blueMoon_DSP_1b5e/Debug    line 25    Semantic Error
    Type 'STS_Obj' could not be resolved    mimocfg.h    /blueMoon_DSP_1b5e/Debug    line 32    Semantic Error
    Type 'LOG_Obj' could not be resolved    mimocfg.h    /blueMoon_DSP_1b5e/Debug    line 31    Semantic Error
    Type 'LOG_Obj' could not be resolved    mimocfg.h    /blueMoon_DSP_1b5e/Debug    line 30    Semantic Error
    Type 'TSK_Obj' could not be resolved    mimocfg.h    /blueMoon_DSP_1b5e/Debug    line 29    Semantic Error
    Type 'uint32' could not be resolved    mimoBSL_utilities.h    /blueMoon_DSP_1b5e/inc    line 25    Semantic Error
    Type 'uint32' could not be resolved    mimoBSL_utilities.h    /blueMoon_DSP_1b5e/inc    line 24    Semantic Error
    Type 'uint32' could not be resolved    mimoBSL_utilities.h    /blueMoon_DSP_1b5e/inc    line 24    Semantic Error
    Type 'uint32' could not be resolved    mimoBSL_utilities.h    /blueMoon_DSP_1b5e/inc    line 24    Semantic Error
    Symbol '__TIME__' could not be resolved    Main.c    /blueMoon_DSP_1b5e/src    line 145    Semantic Error
    Type 'Arg' could not be resolved    SATAoutputDriver.c    /blueMoon_DSP_1b5e/src    line 143    Semantic Error
    Type 'uint32' could not be resolved    mimoBSL_utilities.h    /blueMoon_DSP_1b5e/inc    line 24    Semantic Error
    Symbol '__DATE__' could not be resolved    Main.c    /blueMoon_DSP_1b5e/src    line 145    Semantic Error
    Type 'Arg' could not be resolved    SATAoutputDriver.c    /blueMoon_DSP_1b5e/src    line 496    Semantic Error
    Type 'uint8' could not be resolved    mimoBSL_utilities.h    /blueMoon_DSP_1b5e/inc    line 23    Semantic Error
    Symbol '__LINE__' could not be resolved    UPPinputDriver.c    /blueMoon_DSP_1b5e/src    line 240    Semantic Error
    Type 'uint8' could not be resolved    mimoBSL_utilities.h    /blueMoon_DSP_1b5e/inc    line 23    Semantic Error
    Type 'uint8' could not be resolved    mimoBSL_utilities.h    /blueMoon_DSP_1b5e/inc    line 23    Semantic Error
    Symbol '__LINE__' could not be resolved    UPPinputDriver.c    /blueMoon_DSP_1b5e/src    line 341    Semantic Error
    Symbol '__LINE__' could not be resolved    UPPinputDriver.c    /blueMoon_DSP_1b5e/src    line 342    Semantic Error
    Symbol '__LINE__' could not be resolved    UPPinputDriver.c    /blueMoon_DSP_1b5e/src    line 269    Semantic Error
    Type 'Arg' could not be resolved    UPPinputDriver.c    /blueMoon_DSP_1b5e/src    line 337    Semantic Error
    Symbol '__LINE__' could not be resolved    SATAoutputDriver.c    /blueMoon_DSP_1b5e/src    line 514    Semantic Error
    Symbol '__LINE__' could not be resolved    SATAoutputDriver.c    /blueMoon_DSP_1b5e/src    line 500    Semantic Error
    Symbol '__LINE__' could not be resolved    SATAoutputDriver.c    /blueMoon_DSP_1b5e/src    line 499    Semantic Error
    Symbol '__LINE__' could not be resolved    CollectManager.c    /blueMoon_DSP_1b5e/src    line 614    Semantic Error
    Symbol 'TSCL' could not be resolved    CollectManager.c    /blueMoon_DSP_1b5e/src    line 505    Semantic Error
    Symbol '__LINE__' could not be resolved    CollectManager.c    /blueMoon_DSP_1b5e/src    line 244    Semantic Error
    Type 'Arg' could not be resolved    CollectManager.c    /blueMoon_DSP_1b5e/src    line 252    Semantic Error
    Symbol 'TSCH' could not be resolved    CollectManager.c    /blueMoon_DSP_1b5e/src    line 504    Semantic Error
    Type 'PRD_Obj' could not be resolved    mimocfg.h    /blueMoon_DSP_1b5e/Debug    line 20    Semantic Error



  • 0 in reply to Duy-Ky Nguyen88210
    TI__Guru**** 484151 points

    Duy-Ky - I will contact you privately. Thanks

  • 0 in reply to Ki
    Prodigy 120 points

    Did this ever get resolved?

    I have a similar problem.  If it was fix I'd like to check if it resolve the errors I get too. If not, is there a bug tracking number?

  • 0 in reply to Steven Borley
    Expert 2250 points

    Not yet.

    Ki did submit a bug report

  • 0 in reply to Duy-Ky Nguyen88210
    Prodigy 120 points

    So, Is there a bug number? 

    I found this bug SDSCM00046042, which looks similar, but  I also had problems with macros set in  a Command File not being recognised.

    I've found turning off the relevant error in Code Analysis is a work round for me.