1. 21 Apr, 2013 1 commit
  2. 20 Jan, 2013 1 commit
  3. 23 Dec, 2012 2 commits
  4. 04 Oct, 2012 1 commit
  5. 26 Sep, 2012 1 commit
  6. 07 Sep, 2012 2 commits
  7. 06 Sep, 2012 1 commit
  8. 29 Aug, 2012 2 commits
  9. 24 Aug, 2012 1 commit
  10. 02 Aug, 2012 2 commits
  11. 30 Jul, 2012 1 commit
  12. 17 Jul, 2012 1 commit
    • Andreas Fritiofson's avatar
      Add FTDI JTAG driver using MPSSE layer · f5e97b5e
      Andreas Fritiofson authored
      
      
      Based on ft2232.c but uses the MPSSE layer for low-level access, greatly
      simplifying the JTAG logic. Remove all libftdi/FTD2XX code and all layout
      specific code. Layout specifications are instead handled in Tcl.
      
      Use a signal abstraction to enable Tcl configuration files to define
      outputs for one or several FTDI GPIO. These outputs can then be
      controlled using the ftdi_set_signal command. Special signal names are
      reserved for nTRST, nSRST and LED (for blink) so that they, if defined,
      will be used for their customary purpose.
      
      Depending on the type of buffer attached to the FTDI GPIO, the outputs
      have to be controlled differently. In order to support tristateable
      signals such as nSRST, both a data GPIO and an output-enable GPIO can be
      specified for each signal. The following output buffer configurations are
      supported:
      
      * Push-pull with one FTDI output as (non-)inverted data line
      * Open drain with one FTDI output as (non-)inverted output-enable
      * Tristate with one FTDI output as (non-)inverted data line and another
        FTDI output as (non-)inverted output-enable
      * Unbuffered, using the FTDI GPIO as a tristate output directly by
        switching data and direction as necessary
      
      The data and output-enables are specified as 16-bit bitmasks,
      corresponding to the concatenation of the high and low FTDI GPIO
      registers. To specify an unbuffered output, use the same bitmask
      for both data and output-enable.
      
      The adapter configuration file must also specify default values for the
      FTDI data and direction GPIO registers, and the channel being used (if
      different from 0).
      
      Change-Id: I287a41d4c696cf5fc74eb10d5e63578b0dc7f826
      Signed-off-by: default avatarAndreas Fritiofson <andreas.fritiofson@gmail.com>
      Reviewed-on: http://openocd.zylin.com/452
      
      
      Tested-by: jenkins
      Reviewed-by: default avatarPeter Stuge <peter@stuge.se>
      f5e97b5e
  13. 21 May, 2012 1 commit
  14. 14 May, 2012 1 commit
  15. 30 Mar, 2012 1 commit
  16. 13 Mar, 2012 2 commits
  17. 03 Jan, 2012 1 commit
  18. 19 Dec, 2011 3 commits
  19. 12 Dec, 2011 1 commit
  20. 18 Nov, 2011 1 commit
    • Mauro Gamba's avatar
      libusb-1.0 support · b3023447
      Mauro Gamba authored
      
      
      The configuration script check for libusb-1.0 availability first and only
      if not found check for libusb-0. So if both libraries are installed on the
      system the build script will use libusb-1.0
      It's possible to force compiling with libusb-0 with the --enable-libusb0 switch.
      If the driver support only libusb0 the script check anly for it.
      
      Change-Id: I7eb045d4e2bd553abefad53f3f4023ff46b0f5f6
      Signed-off-by: default avatarMauro Gamba <maurillo71@gmail.com>
      Reviewed-on: http://openocd.zylin.com/33
      
      
      Tested-by: jenkins
      Reviewed-by: default avatarSpencer Oliver <spen@spen-soft.co.uk>
      b3023447
  21. 11 Oct, 2011 1 commit
  22. 30 Sep, 2011 1 commit
  23. 02 Sep, 2011 1 commit
  24. 16 Aug, 2011 3 commits
  25. 15 Aug, 2011 1 commit
  26. 09 Aug, 2011 2 commits
  27. 18 Jul, 2011 1 commit
  28. 12 Jul, 2011 1 commit
  29. 26 Jun, 2011 1 commit
  30. 13 Jun, 2011 1 commit