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?
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):
For the KU040 (KCU105):
For the VU190 (VCU110):
The correct IDCODE will then be reported.