On Monday 20 July 2009, Wookey wrote: > Error: BUG: TAP path doesn't finish in a stable state
I'd have thought that was a requirememnt for (X)SVF... it's hard to decrypt the binary XSVF, so I'll just note the theory that for some reason the Xilinx tools don't generate output conforming to their published spec (as something to confirm or disprove). > Error: XSTATE IRUPDATE is not reachable from current state IRPAUSE in one > clock cycle > Error: XSTATE DRSELECT is not reachable from current state IRPAUSE in one > clock cycle > Error: XSTATE DRCAPTURE is not reachable from current state IRPAUSE in one > clock cycle > Error: XSTATE DREXIT1 is not reachable from current state IRPAUSE in one > clock cycle Those are all true. > Error: BUG: TAP path doesn't finish in a stable state > Error: XSTATE DRUPDATE is not reachable from current state DRPAUSE in one > clock cycle Ditto. > Error: BUG: TAP path doesn't finish in a stable state > Error: XSTATE DRCAPTURE is not reachable from current state RUN/IDLE in one > clock cycle > Error: XSTATE DREXIT1 is not reachable from current state RUN/IDLE in one > clock cycle Ditto. 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? - Dave _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
