Peter0201

I found that installing the latest driver from FTDI (see this post) resolved my issue. I did have to uninstall all other drivers using their uninstaller tool. I can confirm that I was able to use the Xilinx tools (SDK 2019.1 and Vitis 2022) to connect to our hardware using the JTAG-HS3 cable. This was running Windows 11 ARM in Parallels Desktop 17 on Mac Book Pro with M1 Max CPU. I can also confirm that this is running everything faster and smoother than ever before.

Hi @attila Do I need a specific driver for theJTAG-HS3 device, or can one of the general FTDI drivers work? According to the FTDI drivers site the do have drivers for Windows 11 ARM for the D2XX and they have a special mention that it has been tested in Parallels on Mac M1.

Thanks for getting back to me and apologies for only replying now. I did not get an e-mail notification and saw it was not set-up correctly. I downloaded the latest ARM drivers from FTDI but this installed the device as a Serial Port device. It is not picked-up by Xilinx and does not work. Should I have installed it differently, or any other suggestions?

I am looking for a Digilent Cable Driver that will install and work on Windows for ARM to enable Xilinx SoC and FPGA development. We do hardware and software development that requires software running on MacOS, Windows and Linux. For the last 10 years we had no problems developing on Apple hardwaring using Parallels to smoothly also run on Windows and Linux. Apple's ARM platform is changing this and we need to adapt. One of our development branches is hardware using Xilinx SoC and FPGAs. Their toolchain runs without issue on Windows for ARM but the Digilent drivers needed for JTAG connection does not install (also see this post: ). Is there a Digilent Cable Driver for Windows on ARM that could be used? EDIT: It seems the problem may not caused by Windows for ARM but rather Windows 11. The exact error message that I get when trying to install the driver is: "Adding the driver package failed : A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider." Searching for that on the web seems to be an issue with the driver signing that was changed in Windows 11.