On Wed, Aug 19, 2009 at 9:10 PM, Wookey<[email protected]> wrote: > +++ Øyvind Harboe [2009-07-21 22:56 +0200]: >> On Tue, Jul 21, 2009 at 3:07 PM, Wookey<[email protected]> wrote: >> > +++ David Brownell [2009-07-20 15:53 -0700]: >> >> On Monday 20 July 2009, Wookey wrote: >> >> > Error: BUG: TAP path doesn't finish in a stable state >> > >> >> Looks like r1980 creating jtag_add_statemove() from the XSVF-specific >> >> code might have seeded this problem ... if later changes to the >> >> statemove() >> >> logic turned some things into errors. Do r1979 and r1980 behave, or was >> >> it already incompatible then? >> > >> > OK. I tried HEAD (r2551) and that is the same as debian's 0.2.0+r2529-1 >> > in this regard. >> > >> > Tried to build r1979 but there appears to be something wrong with the >> > autofoo because it doesn't build a libopenocd shared library and thus >> > doesn't work. I ran out of time trying to work out what was amiss. >> >> Just a thought: did you try --disable-shared? > > Thanx very much - that lets it build, and allows me to find that > PLAYXSVF is still broken (as is the xscale/ path to find debug_handler).
The xscale path is a known problem and is described in the todo list. It just needs someone to do the legwork in the automake files. Meanwhile you can use the -s(???) to add the right search path. > both these problems are not present in r1609, so I see a long binary chop > process ahead where I look for likely relevant changes between those > versions. Clues welcome. For a thousand revisions you need 10 chops best case... if you can divide it a few times that would help *Greatly*. > > Wookey > -- > Principal hats: iEndian - Balloonboard - Toby Churchill - Emdebian > http://wookware.org/ > _______________________________________________ > Openocd-development mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/openocd-development > -- Øyvind Harboe Embedded software and hardware consulting services http://www.zylin.com _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
