12-18-2018 07:58 AM
I've got an issue with a Zynq UltraScale+ MPSoC ZCU104 Evaluation kit, as the board is not recognized in the hardware manager, neither by Vivado 2018.2 nor 2018.3 on Ubuntu. I've tried with Ubuntu 16.04, 17.10 and 18.10 and even a separate HW_server. When Auto-connecting in the hardware manager, the device won't show up in the list. Open target -> Open new target... does not find any devices that could be added.
I installed the cable drivers from
<Xilinx Install Dir>/Vivado/2018.3/data/xicom/cable_drivers/lin64/install_script/install_drivers
It works flawlessly when attached to a PC running Vivado 2018.3 on Windows 8.1.
Even only running the hw_server standalone on the windows machine and connecting to it from Vivado on an ubuntu based machine works.
Dmesg shows the following when attaching the board and indicating that the board is recognised by the OS:
[17178.606305] usb 3-1.2: new high-speed USB device number 15 using xhci_hcd
[17178.758716] usb 3-1.2: New USB device found, idVendor=0403, idProduct=6011, bcdDevice= 8.00
[17178.758724] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[17178.758730] usb 3-1.2: Product: JTAG+3Serial
[17178.758735] usb 3-1.2: Manufacturer: Xilinx
[17178.758739] usb 3-1.2: SerialNumber: 1829
[17178.767184] ftdi_sio 3-1.2:1.0: FTDI USB Serial Device converter detected
[17178.767292] usb 3-1.2: Detected FT4232H
[17178.767707] usb 3-1.2: FTDI USB Serial Device converter now attached to ttyUSB0
[17178.769481] ftdi_sio 3-1.2:1.1: FTDI USB Serial Device converter detected
[17178.769579] usb 3-1.2: Detected FT4232H
[17178.769870] usb 3-1.2: FTDI USB Serial Device converter now attached to ttyUSB1
[17178.771576] ftdi_sio 3-1.2:1.2: FTDI USB Serial Device converter detected
[17178.771676] usb 3-1.2: Detected FT4232H
[17178.771965] usb 3-1.2: FTDI USB Serial Device converter now attached to ttyUSB2
[17178.773685] ftdi_sio 3-1.2:1.3: FTDI USB Serial Device converter detected
[17178.773789] usb 3-1.2: Detected FT4232H
[17178.774075] usb 3-1.2: FTDI USB Serial Device converter now attached to ttyUSB3
Any help is greatly appreciated .
If any more information is required to get to the bottom of this issue, please let me know.
01-11-2019 03:35 PM
I gave a try with Ubuntu 16.04 and it worked fine. Here are the snapshots.
I can accee the board with Vivado 2018.2
02-05-2019 07:08 AM - edited 02-05-2019 07:10 AM
Thank you for your reply. I made sure the cable drivers are installed correctly and I even reinstalled the drivers!
Other boards like e.g. the Zedboard are working just fine.
However, the zcu104 still can't be found from Vivado on Ubuntu. If the board is connected to a Windows machine running hw_server using the exact same cables and settings and accessed remotely from the Vivado instance on the Ubuntu machine the connenction is working just fine!
The ZCU104 chip is detected using lsusb as:
ID 0403:6011 Future Technology Devices International, Ltd FT4232H Quad HS USB-UART/FIFO IC
What else can I do to debug this issue?
How can I make sure the udev rules are working as intended?
02-05-2019 08:07 PM
Try changing read/write permissions on the USB / PC4 driver by typing:
chmod 666 /dev/windrvr6
Note: By default, access to windrvr6 is restricted to root only.
This step grants group and user access to the driver.
However, After rebooting your system, access to the driver will revert back to root-only and you need to change permissions again.
For more information check AR# 59128
02-06-2019 04:35 AM - edited 02-06-2019 07:11 AM
Thanks for your reply. I tried to follow the steps, however, `/dev/windrvr6` is not present on my system. Also the mentioned file in the AR# 59128
<Vivado installation dir>/data/xicom/cable_drivers/lin64/install_script/install_drivers/readme.txt
is not present, further indicating this is for a different vivado release. The suggested AR seems to be for an older installation of Vivado as it is from 2015, however, I am on the latest 2018.3 release.
The ./install_drivers script from the current release copies three udev *.rules files to /etc/udev/rules.d/ which seem to not be related in any way to a /dev/windrvr6 device as suggested in the AR.
I did some further testing and tried a Xilinx Platform Cable USB II (Model DLC10) to be used as a JTAG to USB interface, the board is working in this configuration on Ubuntu. This can be seen as a temporary workaround for this issue.
The onboard JTAG to USB interface is still NOT working on Ubuntu.
Any more suggestions on how to get this working?
EDIT: Unfortunately when using the JTAG interface (J180) with the plattform cable USB II for JTAG and the USB connector for the serial console, the serial console becomes nearly unusable as only the output is working.