Xilinx Platform Cable Usb Ii Firmware Loader Windows 10
Gifford Brickley
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.
Note: for me after flashing the experimental Jed I experienced instability which was known at the time, (it was an experimental Jed after all), so I just flashed the original Jed back and the instability disappeared. Iirc instability included crashing in the loader, erratic menu behaviour and corrupted menu characters, some files crashing on loading.
I have a JTAG SMT2 and have made the cable; however ISE will not install on any of my Windows machines (various complaints about virtualization, which _is_ turned on in the BIOS). Vivado will not support them. Going to fire up a Raspberry Pi tomorrow and use _firmware_upgrade_using_a_Raspberry_Pi - I have flashed Xilinx CPLD successfuly with this method.
I have been pretty sick - not covid but not far from it. I dug out the Pi 4 and installed Buster, xc3sprog is working as expected not failing with permissions issues immediately but it not yet detecting the JTAG chain, I likely have an error in my cable. When I am better I will get back to it.
All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its affiliates, the authors nor the translators shall be held liable for possible errors or the consequences thereof.
Many commands are also described in their manual pages. To view them, run man, followed by a specific command name. If the man command is not installed on your system, install it with sudo zypper install man.
To simplify this process, click the Report an issue icon next to a headline in the HTML version of this document. This preselects the right product and category in Bugzilla and adds a link to the current section. You can start typing your bug report right away.
To contribute to this documentation, click the Edit source document icon next to a headline in the HTML version of this document. This will take you to the source code on GitHub, where you can open a pull request.
You can also report errors and send feedback concerning the documentation to . Include the document title, the product version, and the publication date of the document. Additionally, include the relevant section number and title (or provide the URL) and provide a concise description of the problem.
Commands can be split into two or multiple lines by a backslash character (\) at the end of a line. The backslash informs the shell that the command invocation will continue after the end of the line:
Problem determination, which means technical support designed to provide compatibility information, usage support, ongoing maintenance, information gathering and basic troubleshooting using available documentation.
Problem isolation, which means technical support designed to analyze data, reproduce customer problems, isolate a problem area and provide a resolution for problems not resolved by Level 1 or prepare for Level 3.
Technology previews are packages, stacks, or features delivered by SUSE to provide glimpses into upcoming innovations. Technology previews are included for your convenience to give you a chance to test new technologies within your environment. We would appreciate your feedback. If you test a technology preview, please contact your SUSE representative and let them know about your experience and use cases. Your input is helpful for future development.
d3342ee215