Jump to content
  • 0

Unable to Connect to Zedboard Target in Vivado via JTAG (Not Micro USB)


khobbit

Question

I need to use the JTAG header to program the Zedboard, since the MicroUSB connector is physically damaged.

I cannot find any documentation or forums about how to use the JTAG connector for programming the FPGA, so I am going to ask for your help.

I have a basic design in Vivado for making switch 0 toggle led 0. The bitstream is ready to be sent to the FPGA. However, when I try to connect to the hardware, by clicking "Open target", it is unable to connect.

error.thumb.PNG.22c45bfe892417f3b93697a49eb3c201.PNG

When I try to manually connect:

error2.PNG.fad07e7f1359cec7452f5111210d0adf.PNG

I am using Xilinx Platform Cable USB adapter for connecting the JTAG to the computer's USB input:

jtag.thumb.jpeg.2bc9473f40bad9f410593ccc52196281.jpeg

I have the driver installed, and it appears in my list of devices when plugged in, and disappears if I unplug it, and is up-to-date:

devices.thumb.PNG.88988d4fb8e87cc3ccc6729dbd553be7.PNG

I suspect the jumpers may not be configured properly? But again I cannot find clear documentation on how to set this up. This is how mine is set up:

setup_sm.thumb.jpg.f2d4c26bd360a6e183ed2fa12be44eac.jpg

Here is some information about my computer:

OS.PNG.de9d784e27578ebf5fafc68944f128bc.PNG

I am using Vivado 2016.1, since that is used in a lot of the tutorials. I think the Diligent tutorial uses 2016.2. It also comes with the Zedboard board file, although I downloaded the one made by Diligent as instructed in the tutorial.

I hope I have provided enough information. I appreciate any help!

Link to comment
Share on other sites

5 answers to this question

Recommended Posts

Hi @khobbit,

I don't believe Digilent has a tutorial that uses 2016.2, the three primary guides we have for getting started with Vivado are in 2016.4 (link), 2018.2 (link) and 2020.1 (link).

Regardless, based on the screenshot in your device manager, the problem you are encountering is a bug with the Xilinx installation script that doesn't install their drivers correctly. You can fix this by following the steps outlined in this specific post:

Thanks,
JColvin

Link to comment
Share on other sites

22 hours ago, JColvin said:

Hi @khobbit,

I don't believe Digilent has a tutorial that uses 2016.2, the three primary guides we have for getting started with Vivado are in 2016.4 (link), 2018.2 (link) and 2020.1 (link).

Regardless, based on the screenshot in your device manager, the problem you are encountering is a bug with the Xilinx installation script that doesn't install their drivers correctly. You can fix this by following the steps outlined in this specific post:

Thanks,
JColvin

Hello @JColvin. I am not sure how to follow those steps since the C:\Xilinx\Vivado\2016.1\data\xicom\cable_drivers\nt64\dlc10_win7 directory does not exist for me:

321990018_nt64directory.thumb.png.f5b398889bb9b19f86cff3f6ad85d545.png

Also here is what's inside of the diligent directory:

1347200829_diligentdirectory.PNG.577a83b5c494620f135c249bb4f4fc17.PNG

If I try going there in the command prompt:
image.png.99ac8c40b028bbacb6f37f4f89e3ba3f.png

I also tried following the instructions on pg.28 of the Vivado Design Suite User Guide ("Installing Windows Driver"), however it is not clear what to put for %log_dir%. I am not sure where this log directory is supposed to be. I tried both "install_drivers_wrapper.bat" as well as "install_drivers_wrapper.bat %log_dir% %log_dir%" since I was not sure which way was correct. But still it is not working afterward.

Link to comment
Share on other sites

22 hours ago, JColvin said:

Hi @khobbit,

I don't believe Digilent has a tutorial that uses 2016.2, the three primary guides we have for getting started with Vivado are in 2016.4 (link), 2018.2 (link) and 2020.1 (link).

Regardless, based on the screenshot in your device manager, the problem you are encountering is a bug with the Xilinx installation script that doesn't install their drivers correctly. You can fix this by following the steps outlined in this specific post:

Thanks,
JColvin

@JColvinI just now tried running those four commands inside of the nt64 directory instead, since I noticed those files were there, but it is still not being detected by the hardware manager:

image.thumb.png.c7b65665cc2f1e166d0f94af77cf88f2.png

When I plugged in the cable, this is what I see in device manager:

image.png.f884cced367b988a3b482d40fe152a33.png

I noticed it is not called "Xilinx USB Cable" as you mentioned, however I followed the steps quite carefully so I am not sure why it is still called "Xilinx Embedded Platform USB Firmware Loader".

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...