well
it may be caused by one of the following reasons.
1- your spartanII device is an engineering sample (pre production sample)
2- it may use virtex bsdl file instead of spartanII
for more information you can check xilinx archive
regards
Hi, impact Returns IDCODE different from the IDCODE In the BSDL file
Returned IDCODE :00001111111111111111111111111110
IDCODE in BSDL File:00000000011000011000000010010011
Could a faulty JTAG cable be a cause of this error .Impact correctly detects the JTAG Cable.
hi
I have the same problem with xilinx saprtan II (xc2s150).
I connect the cable directly to boundary scan pins in the device through a test board. should I pull-up or pull-down any of these pins? if not what may be the source of problem in my hardware
I had configured a Virtex II device with the same cable and it worked correctly . (but that device was on an Avnet development board)
hi
I use ISE 5.1i for both synthesis and downloading the bit stream.( I also installed the service pack but the problem persisted) and I use XST for synthesising.did you mean that I should download the new bsd files from Xilinx?
p.s: I used the same software for cofiguring the virtex II.
hi
I use ISE 5.1i for both synthesis and downloading the bit stream.( I also installed the service pack but the problem persisted) and I use XST for synthesising..
:not: I don't have any idea, just try to debug your JTAG cable
or instead of bit file assain to impact the device bsd file, you will find it in
$:/xilinx/spartan2/data/
and try to get the device ID.
mehrara said:
did you mean that I should download the new bsd files from Xilinx?
hi
the problem was due to my cable.
I used an old cable and it worked correctlly.
but I don`t know why I can not program Spartan II with a cable by which I have programmed Virtex-E!
I also encountered this error (before this error It's ok), I checked as you did up , but the reason is software ,after I reinstalled the ise ,It worked ok again!, try it .