UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Observer logicaledge
Observer
392 Views
Registered: ‎12-16-2014

ZU6 sometimes identifies as ZU9 in Vivado HW Manager

My ZU+ device is the xczu6eg-ffvb1156 device, marked as such on the device package. When I connect to the board with Vivado Hardware Manager, it connects reliably via JTAG, but sometimes the device identifies as a ZU6, but other times as a ZU9. It happens with both Digilent and Xilinx programming cables, and at multiple JTAG clock frequencies including the slowest options available.

Any ideas? Has anyone else seen this behavior?

Thanks,
Kevin

0 Kudos
4 Replies
Xilinx Employee
Xilinx Employee
384 Views
Registered: ‎06-06-2018

Re: ZU6 sometimes identifies as ZU9 in Vivado HW Manager

Hi @logicaledge

which Vivado version you are using ?

Please share the snapshot of IDCODE read from the Vivado hardware manager when you connect the device.

please refer this https://www.xilinx.com/support/answers/67381.html, helpfull for your query.

 

regards,

Deepak D N

------------------------------------------------------------------------------------

Please Reply or Give Kudos or Mark it as an Accepted Solution.

-------------------------------------------------------------------------------------

0 Kudos
Xilinx Employee
Xilinx Employee
356 Views
Registered: ‎03-07-2018

Re: ZU6 sometimes identifies as ZU9 in Vivado HW Manager

Hi @logicaledge

Check following possible causes of Zynq UltraScale+ (not Zynq-7000) device reports an incorrect JTAG IDCODE when identified by Vivado HW Manager

  1. PS_REF_CLK must receive a free-running clock source that is within operating specifications. (If there is no clock running, then the IDCODE might fail, as well as other device functionality.)
  2. PS_POR_B must be de-asserted when scanning for the JTAG IDCODE.  (The JTAG TAP works when PS_POR_B is asserted, but a returned IDCODE might not be right.)
Regards,
Bhushan

-------------------------------------------------------------------------------------------------------------------------------------------------
Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful.
Give Kudos to a post which you think is helpful and reply oriented.
-------------------------------------------------------------------------------------------------------------------------------------------------
0 Kudos
Observer logicaledge
Observer
345 Views
Registered: ‎12-16-2014

Re: ZU6 sometimes identifies as ZU9 in Vivado HW Manager

Hi @ddn,

I am using Vivado 2018.2.

Thanks,
Kevin

0 Kudos
Observer logicaledge
Observer
334 Views
Registered: ‎12-16-2014

Re: ZU6 sometimes identifies as ZU9 in Vivado HW Manager

Thanks, @bpatil - the note about POR assertion may be relevant to what we're seeing. We're investigating further and will update this thread if we can confirm.