The diagnostics indicate that the issue is related to the hardware connection rather than the type of board. Therefore, purchasing a new board won't resolve the issue unless the connection is properly established.
The logs you are seeing are from the Vivado command prompt, as MathWorks launches Vivado tools using a batch Tcl script to execute Tcl commands.
The specific error suggests t,hat Vivado is unable to open the hardware target (e.g., the FPGA board), as the hardware device at the specified chain_position is either not found or cannot be communicated with. To address this, ensure that your board is powered on, and verify that the JTAG/USB download cable is connected correctly to both the board and your computer.
To troubleshoot this:
1. Verify hardware detection in Vivado. To do this:
- Open Vivado Hardware Manager and check if you can detect or program the device.
- Manually attempt to open the target and verify whether the hardware appears in the list. If it doesn't, Vivado may not be detecting the hardware.
2. You can also check for the hardware using the Vivado Tcl console with the following commands:
- If the device is detected, restart MATLAB and set up the Vivado tools and your Zybo board again. If not, the issue is likely a connection problem.
3. Make sure you have downloaded the Lab Edition from the AMD Unified Installer for FPGAs & Adaptive SoCs, as this version provides the necessary drivers and capabilities to program an FPGA device.
4. If you have multiple FPGA devices connected in a JTAG chain, try working with a single device to simplify debugging.
5. You mentioned using Vivado 2020.1, but the retry dialog shows Vivado 2022.1. Ensure that the version you are using matches the settings in both MATLAB and Vivado.
6. If the issue persists, try running the setup on a different computer or with another Zybo board to rule out hardware or environment-specific issues.
By following these steps, you can identify whether the problem lies in the hardware connection or the software configuration and resolve the issue accordingly.
Hope this helps.