I recover by resetting the target (in gdb I use “mon reset init”). The issue
there is that I lose any potential state of where the micro was when it froze
on me. So far in my experience restarting OpenOCD means that GDB is lost.
From: [email protected] [mailto:[email protected]] On Behalf Of
Andreas Fritiofson
Sent: Tuesday, October 14, 2014 3:33 PM
To: Borton, Nick
Cc: [email protected]
Subject: Re: [OpenOCD-devel] Help with K60 and a lost debug state
On Tue, Oct 14, 2014 at 6:14 PM, Borton, Nick
<[email protected]<mailto:[email protected]>> wrote:
Hello,
I’m debugging a custom board with a Freescale K60, and I’m running into a
problem I have never seen before with OpenOCD / GDB.
The K60 seems to be “freezing” under certain conditions in the lab, and when I
try to debug the problem, no exceptions seem to be hit. When I enter ^C in GDB
after it has frozen, OpenOCD times out trying to halt the target.
I am running OpenOCD 0.7.0, and I turn on vector_catch for all sources.
This is an infuriatingly vague question, any tips on what to try would be
helpful. Right now I’m dead in the water with no visibility.
How do you recover? Power cycle? Reset? Or just restart OpenOCD?
What does the OpenOCD console say around the timeout? Does any other operation
succeed (gdb is probably dead by then, use the telnet console).
If you simply restart OpenOCD, does it successfully examine the target?
(assuming your config does not reset on startup, if it does, try to avoid that
as a test)
An equally vague response...
/Andreas
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
