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: CCS debugger expressions window

Tool/software: Code Composer Studio

Hello,

I have a project for a MPU core (Cortex A15) and i am using the gnu (linaro ) v4.9.3 for it compilation and linking.

From some reason when debugging the code (i.e. using JTAG), the debugger does not recognize correctly the type of a variable that is defined in a file that is located in the project's linked folder.

i.e i have a structure variable defined in a source file (under a linked folder) and when trying to see this variable in the expressions window from the A15 core, it only recognizes the symbol name (and thus correctly shows its address) but it does not recognize it as a structure type and treats it as int* type.

When placing the variable's definition in a local project source file the debugger is detecting the variable type properly and able to show all the structure's members.

I am building the project without any optimization and with debug information enabled and i have also tried setting different dwarf levels but so far, nothing seems to be working.

I would really appreciate any help you can give us as it really hinders our work.

Thanks

Guy

  • I tried again using dwarf level 2 instead of dwarf level 3 it seems to be working better (not sure why the first time i tried it it did not work).

    Anyway - there seem to be an incompatibility between CCS debugger and gnu tools - is that something that is under review ? is there a newer version that fixes it?

    ( i am using CCS version 8.1.000011)

    Thanks
    Guy
  • Hi Guy,

    Guy Mardiks said:
    Anyway - there seem to be an incompatibility between CCS debugger and gnu tools - is that something that is under review ?

    The debugger has historically had better support for TI CGT output over GCC output. It is something we have been constantly working on to close the gap. 

    Guy Mardiks said:
    is there a newer version that fixes it?

    We are always making fixes but I can't say with any certainty that it is resolved in a later CCS version. Your version is fairly recent. There is a CCSv8.3.0 release coming next week. You may want to wait for that version and try it out. If there is no luck, please provide a small reproducible test case for us to try locally so we can investigate further.

    Thanks

    ki