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!

AR# 67381

2016.1 Vivado Hardware Manager: Incorrect IDCODES shown in Vivado Hardware Manager GUI for some UltraScale devices

Description

There are incorrect IDCODES shown In the Vivado Hardware Manager GUI for some UltraScale devices. Please see the example below.

In Vivado 2015.4, a board with Production silicon shows the IDCODE as 13931093.

In Vivado 2016.1, the same board shows the IDCODE as 03931093.

Why does this discrepancy appear?

Solution

This discrepancy between IDCODEs in Vivado 2015.4 and 2016.1 was due to an issue in the 2016.1 Vivado Hardware Manager GUI. This issue was resolved in Vivado 2016.2.

If you cannot update to Vivado 2016.2, please issue the following Tcl commands in order to to identify the correct IDCODE when using 2016.1:

After connecting to the board:

For the VU095 (VCU108):

  • close_hw_target
  • open_hw_target -jtag_mode 1
  • scan_ir_hw_jtag 6 -tdi 09
  • scan_dr_hw_jtag 32 -tdi 0


For the KU040 (KCU105):

  • close_hw_target
  • open_hw_target -jtag_mode 1
  • scan_ir_hw_jtag 6 -tdi 09
  • scan_dr_hw_jtag 32 -tdi 0


For the VU190 (VCU110):

  • close_hw_target
  • open_hw_target -jtag_mode 1
  • scan_ir_hw_jtag  18 -tdi 09249
  • scan_dr_hw_jtag 32 -tdi 0

The correct IDCODE will then be reported.

AR# 67381
Date Created 06/14/2016
Last Updated 07/29/2016
Status Active
Type General Article
Devices
  • Kintex UltraScale
  • Virtex UltraScale
Tools
  • Vivado Design Suite - 2016.1