Skip to content
Snippets Groups Projects
  1. Nov 13, 2009
  2. Nov 11, 2009
    • Zachary T Welch's avatar
      add const keyword to some APIs · ca594adb
      Zachary T Welch authored
      Add 'const' keyword to 'char *' parameters to allow command handlers to
      pass constant string arguments.  These changes allow the 'args' command
      handler to be changed to 'const' in a subsequent patch.
      ca594adb
  3. Nov 10, 2009
  4. Nov 09, 2009
  5. Oct 29, 2009
    • David Brownell's avatar
      XSVF: bugfix handling state paths · 0c4d5b8b
      David Brownell authored
      
      Implement XSVF support for detailed state path transitions,
      by collecting sequences of XSTATE transitions into paths
      and then calling pathmove().
      
      It seems that the Xilinx tools want to force state-by-state
      transitions instead of relying on the standardized SVF paths.
      Like maybe there are XSVF tools not implementing SVF paths,
      which are all that we support using svf_statemove().
      
      So from IRPAUSE, instead of just issuing "XSTATE DRPAUSE"
      they will issue XSTATES for each intermediate state: first
      IREXIT2, then IRUPDATE, DRSELECT, DRCAPTURE, DREXIT1, and
      finally DRPAUSE.  This works now.
      
      Handling of paths that go *through* reset is a trifle dodgey,
      but it should be safe.
      
      Tested-by: default avatarWookey <wookey@wookware.org>
      
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      0c4d5b8b
  6. Oct 21, 2009
    • David Brownell's avatar
      XSVF: use svf_add_statemove() · 7556a93a
      David Brownell authored
      
      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: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      7556a93a
  7. Oct 20, 2009
  8. Jul 17, 2009
  9. Jun 23, 2009
  10. Jun 18, 2009
  11. Jun 09, 2009
  12. Jun 05, 2009
  13. Jun 04, 2009
  14. Jun 03, 2009
  15. Jun 01, 2009
  16. May 23, 2009
  17. May 22, 2009
  18. May 12, 2009
  19. May 11, 2009
  20. May 10, 2009
  21. May 08, 2009
  22. May 06, 2009
Loading