On Sun, Sep 6, 2009 at 7:06 PM, David Brownell<davi...@pacbell.net> wrote: > On Sunday 06 September 2009, Dirk Behme wrote: >> This was the first start of OpenOCD after cold reset of the board. > > Yours acted more politely than mine... > > >> Yes, with some further re-starts of OpenOCD without board reset, it >> behaves different. I can't say if this happens with your tck100.patch, >> too, though. So it seem to depend on OpenOCD/board reset status/history. > > The patch with the 100 clocks with TMS high (in JTAG reset) > seems more variable than the tck100 one with TMS low (idle), > though I've not done a proper A/B test yet. > > Public ICEpick docs are incomplete, but the ones I found > were not clear on whether the state mattered ... maybe the > issue is that it *does* matter somewhat, and clocking in > JTAG idle state is better.
If this is the case, then an event would be better than some fixed functionality. The beagleboard config could then define an event to push some buttons, scratch some backs and pull some strings to make the CPU work... -- Øyvind Harboe Embedded software and hardware consulting services http://www.zylin.com _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
