Xilinx Digilent Usb Jtag Driver
Joao Charlesbois
Is there anybody have any experience about XUP (Xilinx University Program) USB-JTAG Programmer Revision-G using with Vivado 2015 or 2018? I have some little experience with Vivado 2015.5 and 2018.1 but regarding my experiences XUP USB-JTAG Programmer is not compatible with Vivado? I tried all ways on Centos-7 OS and the particular script (install_drivers.tar.gz). I aimed to program the Zedboard for petalinux applications developing but no success with XUP USB-JTAG Rev.G and Vivado running on Centos-7. Could you please share any suggestions if you have?
I checked back email chain with the previously mentioned engineer and found that the Xilinx install script does not work correctly. This is for Vivado 2017.4, but presuming 2018.2 is set up similarlly, I would try the following (quoted from the engineer in question):
Both @JColvin and our design engineer that we had reached out to about this thread are out of the office until later next week and the following week respectively. It will be a little bit of time until we are able to respond.
My exact question is that now i can connect via directly to FPGA without xup digilent jtag programmer on zedboard, centos vm, virtualbox and vivado 2018.1 But i couldn't connect with xup digilent jtag programmer on same parameters and conditions. I am suspecting vivado 2018.1 is not supporting Digilent Inc. XUP (Xilinx University Program) JTAG debugger-programmer? Am i right or wrong on my suspicious?
The problem is that the Xilinx installer for the cable drivers (at least for Windows 10) does not work correctly, so those drivers needed to be deleted and manually installed in order to work correctly. On Linux based systems the cable drivers are not installed automatically so you have to manually install them yourself through a series of commands (as described in Xilinx's UG973).
If you have already done those steps, we (Digilent) do not have any other advice as to what you can try aside since we do not offer any formal support for getting devices to work in vitual machines; the engineer I mentioned before only happened to try VMware since they already had it installed and it worked for them when they followed the installation instructions from Xilinx documentation.
I tried with fedora 20 64 bit and ISE-DS 14.6 version. Everything was fine for zedboard and also additionally NetFPGA-1G-CML boards. I still think Digilent XUP debugger is not compliant for Vivado 2018.1. Could you please share any screenshots about installation drivers or running xup debugger? So i have for ISE-DS impact 14.6.
You mentioned that on 28 June e-mail subject of "XUP USB-JTAG Programmer" on digilent forum "Our engineer was able to get the XUP cable recognized and working on a Centos 7 64-bit VM with Vivado 2018.1 without much issue." Could you please share more detail about the virtualization infrastructure for example VirtualBox or vmware? If vbox did this engineer install the virtualbox extension-pack for USB2.0 drivers recognizing?
Today I tried to replicate the setup in my CentOS 7 Virtual Machine running on my Windows 10 host and Vivado 2018.1 didn't initially find XUP JTAG Cable. In my attempts to debug this I disconnected the cable from the virtual machine and opened Vivado 2018.1 in Windows 10 and proceeded to see if it could be found. Much to my surprise, Vivado could not find it. I then opened the device manager and discovered that in Windows the XUP USB JTAG Cable was showing up as "Xilinx Embedded Platform USB Firmware Loader", which is effectively a bootloader firmware that's used to download the real firmware image. When the driver is properly installed in Windows 10 the OS should initially detect that the device does not have the application firmware programmed, programm it, and then re-enumerate it on the bus. To get Windows to do this I had to do the following:
Here we can see that there is no call to fxload and there are no pathnames specified for the firmware images. I suspect that if you want to get this to work seamlessly then you will need to install impact and the cable drivers that impact includes. However, I cannot gaurantee that will work either. Since you are running a Windows host you could just do the same thing that works for me, which is installing the Windows drivers and letting Windows download the firmware to the XUP JTAG cable before you connect it to your Linux VM.
Thanks,
Michael
You are the one and you are the wonderful guy for me. Many thanks for your kindly answer. It works!!! I don't have any vivado installation on my host windows-7 so i don't want to install. When i connect the Xilinx XUP-USB debugger to Centos-7 vm and the solution was editing the /etc/udev/rules.d/52-xilinx-pcusb.rules file like below;
My last question is in vivade hardware manager GUI i couldn't see the flash programming option with an *.mcs file? But impact has this feature? How can i program my zedboard's flash memory with Vivado 2018.1 hardware manager via Xilinx XUP-USB JTAG debugger/programmer? So now it's working. :)
I'm glad to here you are able to see your board through the XUP-USB through the VM. My understanding is that the .mcs file process for configuring the flash has been deprecated. The .bin file is used to program flash. For the Zedboard you will need to create a boot.bin file in SDK. Here is the Zedboard Programming Guide which is an older tutorial for doing this with the Zedboard.
Everything is fine from my side. I would share last point of my problem that the failure been regarding with xusb_xup.hex firmware file. The file which is coming with Vivado 2018.1 is not properly running but (I know hearing this is strange) the one which was coming with ISE-DS-14.6 is properly running on my host Windows 7.
My last question is in vivade hardware manager GUI i couldn't see the flash programming option with an *.mcs file? But impact has this feature? How can i program my zedboard's flash memory with Vivado 2018.1 hardware manager via Xilinx XUP-USB JTAG debugger/programmer? So now it's working.
Our engineer was able to get the XUP cable recognized and working on a Centos 7 64-bit VM with Vivado 2018.1 without much issue. The main thing that they did (detailed in the Installing Cable Drivers section of Xilinx UG973) and went to their install_install drivers directory (../data/xicom/cable_drivers/lin64/install_script/install_drivers) and executed the ./install_drivers script as sudo. They were then able to run Vivado and use the hardware manager as normal to connect to the cable and have Vivado 2018.1 successfully auto-connect to the XUP USB JTAG cable and the downstream Zedboard.
I have installed the Xilinx ISE webpack 14.7 on my arch system. The software works and the license was
accepted.
Now in order to communicate with the spartan 3e board from digilent one has to manually install the proper
driver. I followed the arch wiki ISE in order to get things working. This means I installed fxload and from the AUR I installed:
usbdrv
adept-runtime 2.16.1-1
libftd2xx 1.1.12-2
My problem is that I still cannot communicate with the device. There is a little diode that should light up once
the board has been properly set up in the OS but this doesn't happen. Would anyone know into which direction
I should go to make it work?
And what exactly did you try and at what point it fails? When you run impact, click on Boundary Scan and then on Initialize Chain and look at the output in the Console window. You should see some output of the Digilent Plugin there.
Thank you, I installed the driver from the repository you mentioned. Unfortunately the repo hasn't been updated in a while and
I get an error message while running make. However, I installed the precompiled version and this seems to work (i.e. the LED
lights up)...
But now I perform a boundary scan under iMPACT and the board is not found. On the following page it is said
that ISE 13.2 crashes every time (I use ISE 14.7). Does this happen to you?
make runs fine here. Maybe some package is missing. But looking into the index.html file building is unnecessary anyway since ISE includes a driver itself. So in theorey it should just work now. You could try running impact as root to see if it is a problem with permissions. But the installed udev rule should set it to 666...
Are you running your setup directly on your PC or in a virtual machine using usb passthrough? Just asking because the device changes its id when the firmware is loaded so if used inside of a VM the device has to be passed to the VM again.
ML505 board does not use Digilent JTAB Download Cable solution but uses the old xilinx JTAG cable driver.
However, I believe that the xilinx always has trouble with their drivers.
Here is the solution:
1. If the libdabs.so is not found, please check the attributes of libdabs.so.2.
In some Ubuntu OS, when a copy is performed from a NTFS disk to EXT disk,
read/write attributes may get messed up.
Make sure that the file libdabs.so.2 is readable.
Once the dynamic loader configuration file has been installed it is
necessary to have the dynamic loader update its cache. The following
command, when executed with superuser privileges, can be used to force
the cache to be updated.
I installed Adept on Fedora16. There is an apparent incompatibility with libusb1 : crash occurs in this library. Adept works fine on f15, f14, etc. The difference is that f16 uses libusb1 version 1.0.9 and f14 uses 1.0.8.
I recently switch to Linux Kernel 4.4 (from 4.0) for some of my projects and to my no surprise found Xilinx AXI-DMA not working again. This time it complained that it can't find DMA channel: "unable to read dma-channels property" and as result "Probing channels failed." So, looks like Xilinx added support for "multi-channel mode" for kernel driver and this is a big deal! And I waited for this forever!
7fc3f7cf58