cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
371 Views
Registered: ‎11-27-2018

Program QSPI flash failure using Jtag- HS3 programming cable on zc702

Hi,

I could succesfully program the QSPI Flash on the ZC702 Eval board using the on-board Digilent USB to jtag interface.

However, when I switch the Jtag interface to 14-Pin jtag and use HS3 Jtag interface, I am able to program the Zynq device directly but when I try to program the QSPI flash, it displays the following error which states that the device is not found.

Connected to hw_server @ TCP:127.0.0.1:3121
Available targets and devices:
Target 0 : jsn-JTAG-HS3-210299ABBED6
Target 1 : jsn-Cora Z7 - 7007S-210370A92F09A
Target 2 : jsn-JTAG-SMT1-210203A7DD77A

ERROR: Given target do not exist

When I try the same cycle with the on-board Digilent USB to jtag interface , "Device 0" is detected and programming the flash is sucessful as shown below.

Connected to hw_server @ TCP:127.0.0.1:3121
Available targets and devices:
Target 0 : jsn-JTAG-HS3-210299ABBED6
Target 1 : jsn-Cora Z7 - 7007S-210370A92F09A
Target 2 : jsn-JTAG-SMT1-210203A7DD77A
Device 0: jsn-JTAG-SMT1-210203A7DD77A-4ba00477-0

Retrieving Flash info...

Initialization done, programming the memory
===== mrd->addr=0xF800025C, data=0x00000000 =====
BOOT_MODE REG = 0x00000000
Downloading FSBL...
Running FSBL...
Finished running FSBL.

I would like to know why the "device 0" is not being detected when I am programming the flash with Jtag - HS3 Interface.

Are there any steps I am missing before I program the flash using HS3- Jtag interface.

Note : I am using Vivado 2018.3 version and programming the flash using the "Xilinx SDK - program flash GUI" to program the QSPI Flash.

 

Thanks in advance.

0 Kudos
1 Reply
Highlighted
Moderator
Moderator
206 Views
Registered: ‎02-09-2017

Hi @nithinvarma_a,

 

A few times I have seen a similar issue with Vivado HW Manager.

My guess is that when you use the HS3 cable, the hw_server is connecting at a higher JTAG speed (around 30 or 40MHz) and sometimes the hw_server cannot communicate and find a device at such high speed (specially in your case where it’s a 7-series device).

In comparison, when connecting with a Digilent USB cable, hw_server normally connects at 10 or 15MHz by default.

I’d suggest try lowering the JTAG speed and refreshing to see if it finds the device.

Since you're using SDK, I think you'd need to set the frequency as in the image below. Select “Manual Configuration of JTAG Chain” and then click on the frequency button.

Target_connection_SDK.JPG

You can also do the same test using Vivado HW Manager.

Thanks,

Andre Guerrero

Product Applications Engineer

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos