Is there any particular reason to compile your own libusb instead of using the distribution packages?
To make the Xilinx JTAG cable working in the RHEL/CentOS/SL 6.x do the following stops. There is detailed description on my website
formatting link
but unfortunately it is in Czech language only. Sorry.
Install and "fix" libusb:
yum install libusb libusb1 fxload cd /usr/lib64 (or /usr/lib if you are running 32b system) ln -s libusb-1.0.so.0.0.0 libusb.so
"Fix" the Xilinx cable setup script /ISE_DS/ISE/bin/lin64/setup_pcusb (or the same path with lin instead of lin64) which does not detect udev correctly:
cd /ISE_DS/ISE/bin/lin64/setup_pcusb (or lin instead of lin64) ./setup_pcusb
Generated udev rule uses wrong syntax. The rule for current version of udev /etc/udev/rules.d/xusbdfwu.rules must look like this (long lines must be retained, see my website for proper formatting):
Thanks for the tutorial. Im attempting to do the same thing with SL6.1/CentOS6/RHEL6 and the Xilinx 10.1.03 tools with no success. After I configure everything as you prescribe when I run impact and try to read the jtag chain it bombs and says "Module windrvr6 is not loaded. Please reinstall the cable drivers". Your solution should bypass the windrvr6 module correct? Any idea why it would still be looking for it?
Thanks, Nat
--------------------------------------- Posted through
Xilinx ISE version 10 uses the windrvr6 module by default. You have to set the XIL_IMPACT_USE_LIBUSB environment variable to force the tools to use the libusb. See
ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.