• State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 21 subscribers
  • Views 1360 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Using ULINKpro/Trace to debug a crashed CPU

Gunnar Bohlen

Hello,

I'm using ULINKpro (ETM Trace enabled) to debug a problem with my code on a LPC4357. In some situations the CPU crashes. I would like to use the "Trace Data" view to see the last instructions that the CPU was doing before it crashed.
As soon as the CPU crashes I stop the debugger. But then µVision only tells me

"Could not stop Cortex-M device! Please check the JTAG cable."

When I press the OK-Button, the debugg session is closed and I cannot see the Trace data any more.
How do I use the "Trace data" in such a situation correctly?

After this crash a normal "reset" does not recover the CPU, a power cycle is required.
This crash may be related to inter-cpu communication. CM0 and CM4 exchange a lot of data via IPC.

Thank you.

0