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!

The version of silicon on your board can also be determined by reading the JTAG ID in the iMPACT software.

For example, in the iMPACT GUI, the JTAG ID of the Spartan-6 device on a SP605 can be read as follows:

Connect one of the Type-A to Type-Mini-B USB cables (shipped with the board) to the USB JTAG Download Port (J4).
Ensure that it is the JTAG port that you connect to, and not the UART port. Power on the board.

Open up iMPACT, double-click Boundary Scan in the iMPACT Flows window.

Right-click in the Boundary Scan window and select Initialize Chain.

When the XC6SLX45T device appears in the Boundary Scan window, select it (it will turn green).

Double-click Get Device ID in the iMPACT Processes window to read the JTAG IDCODE (see below).

The resulting readout should be similar to the following (which is from an SP605 board):

The first digit (0 in these examples) is the JTAG ID code version field and reflects the silicon version.

This varies, depending on whether the device is ES or Production silicon.

Using the errata for your particular device outlines which JTAG ID corresponds to which device, and whether it is ES or Production silicon.
Use the Virtex-6 FPGA errata, found in the Virtex-6 Documentation Center (https://www.xilinx.com/support/documentation/virtex-6.htm#131587), to check the JTAG ID to identify your device.

Note: You can look at the production and ES errata to see what JTAG IDs are listed.

Occasionally, a JTAG ID revision might be listed for both ES and production.

This is due to the fact that if Xilinx runs out of ES silicon, production silicon is shipped as ES parts until all of the qualification and characterization are complete for a production release.

So, the best way to identify ES parts from production is from the top mark.

For example, LX240T with JTAG ID rev "4" is production silicon, however, they were shipped as ES devices.

Technically, ES devices are only guaranteed with ES errata (because the ES test program might not be upgraded to production level quality at the time those parts are shipped).

The revision code is not used by the programming tools when performing IDCODE verification.

Therefore, the programming tools do not error out while verifying ID codes with differing revisions.

UltraScale Kits

The IDCODE of UltraScale devices on UltraScale Boards and Kits can also help identify whether there is ES or Production Silicon on the relevant Evaluation Kits. To read the IDCODE of UltraScale devices, Hardware Manager in Vivado should be used.

When you open Hardware Manager, connect to the target, and then check the Hardware Device Properties on the left hand side of the GUI. The Hardware Device Properties window includes the ID code of the part, for example:

Once you have made a note of the ID code of the device on your board, you can then use the Configuration User Guide to confirm the silicon on the board.

For example, a device with IDCODE 0x1391093 is a Production XCVU190 device.

UltraScale+ Kits

The IDCODE of UltraScale+ devices on UltraScale+ Boards and Kits can also help identify whether there is ES or Production Silicon on the relevant Evaluation Kits. To read the IDCODE of UltraScale+ devices, Hardware Manager in Vivado should be used.

When you open Hardware Manager, connect to the target, and then check the Hardware Device Properties on the left hand side of the GUI. The Hardware Device Properties window includes the ID code of the part, for example:

Once you have made a note of the ID code of the device on your board, you can then use the Configuration User Guide to confirm the silicon on the board.