AR# 12995

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

Description

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

Solution

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 can continue to program the Spartan-II/-IIE device normally by assigning the Spartan-II/-IIE bit file in iMPACT.

Was this Answer Record helpful?

AR# 12995
Date	09/06/2017
Status	Active
Type	General Article
Devices	Spartan-II Spartan-IIE Spartan-IIE XA More Virtex-E Virtex-E QPro Virtex Less
Tools	ISE - 10.1 ISE Design Suite - 11.1 ISE Design Suite - 11.2 More ISE Design Suite - 11.3 ISE Design Suite - 11.4 ISE Design Suite - 11.5 ISE Design Suite - 12.1 ISE Design Suite - 12.2 ISE Design Suite - 12.3 ISE Design Suite - 12.4 ISE Design Suite - 13 ISE Design Suite - 13.1 ISE - 8.1i ISE - 8.1i sp1 ISE - 8.1i sp2 ISE - 8.1i sp3 ISE - 8.2i ISE - 8.2i sp1 ISE - 8.2i sp2 ISE - 8.2i sp3 ISE - 9.1i ISE - 9.1i sp1 ISE - 9.1i sp2 ISE - 9.1i sp3 ISE - 9.2i ISE - 9.2i sp1 ISE - 9.2i sp2 ISE - 9.2i sp3 ISE - 9.2i sp4 ISE - Legacy Less

Page Bookmarked