I just want to add that there is a tcl hook that gets called when gdb connects. Depending on how you use openocd/gdb, that one can be more convenient for doing a reset init than with monitor commands from within gdb.
As has been said already, openocd (and gdb) should do as little as possible to the target by default. Attaching to a running target for post-mortem analysis is very useful and a by-default reset, or even halt, really hampers this. I'd rather consider it a bug if there are targets that can't be attached to while running (if possible in the debug architecture). I remember fixing a bug of this kind for the STM32 target. SF list is broken, btw. Or is it just me? /Andreas
_______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
