• Locked Locked
  • Replies 2 replies
  • Subscribers 55 subscribers
  • Views 5492 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.

Debugging on TMS570LS1227 : No symbols are defined for 0X______

Shivaram Singh Rajput
Prodigy 75 points
Other Parts Discussed in Thread: TMS570LS1227, TMS570LS20216, HALCOGEN

Hi ,

I have loaded a .elf binary to TMS570LS1227, when it enters the debug window, I see no symbols are defined for 0x0000040C  and the memory  content is as seen in the screen shot below .

 

As I step through the memory location changes and the memory content and disassemble window for one such location is as seen in screenshot below. 

Can some one explain why this happens and how can it be solved ? 

It is hard to debug as it doesnot point to any particular function or symbols .

  • TI__Guru**** 171309 points

    Hi,

    The code loaded to the entry point most probably is not mapped to any source code present in your workspace. In this case I suggest you take a look at the two references below:

    processors.wiki.ti.com/.../Debug_Handbook_for_CCS

    https://youtu.be/QvK-QOdK134

    I suspect the TMS570 is either protecting or remapping the referenced memory regions during runtime. Given this is an intricate part of how the device operates, I strongly suggest you to ask for suggestions on the Hercules device forum. I can move this thread there if you prefer.

    Hope this helps,
    Rafael

  • Guru 92251 points

    Shivaram Singh Rajput said:
    As I step through the memory location changes and the memory content and disassemble window for one such location is as seen in screenshot below. 

    What software is used for the device initialization / run time library code?

    Maybe the start-up code which calls main() doesn't set up the information required to allow the stack unwinding in the CCS debugger to resolve where main() was called from.

    [Based upon the filenames / functions in your stack backtrace I think you may be using AutoSAR and/or FreeRTOS]

    Using a TMS570LS20216 with CCS 6.1.3 and either the TI ARM compiler start-up code or the HALCoGen start-up code I am unable to repeat this problem, in that that stack backtrace correctly shows the entry point as step through the code. E.g. with a project which use the TI ARM compiler v15.12.3 start-up code: