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.

Linux/AM5726: SPL debug in CCS

Part Number: AM5726
Other Parts Discussed in Thread: AM5728

Tool/software: Linux

Champs,

there is number of discussions on the forum on this topic however in the current SDK (4.03.00.05) the problem still persists: ie it is not possible to setup a source breakpoint in SPL and step through with CCS debugger. One post here:

e2e.ti.com/.../642740

proposes rather elaborate procedure that apparently works but I am wondering if there are any plans to support this in the SDK in a more streamlined manner.

thanks

Michael

  • Hi Michael,

    A few weeks ago a colleague from CCS and I were testing debugging SPL on CCS 8.0, but it was on Windows. We did not have to do anything from the link you posted. I just installed CCS 8.0 on my Linux PC and could set breakpoints and it all worked as expected.

    Steve K.

  • Hi Steve,

    I guess there is something I am missing then, because I am trying exact same thing on AM5728 IDK. I also have CCS 8.0 on Ubuntu 14.04 using SD XDS560.v2 JTAG. I follow the following steps:

    • Create uboot project in CCS following the old Sitara training steps
    • Connect to A15_0
    • load $uboot/spl/u-boot-spl.bin to 0x40300000
    • Load symbols $uboot/spl/u-boot-spl

    At this point I can step through the disassemby code and I do see the symbols in disassembly. However, when I create a breakpoint either in disassembly or in source and hit "run" it never stops at the breakpoint. I tried breaking in the function preloader_console_init() which is ran for sure (I put some puts() calls there and saw output on console)

    Does anything look suspicious in the above steps?

    thanks

    Michael

  • One thing I did was to do a CPU reset right after connecting. I'll try some more testing since I only set a few breakpoints here and there. I'm using an AM574x IDK and the built on XDS100 (which is horribly slow).

    Steve K.
  • Hi Michael,
    I am seeing some strangeness. Earlier I was setting breakpoints in disassembly. Now I set a breakpoint at do_board_detect and it hangs in do_fat_write. I'll contact a member of CCS and see what he thinks. I know in the past he said the Linux version of CCS does not always get the same level of testing as Windows. And I'll try this on Windows CCS.

    Steve K.
  • Hi Steve,

    I tried the same using on-board xds100.v2 and I am able to do breakpoints in both source and disassembly. This is rather unusual, I think first time in my experience where 560.v2 falls short compared to other JTAGs. The on-board xds100 is indeed very slow, would be nice to have the issue with 560 fixed. let me know over email where should I file the ticket

    thanks a lot for your help!
    Michael
  • Michael and I had some offline discussions. This is the result e2e.ti.com/.../713052

    Steve K.