On Wed, Oct 21, 2009 at 10:39 AM, David Brownell <[email protected]> wrote: > On Wednesday 21 October 2009, Řyvind Harboe wrote: >> > Notice how even the new "short" paths are in most cases longer >> > than they need to be... >> >> The "short" paths should essentially make endstate + pathmove >> unambiguous. >> >> So short should be "shortest". > > They're not. I don't think that's a fix-for-0.3.x issue > though. > > >> Are there any shortest paths that are ambiguous? > > I don't understand what you mean by "ambiguous"; > at any TCK edge, TMS will have only one value so > only one state will be entered.
There are many ways to get from A to B. The "shortest" from A to B is, presumably unambiguous so one can then use endstate + pathmove to get a predictable behavior. -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
