Chris2000

Thanks for the followup @JColvin "Bus Reported Device Description" is Digilent Adept USB Device for all USB Serial Converter A-D. With Vivado closed, Adept can initialize the chain. Is "ARM_DAP" the ZU5 FPGA? When I browse to select a .bit file to program it, it refuses to select the file.

I cannot program the FPGA on this board over USB from Vivado's hardware manager or SDK. I get the error INFO: [Labtoolstcl 44-466] Opening hw_target localhost:3121/xilinx_tcf/Digilent/210383AF7FB6A ERROR: [Labtools 27-2269] No devices detected on target localhost:3121/xilinx_tcf/Digilent/210383AF7FB6A. The supplied demo is working, so the FPGA is functional. The board is a few weeks old. I have 2 PC's (windows 10 & Ubuntu) that both can connect and program an FPGA board (TEB707 + TEB0821) so I don't believe it's my drivers or cable. I have Xilinx tools versions 2019.1 and 2021.2 on both PC's. I get similar failures on all. Debug questions from another post: - If you are using Windows, can you see the board in the Windows device manager? It would be listed as USB Serial Converter A and USB Serial Converter B under the Universal Serial Bus controllers dropdown, both with which with bus reported device descriptions in the Details tab of their Properties window of "Digilent USB Device" When I connect the USB cable, I see USB Serial Converter A-D, but the details tab does not show Digilent. All have device description of USB Serial Converter x. - Did you install the cable drivers? Xilinx cable drivers, yes - Are you able to detect the board if you use the Digilent Adept software? The board is detected, but Initialize chain fails. Note I get the same result with the TEB707 + TEB0821 - Has the board been successfully detected before previously? no - Have you attempted to connect the board with a different USB cable or to a different computer? (You do not need to have Vivado installed on a different computer, you can check in the Device Manager or with the Digilent Adept software). Yes, I tried different cables & the linux computer. I'd appreciate any help getting this working.

I know the MIPI CSI-2 IP core is now free in the latest Vivado release, but I would like to use a project that was built in Vivado 2019 and that requires a license for the core. I purchased the board last week

@vcb1I got a mini-DP to regular DP cable and it does work. The PetaLinux console shows on the DP port at bootup and running DP-bist shows a test pattern. I assume an active cable that converts DP to HDMI protocol would work. I had tried a passive DP to HDMI cable, but after a bit of research I found that for this to work the DP source must be dual-mode/DP++, which means it can generate HDMI signals if it detects an HDMI cable. The Genesys board doesn't seem to have this capability. Good luck!

I'm having the same issue. I'm using a mini-DP to HDMI cable to connect the Genesys board to my monitor. root@GenesysZU:/usr/bin# DP-bist -v Encoders: id crtc type possible crtcs possible clones 41 0 TMDS 0x00000001 0x00000000 Connectors: id encoder status name size (mm) modes encoders 42 0 disconnected DP-1 0x0 0 41 ... failed to find mode "1920x1080" for connector 42 failed to create dumb buffer: Invalid argument