UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
167 Views
Registered: ‎05-21-2019

Xilinx JTAG Fails to Connect to Digilent Programmer

Jump to solution

Recently I've installed Vivado 2019.1 64-bit Hardware Server for Linux and I've been unable to get the hardware server to work with our Digilient Programmer.

Any help to resolve this would be appreciated.

John Shield


###############################

Vivado produces:

INFO: [Labtools 27-2285] Connecting to hw_server url TCP:192.168.40.5:3121
ERROR: [Labtoolstcl 44-494] There is no active target available for server at 192.168.40.5:3121.
Targets(s) ", jsn-JTAG-HS3-210299A55FF7" may be locked by another hw_server.

The hardware server produces:

TCF 11:07:49.551: jtagpoll: cannot open port Digilent/210299A55FF7: sync failed: got 0: aa 87 iteration 1

TCF 11:07:51.613: jtagpoll: cannot open port Digilent/210299A55FF7: sync failed: got 0: aa 87 iteration 1

TCF 11:07:53.677: jtagpoll: cannot open port Digilent/210299A55FF7: sync failed: got 0: aa 87 iteration 1

TCF 11:07:55.741: jtagpoll: cannot open port Digilent/210299A55FF7: sync failed: got 0: aa 87 iteration 1

xsdb debug shows:

[root@hardware-server bin]# ./xsdb

****** Xilinx System Debugger (XSDB) v2019.1
**** Build date : May 24 2019-15:06:52
** Copyright 1986-2018 Xilinx, Inc. All Rights Reserved.


Got $RDI_APPROOT: /tools/Xilinx/HWSRVR/2019.1
xsdb% connect -host localhost
tcfchan#0
xsdb% jtag targets
1 Digilent JTAG-HS3 210299A55FF7 (closed)

lsusb shows: (Device 003 is the USB JTAG programmer.)

[root@hardware-server install_drivers]# 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 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
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

Programmer is working:

The programmer was tested to work on Vivado 2017.1 on Windows 7.

Driver Install Output (ug973 pp24):

[root@hardware-server ~]# cd /tools/Xilinx/HWSRVR/2019.1/data/xicom/cable_drivers/lin64/install_script/install_drivers/
[root@hardware-server install_drivers]# ./install_drivers
INFO: Installing cable drivers.
INFO: Script name = ./install_drivers
INFO: HostName = hardware-server
INFO: Current working dir = /tools/Xilinx/HWSRVR/2019.1/data/xicom/cable_drivers/lin64/install_script/install_drivers
INFO: Kernel version = 3.10.0-957.el7.x86_64.
INFO: Arch = x86_64.
USB udev file exists and will not be updated.
--File /etc/udev/rules.d/52-xilinx-ftdi-usb.rules exists.
--File /etc/udev/rules.d/52-xilinx-ftdi-usb.rules version = 0001
--File 52-xilinx-ftdi-usb.rules exists.
--File 52-xilinx-ftdi-usb.rules version = 0001
--File 52-xilinx-ftdi-usb.rules is already updated.
--File /etc/udev/rules.d/52-xilinx-pcusb.rules exists.
--File /etc/udev/rules.d/52-xilinx-pcusb.rules version = 0002
--File 52-xilinx-pcusb.rules exists.
--File 52-xilinx-pcusb.rules version = 0002
--File 52-xilinx-pcusb.rules is already updated.

INFO: Digilent Return code = 0
INFO: Xilinx Return code = 0
INFO: Xilinx FTDI Return code = 0
INFO: Return code = 0
INFO: Driver installation successful.
CRITICAL WARNING: Cable(s) on the system must be unplugged then plugged back in order for the driver scripts to update the cables.

Installed packages that were previously suggested to help:

[root@hardware-server install_drivers]# yum install libusb kernel-headers kernel-devel
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
Package 1:libusb-0.1.4-3.el7.x86_64 already installed and latest version
Package kernel-headers-3.10.0-957.el7.x86_64 already installed and latest version
Package kernel-devel-3.10.0-957.el7.x86_64 already installed and latest version
Nothing to do

Windrvr6 Suggestion

An older support ticket talks about "/dev/windrvr6", but there was no such device.

https://www.xilinx.com/support/answers/54381.html

Operating System:

[root@hardware-server bin]# cat /etc/os-release
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

[root@hardware-server install_drivers]# uname -r
3.10.0-957.el7.x86_64

Host Operating System VMWare EXSI:

The operating system running on EXSI server, with the USB enabled at the EXSI level "Future Devices Digilent USB Device (Connected)".

Client version:

1.33.4

Client build number:

14093553

ESXi version:

6.7.0

ESXi build number:

14320388

0 Kudos
1 Solution

Accepted Solutions
13 Views
Registered: ‎05-21-2019

Re: Xilinx JTAG Fails to Connect to Digilent Programmer

Jump to solution

We eventually figured out that the specific JTAG programmer we were using couldn't handle the virtualisation of the ESXI host.

We installed an USB PCIE card into the ESXI host and setup the card for passthrough mode. After we connected the JTAG to the PCIE card (which is running in passthrough mode), we were able to successfully detect the FPGA on the JTAG.

View solution in original post

0 Kudos
1 Reply
14 Views
Registered: ‎05-21-2019

Re: Xilinx JTAG Fails to Connect to Digilent Programmer

Jump to solution

We eventually figured out that the specific JTAG programmer we were using couldn't handle the virtualisation of the ESXI host.

We installed an USB PCIE card into the ESXI host and setup the card for passthrough mode. After we connected the JTAG to the PCIE card (which is running in passthrough mode), we were able to successfully detect the FPGA on the JTAG.

View solution in original post

0 Kudos