-
Notifications
You must be signed in to change notification settings - Fork 150
Closed
Description
What is the procedure to debug a boot loop on the C3? I am unable to get into debugger. This is using the new openocd that resets if needed to remove protection.
My exact case was two tasks, the second task was sometime calling into the first task before it had gotten everything initialized.That caused a NULL deference and rebooted the CPU. I've fixed this but it was difficult to locate the issue without a debugger.
If a C3 is stuck in a boot loop like this, why doesn't the debugger simply catch the fault and leave me sitting at the location that faulted? Then I'd have a nice call stack showing me what happened.