When I got the USB-JTAG drivers working, I followed and used the udev modifications in this package. By the way, I think I originally got this stuff from Namely, install the udev files into the correct locations. This package is intended to do what setup_pcusb does. I removed the usb-driver source.Īre you saying iMPACT runs setup_pcusb? That doesn't seem right. Yea, I'm OK with not adding support for parallel ports. I tried changing its group to uucp and/or using the libusb from Michael Gernoth () instead of libusb-compat, but neither combination worked. This is really strange as the usb device in /dev is owned by root:root and made world-writable by the first udev rule. One thing that is still missing is a dependecy on libusb-compat, which I did not notice before as it was already installed.Īdding my user to the uucp group didn't help unfortunately, even after a reboot it still complained that I should run setup_pcusb (like mentioned above) and then just says 'Cable connection failed'. Regarding your changes: I don't think that the dependency and the copied plugin should be included in this package, as this is not required for platform-cable-compatible jtag adapters like in my case. Disconnect and then reconnect the cable from the USB port to complete the driver update.'). setup_pcusb` from the /opt/Xilinx/14.7/ISE_DS/ISE//bin/lin64 directory with root privilege to update the firmware. If not it prints a message that you should run it manually as root ('Please run `source.

Yes, Impact always runs its setup_pcusb when it is uid 0. But as the package is called usb-drivers, it doesn't make much sense to include it. Ah, right, I did not think about the parallel port.

Digilent usb jtag cable driver linux