On Tuesday 09 June 2009, Øyvind Harboe wrote: > > And the only event of interest seems to be transitioning > > from a "running" or "debug-running" state ... to something > > else. With the only listeners being the TCL shell, or in > > some cases GDB (when a breakpoint or watchpoint fires). > > There are other events: > > - the target can send messages via DCC > - power outage(which drivers can detect if they support it) > - srst assert/deassert detection. srst can be asserted by > other devices than JTAG, e.g. the CPU itself.
Good info. I'll supply a doc update to highlight and explain this polling activity ... I think I have good answers for my questions now. :) Same update will make "poll" output say if the periodic polling is active. There are also various JTAG connector standards which support GPIO-ish event channels (potentially bidirectional). Atmel's Nexus connectors include event in and out signals. TI uses EMU0 and EMU1 ... and on some connectors I think EMU2..EMU5. And I think I've seen this on other hardware too. Sometimes that seems to be called "instrumentation support", with some of the signals used to flag e.g. "trace buffer has overflowed" or whatever else might merit immediate debugger attention. _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
