On Mon, Jun 1, 2009 at 11:39 AM, Magnus Lundin <lun...@mlu.mine.nu> wrote: > I propose some changes to the jtag subsystem > > - Add jtag_add_statmove( endstate ) call, the code is already in > jtag_add_tlr()
Could you write the documentation for this fn as a separate proposal? You are here talking about the application code communicating to the driver that somehow the JTAG state machine state has changed "behind the scenes"...? I don't understand the motivation for allowing access to this fn, but I vaguely recall that something was written about this on the list recently. Post 0.2? Or are you talking about something along the lines of xsvf_add_statemove() in xsvf.c? > - Implement jtag_add_tlr() as > jtag_add_statemovet(TAP_RESET) > jtag_stableclocks(6) /* I am not 100% sure about this here */ Why? > - Make sure that JTAG_STABLECLOCKS is implemented in all drivers (we > will soon fingd out otherwise ) Don't we already have this in jtag_add_clocks()? Another thing I'd like first is to see if we can retire jtag_add_end_state(), as this would effectively make removing jtag_add_runtest() that little bit easier... -- Øyvind Harboe Embedded software and hardware consulting services http://consulting.zylin.com _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
