[<<][arm][>>][..]
Sun May 29 16:09:57 CEST 2011

OpenOCD bugs

I'm trying to get to a reliable workaround for all the bugs I run
into.  Up to now there hasn't been a simple pattern.  This is an
attempt to separate multiple bugs + their workaround.


* Error: address + size wrapped(0xffffffff, 0x00000004)

This is supposed to be a bug in GDB[1].  I have no reliable
workaround.

* Target not halted, starts running when left alone for a while
  (i.e. +- 1 hour)

Could be WDT?

It seems to be seriously messed up.  I can't fix it with just software.

Warn : srst pulls trst - can not reset into halted mode. Issuing halt after reset.
Error: Jazelle debug entry -- BROKEN!
Error: Jazelle state handling is BROKEN!
target state: halted
target halted in Jazelle state due to debug-request, current mode: Supervisor
cpsr: 0x61000013 pc: 0x00106a72
requesting target halt and executing a soft reset
Error: Jazelle state handling is BROKEN!
target state: halted
target halted in Jazelle state due to debug-request, current mode: Supervisor
cpsr: 0x610000d3 pc: 0x00000000
1000 kHz

There are 3 things to reset:
- target power
- programmer power
- OpenOCD

Assuming it's not the programmer, it should be possible for OpenOCD to
reset the chip, whatever the state it is in.  So assume the bug is
with OpenOCD and restart it.

When I reset just OpenOCD (not the board) I run into the other error:

GDB:     Cannot find bounds of current function
OpenOCD: Error: address + size wrapped(0xffffffff, 0x00000004)

Doing "reset" and "continue" a couple of times will eventually pull it
back in line.

Summary: I managed to reset it:
  - by re-starting OpenOCD
  - by fiddling a bit with GDB
  - did not touch target nor programmer power

That should be automatable.


[1] http://lists.berlios.de/pipermail/openocd-development/2009-February/004684.html



[Reply][About]
[<<][arm][>>][..]