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# 12995

5.1i iMPACT - Why does iMPACT identify a Spartan-II/-E device in a JTAG chain as a Virtex/-E?


Keywords: iMPACT, JTAG, Spartan-II, Spartan-IIE, idcode, intialize, chain

Urgency: Standard

General Description:
When I initialize my JTAG chain in iMPACT, why does iMPACT identify a Spartan-II/-IIE device as a Virtex/-E?


Spartan-II and Virtex have identical IDCODEs, and are therefore indistinguishable in a JTAG chain. (The same holds true for Spartan-IIE and Virtex-E.)

You may continue to program the Spartan-II/-IIE device normally by assigning the Spartan-II/-IIE bit file in iMPACT.
AR# 12995
Date 03/14/2005
Status Active
Type General Article