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

can CCSV5 do source level debug of u-boot for start.S with JTAT XDS100v2?

anthony fu
Prodigy 10 points


Hi,

I follow the U-boot Debug in CCSv5 as below link:

http://processors.wiki.ti.com/index.php/U-boot_Debug_in_CCSv5

But I had 2 problems when I want to do as "handling relocation" suggests:

1. I stop the CPU with a HW breakpoint at "relocate"(I can not find board_init_f in U-boot),  and try to examine the id->id->relocaddr in Variables view. But I can not find any thing there.

2. I also can not see the source code when breakpoint stop the CPU. In the source code view, it says"No source code available for 0x80e800a0" View disassembly. I can not only single step the code in disassembly view. Even I open the start.S file manually, the program counter does not change in start.S like the one in disassembly view. If I double click the line of source of start.S to enable a breakpoint, the breakpoint is added into the Breakpoint view but it seems not working(won't stop the CPU).

Can any one help with these 2 questions? I think it is crucial to bringing the board up in the early stage. thanks in advance.

Anthony

  • 0
    TI__Guru**** 171349 points

    Anthony,

    anthony fu said:

    1. I stop the CPU with a HW breakpoint at "relocate"(I can not find board_init_f in U-boot),  and try to examine the id->id->relocaddr in Variables view. But I can not find any thing there.

    Several things may prevent a variable or symbol to be seen by CCS, including facts like local variables being stored in registers, high optimization which can inline functions or optimize out variables, the code being built without symbols... Optimization and lack of debug symbols are the default options when u-boot is built.

    anthony fu said:

    2. I also can not see the source code when breakpoint stop the CPU. In the source code view, it says"No source code available for 0x80e800a0" View disassembly. I can not only single step the code in disassembly view. Even I open the start.S file manually, the program counter does not change in start.S like the one in disassembly view. If I double click the line of source of start.S to enable a breakpoint, the breakpoint is added into the Breakpoint view but it seems not working(won't stop the CPU).

    There is a reported issue that prevents source-code debugging with assembly source files (check bug number SDSCM00042271).

    At last, make sure you are setting the hardware breakpoints (not C/C++ breakpoints). Check the thread below for details:

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/122821.aspx#438884

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Prodigy 20 points

    I am using beaglebone and trying to get debugger working with XDS100v2 with CCS 5.2.0.00069. having same kind of issues mentioned below. . I tried both the solutions pointed by Rafael. Followed this http://software-dl.ti.com/sdo/sdo_apps_public_sw/CCSv5/Demos/u-boot_debug_autonomous/u-boot_debug_autonomous.html  to debug u-boot. Have the following issues. 

    1. I stop the CPU with a HW breakpoint at "relocate"(I can not find board_init_f in U-boot),  and try to examine the id->id->relocaddr in Variables view. But I can not find any thing there.

    2. I also can not see the source code when breakpoint stop the CPU. In the source code view, it says"No source code available for 0x80e800a0" View disassembly. I can not only single step the code in disassembly view. Even I open the start.S file manually, the program counter does not change in start.S like the one in disassembly view. If I double click the line of source of start.S to enable a breakpoint, the breakpoint is added into the Breakpoint view but it seems not working(won't stop the CPU).

    sri