AnsweredAssumed Answered

GDB / OpenOCD unable to halt K60 target

Question asked by Nick Borton on Oct 17, 2014
Latest reply on Oct 17, 2014 by Nick Borton



I have been developing with GDB + OpenOCD on K60s for a couple of years, and this is the first time I've had a time where OpenOCD and GDB were unable to halt the micro. The device is going off into some odd and unresponsive state (it is not even blinking its LED anymore). No exceptions are being caught, and the device is not resetting. When it gets into this state, I attempt to ^C in GDB to see where in the code it is. OpenOCD responds with the following:

Info : Halt timed out, wake up GDB.

Warn : target not halted

Warn : target not halted


Has anyone encountered this before? JTAG is not broken, since I can reset the device with a NVIC SYSRESETREQ, as opposed the the SRST line from the pod.