• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 4866 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.

Device core Hung

Ajay Barboza
Prodigy 110 points

I am using evm6678l and the debugger was working fine since long, but Now when I try to connect the target, I get the following errors at different times:

1. Trouble Halting Target CPU: (Error -1060 @ 0x0) Device is not responding to the request. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.45.0) 

or

2. C66xx_3: Trouble Reading Memory Block at 0x1845028 on Page 0 of Length 0x4: (Error -1139 @ 0x1845028) Lost debug connection to device. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.45.0) 

C66xx_3: GEL: Error calling OnPreFileLoaded(): target access failed

or

3. Trouble Reading Memory Block at 0x2620020 on Page 0 of Length 0x4:

(Error -1202 @ 0x2620020)
Device core is hung. The debugger will attempt to force the device to a ready state to recover debug control. Your application's state will be corrupt. You should have limited access to memory and registers, but you may need to reset the device to debug further.
(Emulation package 5.1.45.0)
I am not sure what is going wrong as I have not changed the gel, target configuration file since it was working last.
I have tried power cycle and reset. The emulator I am using is BlackHawk XDS560v2.
  • 0
    TI__Guru**** 171004 points

    Hi,

    If you are getting these different errors at random times, then I suspect there may be some hardware failure starting to develop. The messages you sent seem to be focused on the device (random reset or power down issues, core locked up due to an exception or peripheral, fluctuation on power supply lines), but it is also possible the cable and the XDS560v2 emulator be at fault (loose connections on cable or connectors, intermittent issues, etc.). The root cause of such issues is usually easier to detect if you have a spare board and / or an emulator.

    If these errors happen all the time, then I would still suspect the hardware but thoroughly check the page Debugging JTAG Connectivity Problems, which has a good strategy to investigate problems of this nature.

    Hope this helps,

    Rafael