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.

TMS320F28379D: "identifier not found" Occurs on Static Structure

Part Number: TMS320F28379D

Greetings,

I am using CCS 9.1.0.00010 and have created a static array of structures called my_structure, in one of my cpp files.  It is declared as follows:

 #pragma DATA_SECTION(“STRUCT_LOC”)

static volatile struct MY_STRUCT my_structure[NUM_ELEMENTS]; 

When I try to see it in the Expressions window, as I type the name, I am offered my_structure.  I select it, but the value become “identifier not found my_structure”.  Also, it is not in the map file.  So CCS knows it exists, but doesn’t know anything else about it.  What do I need to do to make it visible to the tool?  Is there an alternative way to see the structure?

Thank you,

Ed

  • Hi Ed,

    Can you provide a simple test case (project + source) that I can run on my F2837x target? The simpler the better, as long as it can reproduce the issue. 

    Thanks

    ki

  • Hi Ki,

    I found a clue.  I removed the static part of the declaration, and now CCS sees the array.  Is this expected?

    Thank you,

    Ed

  • Hi Ed,

    Oddly, this is working for me (I can see it in the expressions view). Can you send my the non-working test case?

    Thanks

    ki

  • Hi Ki,

    Currently, this is part of our regular code set, so sending it to you isn’t possible.  For debugging purposes, removing the static part of the construct, which was done simply to hide it from the rest of the code, will work fine.

    As you said, it’s odd.  I have noted, that upon occasion, I have been able to see it without removing the static construct.  I don’t know what changed this time which made it un-findable to CCS.  If I can figure out a way to replicate it without sending you our IP, I will forward that project to you.

    Regards,

    Ed

  • If I can figure out a way to replicate it without sending you our IP, I will forward that project to you.

    Thanks Ed.

    If you can strip it down to just a skeleton with mostly just the structure definition, that would be enough (as long as it reproduces the issue). The code doesn't really have to do anything

    ki