• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 718 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.

In CCS6 hardware break doesn't work when testing with AM437x IDK

khalid
Prodigy 80 points

I have AM437x IDK development board and I am using original files (GEL files etc..) provided in CCS6 to connect and debug the sample program(simple program to write 100 locations in DDR) on the board.

I can load code, it runs to main() and breaks, and I can step through. But when I set a hardware break point at a later stage and allow the code to run, it is not halting on the hardware break point.

Any suggestions?

PS: I have worked on AM335x EVM with CCS5. There I was able to put hardware break points and debug the Linux kernel also in stop mode.

  • 0
    TI__Guru**** 171044 points
    Hi,

    Thanks for reporting this. I was able to verify this issue on my IDK as well. I filed the bug number SDSCM00051939. Please check its status in the link SDOWP in my signature below.

    I apologize for the inconvenience,
    Rafael
  • 0 in reply to desouza
    Prodigy 80 points
    I am sorry I am not able to find out the bug report filed by you in the link.
    What is the priority for this bug?

    Actually we are struck with this issue when we are debugging our non-working kernel on this board. We are thinking of the following alternatives in order to avoid delays.

    1. Check this issue with older version of CCS assuming the issue is with the CCS6
    The issue in this alternative is bringing up the Am437x IDK support to CCS5.x

    2. Going ahead with other debuggers.
    We have to look at this approach.

    Any insights into the alternatives which we are thinking of?
  • 0 in reply to khalid
    TI__Guru**** 171044 points

    Hi,

    Is there a reason why you can't use software breakpoints? If the code is in RAM (most likely given the device does not have built-in flash) you should not have a problem - in my system here the SW breakpoints worked just fine.

    1. Although at first glance it may be possible to port the IDK to CCSv5.x, I wouldn't expect the projects created with v6 (as part of the IDK itself) will work in v5.5. In this case you may be looking at a lot of extra effort - not to mention that, if I recall correctly, AM437x is not officially supported in CCSv5.

    However, in lieu of your questions I just tested CCSv6.0.1 with TI Emulators component release 5.1.636.0 and hardware breakpoints worked. That is a safer alternative if you do require HW breakpoints.

    2. I am not sure what you mean by that. If you mean using a different JTAG debugger such as a XDS200 or any other, I was not able to make HW breakpoints work with these as well.

    Hope this helps,
    Rafael

    (edit) To install this TI Emulators package version, please refer to:

    http://processors.wiki.ti.com/index.php/XDS_Emulation_Software_Package

  • 0 in reply to desouza
    Prodigy 80 points

    Thank you so much for supporting us in this issue.

    desouza >> However, in lieu of your questions I just tested CCSv6.0.1 with TI Emulators component release 5.1.636.0 and hardware breakpoints worked. That is a safer alternative if you do require HW breakpoint

    We are not able to test this at our end as the CCS is crashing when connecting to the target and we didn't debug this issue.

    We have inserted the software break point in the Linux kernel "start_kernel" function and we are able to halt the CPU. After this we are able to set the break points for the debug. This is not standard but served our purpose to debug the kernel.