summaryrefslogtreecommitdiff
path: root/testing/examples
diff options
context:
space:
mode:
authorDavid Brownell <dbrownell@users.sourceforge.net>2009-10-20 20:04:36 -0700
committerDavid Brownell <dbrownell@users.sourceforge.net>2009-10-20 20:04:36 -0700
commit7556a93aed97c3fad2c0a904a115168cd3dd61a8 (patch)
tree9ec8b3587676945e34181671fdbb4b8eb0c70344 /testing/examples
parenta1609e5ad1b8df67f216d2f7c43db82c420db373 (diff)
downloadopenocd+libswd-7556a93aed97c3fad2c0a904a115168cd3dd61a8.tar.gz
openocd+libswd-7556a93aed97c3fad2c0a904a115168cd3dd61a8.tar.bz2
openocd+libswd-7556a93aed97c3fad2c0a904a115168cd3dd61a8.tar.xz
openocd+libswd-7556a93aed97c3fad2c0a904a115168cd3dd61a8.zip
XSVF: use svf_add_statemove()
XSVF improvements: - Layer parts of XSVF directly over SVF, calling svf_add_statemove() instead of expecting jtag_add_statemove() to conform to the SVF/XSVF requirements (which it doesn't). This should improve XSTATE handling a lot; it removes most users of jtag_add_statemove(), and the comments about how it should really do what svf_add_statemove() does. - Update XSTATE logic to be a closer match to the XSVF spec. The main open issue here is (still) that this implementation doesn't know how to build and submit paths from single-state transitions ... but now it will report that error case. - Update the User's Guide to mention the two utility scripts for working with XSVF, and to mention the five extension opcodes. Handling of state transition paths is, overall, still a mess. I think they should all be specified as paths not unlike SVF uses, and compiled to the bitstrings later ... so that we can actually make sense of the paths. (And see the extra clocks, detours through RUN, etc.) Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Diffstat (limited to 'testing/examples')
0 files changed, 0 insertions, 0 deletions