* ChipScope 9.1.03i
* ChipScope 9.1.02i
* ChipScope 8.2.04i
+ * EDK 9.1.02i
+ * EDK 9.1.01i
* EDK 8.2.02i
* EDK 8.1.02i
+ * Synplicity Identify
In addition to the XILINX USB and parallel cables, devices based on the FTDI
2232 serial converter chip are also experimentally supported. This includes
devices like the Amontec JTAGkey(-Tiny).
-Build the library by calling `make'.
+Build the library by calling `make'. If you are on a 64 bit system but want
+to build a 32 bit library, run `make lib32' instead.
To use this library you have to preload the library before starting impact:
$ impact
The source for this library can be found at:
-http://cvs.zerfleddert.de/cgi-bin/viewcvs.cgi/usb-driver/
+http://git.zerfleddert.de/cgi-bin/gitweb.cgi/usb-driver
The main website is located at:
http://www.rmdir.de/~michael/xilinx/
+The Git repository can be cloned with:
+git clone git://git.zerfleddert.de/usb-driver
+
Notes for the USB cable
=======================
~~~~~~~~~
2. Copy the sample libusb-driverrc to ~/.libusb-driverrc, edit it and replace
- the vendor and product-id in the example file with the values from provided
- in the lsusb-output. You can also change the 'parallel port' which is mapped
- to this cable. Impact sees the device at that port as a Parallel Cable III.
+ the vendor and product-id in the example file with the values provided in
+ the lsusb-output. You can also change the 'parallel port' which is mapped to
+ this cable. Impact sees the device at that port as a Parallel Cable III.
3. To use the device as an ordinary user, put the following line in a new file
in /etc/udev/rules.d/ and restart udev:
(replace the vendor and product id with your values)
The support for FTDI 2232 based devices is experimental and they are currently
-significantly slowen than the other supported cables.
+significantly slower than the other supported cables.