• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 2497 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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: Object file contains invalid call frame information at .debug_frame

Bruno Saraiva
Guru 13040 points
Other Parts Discussed in Thread: UNIFLASH

Tool/software: Code Composer Studio

I'm confronting this interesting new message:

"CORTEX_M4_0: Symbol Manager: the object file contains invalid call frame information at .debug_frame 0x2d3a; the rest of call frame information will be skipped. Callstack may not be unwound properly."

Some relevant information:

- CCS 7.3.0.00019 running in Windows PC
- Started showing up today, after updating the TI Emulators package to 7.0.100.1
- Probe is XDS110
- Targets are TM4C1294NCDPT

The project is a stable one, I do not suspect anything in it, the boards are good and proven.

Something seems to have become conflicting on the debugger (after the update, the actual firmware inside the debugger also got updated):

On target board "A', I could no longer start a debugger session. I was able to download new firmware to it directly via Uniflash, but not via the CCS Debugger... Temporarily changed the probe to a ICDI, and got it running on CCS.

On target board "B", these Invalid Frame messages are showing in the Console.

Any ideas?

Bruno

  • 0
    TI__Guru**** 450011 points
    Hi Bruno,
    Are you building GCC and using C++?

    Thanks
    ki
  • 0 in reply to Ki
    Guru 13040 points

    Hello Ki!
    Using plain C.
    Compiler is TI 16.9.4 LTS. (Edited later, correct information would be 16.9.6 LTS)
    Board "B" project issue is fixed, I deleted the folders .settings, .launches and targetConfigs.
    Will give it a try on Board "A" project as well, and see if I can use XDS110 on it again.
    Regards
    Bruno

  • 0 in reply to Ki
    TI__Guru**** 450011 points

    Actually, scratch that. I believe you are running into known issue: CCBT-2123

    The root cause is a compiler issue: CODEGEN-2399

    Before CCS 7.3.0, CCS would hang when trying to read corrupted DWARF output. Now it will simply skip the corrupted info and output the message you see now.

    To resolve the root cause of the corrupted DWARF output, please update your compiler version to at least 16.9.6.LTS (CCSv7.3.0 comes with 16.9.4.LTS).

    Thanks
    ki

  • 0 in reply to Ki
    Guru 13040 points
    Hello again,
    My replied was flawed as well! Curse CTRL+C CTRL+V, I had copied the compiler from my revision file and it was wrong!
    Short version: the compiler had already been changed to 16.9.6.LTS. But maybe something was left corrupted in the process...
    Deleted the same three folders from project A, and now I can use XDS110 normally, and the messages are gone.
    Regards
    Bruno