add link to instructions for Ubuntu in VMware by Sven Andersson
[usb-driver] / README
CommitLineData
54357994 1This library emulates Jungo Windrvr USB and parallel port functions in
2userspace which are required by XILINX impact to access the Platform cable USB
3and Parallel Cable III.
4With this library it is possible to access the cables without loading a
5proprietary kernel module which breaks with every new kernel release. It uses
6f766a61 6the functionality provided by the libusb userspace library for USB access and
54357994 7the kernel interface at /dev/parport0 for parallel port access instead and
8should work on every kernel version which is supported by libusb and supports
9ppdev. It was written against impact from ISE Webpack 9.1SP1 and tested with
10the following software:
0b50c513 11
7824bbf6 12 * ISE Webpack 9.1SP3
0b50c513 13 * ISE Webpack 9.1SP2
14 * ISE Webpack 9.1SP1
54fc4508 15 * ISE Webpack 8.2SP3
0b50c513 16 * ISE Webpack 8.1SP3
3b1b5fa8 17 * ChipScope 9.1.03i
0b50c513 18 * ChipScope 9.1.02i
3b1b5fa8 19 * ChipScope 8.2.04i
b8b5059a 20 * EDK 9.1.02i
2c6ade7a 21 * EDK 9.1.01i
54fc4508 22 * EDK 8.2.02i
5649925c 23 * EDK 8.1.02i
337944d1 24 * Synplicity Identify
113af964 25
7606d470 26In addition to the XILINX USB and parallel cables, devices based on the FTDI
272232 serial converter chip are also experimentally supported. This includes
28devices like the Amontec JTAGkey(-Tiny).
29
b8b5059a
MG
30Build the library by calling `make'. If you are on a 64 bit system but want
31to build a 32 bit library, run `make lib32' instead.
113af964 32
33To use this library you have to preload the library before starting impact:
34
35$ LD_PRELOAD=/path/to/libusb-driver.so impact
36or
37$ export LD_PRELOAD=/path/to/libusb-driver.so (for sh shells)
38$ setenv LD_PRELOAD /path/to/libusb-driver.so (for csh shells)
39$ impact
fdd05738 40
45b9b80b 41The source for this library can be found at:
badd6a82 42http://git.zerfleddert.de/cgi-bin/gitweb.cgi/usb-driver
45b9b80b 43
32e2af23 44The main website is located at:
45http://www.rmdir.de/~michael/xilinx/
46
b22eea29
MG
47The Git repository can be cloned with:
48git clone git://git.zerfleddert.de/usb-driver
49
54357994 50
51Notes for the USB cable
52=======================
53
54To use the device as an ordinary user, put the following line in a new
fdd05738 55file in /etc/udev/rules.d/ and restart udev:
56ACTION=="add", BUS=="usb", SYSFS{idVendor}=="03fd", MODE="666"
979132fe 57
58
59If your cable does not have the ID 03fd:0008 in the output of lsusb,
60the initial firmware has not been loaded (loading it changes the
61product-ID from another value to 8). To load the firmware follow
62these steps:
63
c2e95a30 641. If you have no /etc/udev/rules.d/xusbdfwu.rules file, copy it from
65 /path/to/ISE/bin/lin/xusbdfwu.rules to /etc/udev/rules.d/xusbdfwu.rules
979132fe 66
672. Install the package containing /sbin/fxload from your linux distribution.
68 It is usually called "fxload"
69
703. copy the file /path/to/ISE/bin/lin/xusbdfwu.hex to /usr/share/xusbdfwu.hex
71
724. restart udev and re-plug the cable
54357994 73
74
75Notes for the parallel cable
76============================
77
78To access the parallel port from userspace, the kernel needs to be built with
79the features "Parallel port support" (CONFIG_PARPORT), "PC-style hardware"
80(CONFIG_PARPORT_PC) and "Support for user-space parallel port device drivers"
81(CONFIG_PPDEV) builtin or as modules. If these features are built as modules,
82they need to be loaded before using this library.
83These modules are called:
84parport
85parport_pc
86ppdev
87
88
89To use the device as an ordinary user, put the user in the group 'lp'
6f766a61 90
91
cdc9c5bf 92If you have an almost compatible cable which works with other software but not
05e1bfcd 93with Impact, try adding -DFORCE_PC3_IDENT to the CFLAGS line in the Makefile.
94This enables a hack by Stefan Ziegenbalg to force detection of a parallel cable.
cdc9c5bf 95
96
6f766a61 97Parallel Cable IV is currently only supported in 'compatibility mode', as no
98attempt to configure the ECP registers is done by this library.
0c71f276 99
100
101If you get "Programming failed" or "DONE did not go high" when programming
102through the parallel cable with Impact 9.1, make sure to have the option "Use
103HIGHZ instead of BYPASS" enabled in Edit -> Preferences -> iMPACT Configuration
104Preferences.
105If you are using batch mode, add the following line to your cmd file:
106setPreference -pref UseHighz:TRUE
7606d470 107(This problem also occurs on windows and when using the real windrvr in linux
108and is solved with the same workaround. Impact 8.2 is working fine with the same
0c71f276 109boards and designs)
7606d470 110
111
112Notes for FTDI 2232 based cables
113================================
114
115To build the driver with FTDI 2232 support, you need to have libftdi and
116the libftdi development package installed. On debian, you can install both
117by installing 'libftdi-dev'.
118
119To set-up the device:
1201. Find out the vendor and product id of your cable using lsusb:
121 Bus 003 Device 005: ID 0403:cff8 Future Technology Devices ...
122 ~~~~~~~~~
123
1242. Copy the sample libusb-driverrc to ~/.libusb-driverrc, edit it and replace
19020bc5 125 the vendor and product-id in the example file with the values provided in
126 the lsusb-output. You can also change the 'parallel port' which is mapped to
127 this cable. Impact sees the device at that port as a Parallel Cable III.
7606d470 128
1293. To use the device as an ordinary user, put the following line in a new file
130 in /etc/udev/rules.d/ and restart udev:
131 ACTION=="add", BUS=="usb", SYSFS{idVendor}=="0403", SYSFS{idProduct}=="cff8", MODE="666"
132 (replace the vendor and product id with your values)
133
dc587d11 134The support for FTDI 2232 based devices is experimental and they are currently
1830118e 135significantly slower than the other supported cables.
Impressum, Datenschutz