problem proramming the fpga on spartan 3e

[dag1]

After clicking the Configure iMPACT I click on xc3s500e and choose Assign New Configuration File.
I choose the  .bit file then I do "Program" but I get message:

ERROR:iMPACT:583 - '1': The idcode read from the device does not match the idcode in the bsdl File.

What is the bsdl file ?

Dag.

[architecture_whiz]

The BSDL file is the boundary scan decription file.  It tells the software the structure of the boundary scan chain, as well as things like the JTAG instruction width.

It can be found in the install directory for the Xilinx tools, then in the folder named after the device family.  Say I have an XC3S500E in the FG320 package.  The file would be located at:
$XILINX\spartan3e\data\xc3s500e_fg320.bsd

In the file, you can search for "IDCODE."  The expected IDCODE should be right after the second instance of the word in the file. 


What is the IDCODE that iMPACT is reading?  (This should be in the console window after an attempt to read the code.)

[Anonymous]

• In most cases, this IDCODE error message is indicative of a board problem. Mostly problems related to JTAG chain hardware. So please check all the programming hardware of the board.
• Perform an IDCODE looping test. If IDCODE looping fails, see http://www.xilinx.com/support/answers/8902.htm

• Check all the connections as per configuration guide recommendations

• Check the continuity of the cable & cable insertion direction.

• Check all the voltages of device. They should be with the range  as per data sheet recommendations

[bassman59]

---

@Anonymous wrote:

---

TWO AND A HALF YEAR OLD THREAD! A NEW RECORD!

[Anonymous]

• In most cases, IDCODE error message is indicative of a board problem. Mostly problems related to hardware. So please check all the programming hardware of your board.

• Obtain the IDCODE that iMPACT is reading from the device, and compare it to the IDCODE in the BSDL file.

- iMPACT will not report the exact IDCODE returned in Expert Operating mode. To view the actual IDCODE returned from the device, set iMPACT to Novice Operating mode (Edit -> Preferences).
- If the IDCODEs match, a software problem might exist.
- If the IDCODEs do not match, proceed to Step 2

• Perform an IDCODE looping test. If IDCODE looping fails, see http://www.xilinx.com/support/answers/8902.htm

• If possible Please check once all the voltages of the FPGA & Flash. They should be with the ranges given in data sheet operating voltage recommendations.

• The status register can be read out of the device via JTAG using iMPACT. Analyze the contents it helps you lot to debug.

[bassman59]

Mahesh, you're a robot, right?

[robinliuy]

Which ISE version do you use? Please attach iMPACT log file to debug this issue.

[eteam00]

The last time the original poster logged in was June.

Let it go!

- Bob Elkind