Showing results for 
Show  only  | Search instead for 
Did you mean: 
Registered: ‎10-11-2018

Digilent JTAG-HS3 not recognized XSDK 2017.2 on Linux

I am running two different virtual machines, one Ubuntu 18.04 LTS under VMware running Vivado 2017.2 and another running Ubuntu 16.04 LTS and Vivado 2015.4.  I can program FPGA / JTAG debugging with the Digilent HS3 using XSDK 15.4.  Running the same hardware running the second VM with XSDK 17.2, it does not find the JTAG.  The debugger does not discover the JTAG device on Vivado 17.2 the way it does on Vivado 15.4.  In both cases the cable drivers say they are loaded, and the HS3 driver appears to be recognized in dmesg.  So I know that the JTAG is wired correctly as it works in the first VM.  However, the new development must be on the second VM.

Please note that I can access the JTAG under Windows using XSDK 2017.2.  However, I need to develop under Ubuntu and transferring to Windows for debugging is very time consuming!

The board is the MicroZed 7020.  The configurations of both machines appears substantially the same.  What is the problem?  How to diagnose?

Ubuntu 18.04 / Vivado 2017.2

ls -al /etc/udev/rules.d
total 88
drwxr-xr-x 2 root  root   4096 Jan 21 14:46 .
drwxr-xr-x 4 root  root   4096 Jan 11 09:49 ..
-rw-r--r-- 1 root  root   3848 Oct  4 19:23 52-digilent-usb.rules
-rw-r--r-- 1 root  root   3797 Oct 18 17:53 52-xilinx-digilent-usb.rules
-rw-r--r-- 1 devel devel  3301 Jun 13  2017 52-xilinx-ftdi-usb.rules
-rw-r--r-- 1 devel devel   435 Jun 13  2017 52-xilinx-pcusb.rules
-rw-r--r-- 1 root  root  58549 Jul 27 11:44 70-snap.core.rules
-rw-r--r-- 1 root  root    341 Jan 14 17:25 99-vmware-scsi-udev.rules


devel@ubuntu-taa:~$ lsusb

Bus 001 Device 003: ID 0403:6014 Future Technology Devices International, Ltd FT232H Single HS USB-UART/FIFO IC

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 002 Device 004: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light

Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub

Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse

Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub




0 Kudos
1 Reply
Xilinx Employee
Xilinx Employee
Registered: ‎10-06-2016

Hi @talbertin

Is the issue present both in Vivado and XSDK? I mean you can check if Vivado Hardware Manager is able to detect the cable and target to discard XSDK specific issues to focus on the cable drivers only.


Don’t forget to reply, kudo, and accept as solution.
0 Kudos