Michael Gordon

I haven't tried 2022.2, but I'd prefer to use the latest version if I can get it to work. The lab that we're trying to build a replacement for currently uses Vivado 2015.2 on Scientific Linux 7, and if we're going to persuade our academics to rewrite their entire lab notes then we really need to move to the latest version that can be used for several years. In some sort of progress, I've found an Ubuntu 20.04 box to test Vivado on and both 2015.2 and 2023 see the hardware. I don't think it's the kernel as both the 20.04 and 22.04 boxes are running 5.15.0-76-generic, but nothing obvious leaps out at me when I diff the package lists from both Ubuntu machines.

I run Vivado ML and click on "Open Hardware Manager" on the opening screen. After a little while the popup with the bar going back and forth disappears and I'm left with two bars at the top of the screen, one reading "HARDWARE MANAGER - unconnected" and the other reading "No hardware target is open. Open target". Clicking on "Open target" and selecting "Open New Target ..." from the menu that appears takes me to the Open Hardware Target wizard. "Next" takes me to the screen where I accept the default "Connect to: Local server" and click on "Next" again. After a few seconds I get the response seen in the first image. On a Scientific Linux 7 box I do the same and get the response seen in the second image. I may well be missing some important package - that would be a reasonable explanation of why it works on the SL7 box but not the Ubuntu 22.04 box - but I've no idea what that package may be. The installer doesn't complain about any missing packages and I can't find anything that seems relevant in the install notes. I have both libusb-0.1-4 and libusb-1.0-0 installed so both versions of the libusb API are available for example.

I've added the cable drivers both by running .../data/xicom/cable_drivers/lin64/install_script/install_drivers/install_drivers and by copying the udev rules from the SL7 box on which things work; the Ubuntu box doesn't see the card in either case.

This doesn't appear to be the case. Ununtu 22.04 is running kernel 5.15.0-76-generic, although they may have back-ported various things from newer versions. dadutil runs and sees the board w8557> dadutil enum Found 1 device(s) Device: Basys3 Device Transport Type: 00020001 (Transport Type = USB, Protocol = 2) Product Name: Digilent Basys3 User Name: Basys3 Serial Number: 210183714313 w8557> dadutil -d Basys3 showinfo Product Name: Digilent Basys3 User Name: Basys3 Serial Number: 210183714313 Product ID: 01700151 Firmware Version: 010A Device Transport Type: 00020001 (Transport Type = USB, Protocol = 2) Device Capabilities: 00000001 DJTG - JTAG scan chain access

I'm having similar problems, but only on Ubuntu 22.04 No version of Vivado on Ubuntu 22.04 will see my Digilent card. The Linux system is seeing the card: from "lsusb" I get Bus 001 Device 013: ID 0403:6010 Future Technology Devices International, Ltd FT2232C/D/H Dual UART/FIFO IC and from "djtgcfg enum" I get Found 1 device(s) Device: Basys3 Device Transport Type: 00020001 (USB) Product Name: Digilent Basys3 User Name: Basys3 Serial Number: 210183714313 but Vivado hardware manager doesn't see it. Weirdly, if I rsync the, for example, Vivado ML 2023 install onto an old Scientific Linux 7 box, then that version of Vivado that didn't see the card will see it when it's plugged in to the SL7 box. Is it possible that I'm missing a package or packages on the Ubuntu 22.04 install that make things work on the SL7 install?