4/19/2021 0 Comments Xilinx Digilent Usb Jtag Driver
If they are not in this directory (and have the right version), it simply skips the usb-stage and doesnt even try to find the jtag adapter, but prints the mentioned message about its script which will copy the files into the appropriate locations.I also updated my patch based one your one: It makes the digilent support optional and doesnt use the XILINX variable as it might not be set when this package is built.
It also properly installs the udev rules into usrlib instead of etc. I have tested this with a Platform Cable USB II and a virtex5. But as the package is called usb-drivers, it doesnt make much sense to include it. If not it prints a message that you should run it manually as root (Please run source.setuppcusb from the optXilinx14.7ISEDSISEbinlin64 directory with root privilege to update the firmware. Disconnect and then reconnect the cable from the USB port to complete the driver update.). Regarding your changes: I dont think that the digilent.adept.utilities 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. Adding my user to the uucp group didnt help unfortunately, even after a reboot it still complained that I should run setuppcusb (like mentioned above) and then just says Cable connection failed. Are you saying iMPACT runs setuppcusb That doesnt seem right. By the way, I think I originally got this stuff from When I got the USB-JTAG drivers working, I followed and used the udev modifications in this package. I originally modified the xilinx-ise PKGBUILD with the changes on that wiki page, like adding dependencies on fxload and digilent.adept.utilities and installing a plugin. I chose to fix up the udev rules with sed instead to keep it general. I finished the class that gave me access to the FPGA I was using, so Ill need you to test the new PKGBUILD for me before I upload it. Regarding your issues with root privileges, make sure you are a member of the uucp group as suggests. However it is not needed anyway in my case, the default libusb works fine. Strictly speaking xilinx-ise is currently a make dependency only, but I think it is better to make it an actual dependency by using the firmware files directly instead of copying them to usrshare (which is the wrong place anyway). I made a patch for all these changes: One strange thing I noticed: Impact refuses to recognize my adapter if the uid is not 0, which can either be achieved by using fakeroot or running as actual root (not recommended). Now the interesting thing is that it works without uid 0 on ubuntu 16.04.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |