I am trying to program the Spartan 3E Breakout Dev board from sparkfun, but I’m getting:
INFO:iMPACT:583 - ‘1’: The idcode read from the device does not match the idcode in the bsdl File.
INFO:iMPACT:1578 - ‘1’: Device IDCODE : 00000000000000000000000000000000
INFO:iMPACT:1579 - ‘1’: Expected IDCODE: 00000001110000100010000010010011
Any ideas of whats going on?
Thanks!
It looks like you have a problem with the JTAG connections to the FPGA. What interface are you using? Where’s the data for the board?
Leon
I’m using sparkfun’s Xilinx FPGA Parallel Programmer, which is similar to the Xilinx Parallel cable III. Connecting that to the board is a Samtec IDC cable.
I’m not sure what you mean by data… the FPGA is a spartan 3e XC3S500e.
I meant the data for the board.
You might have a problem with the board, the JTAG interface, or the cable. Can you test the interface on a board you know is working? I’ve got several Xilinx boards and a couple of JTAG interfaces here, which would be useful if I had problems like that. I never have had, though. 
Leon
The board I’m using is:
http://www.sparkfun.com/commerce/produc … ts_id=8458
I tried ringing it out, everything seems connected. The driver chip might be busted for the parallel cable.
I also read that it might be a power issue, but my supply is 5 V at 2 A.
Unfortunately I don’t have another board to test it out on. briefly I did get IDCODE = 000011111111111 (somewhat) But I haven’t been able to repeat that case.
Thanks for your suggestions anyway.
That could very well be. I haven’t used a Xilinx board since many years ago in school. And I’m really now just learning the software.
first, I hook up the power, parallel cable. The config mode I use is
m2 m1 m0 = 0 1 0, which I understand to be the JTAG mode
and start iMPACT. Then I create a new project, and check the box:
Configure devices using Boundary-Scan (JTAG) and select automatically connect to a cable.
It recognizes a Parallel III cable, but an ‘Unknown File Device Query’ window pops up. asking for a BSDL or BIT file. I load xc3s500e.bsd from the ISE directory.
Then, in the iMPACT processes window I double click ‘Check Idcode’. and get:
INFO:iMPACT:583 - ‘1’: The idcode read from the device does not match the idcode in the bsdl File.
INFO:iMPACT:1578 - ‘1’: Device IDCODE : 00000000000000000000000000000000
INFO:iMPACT:1579 - ‘1’: Expected IDCODE: 00000001110000100010000010010011
I figure if it was working properly, It should be able to read the IDCODE.
Also, I have breadboarded a parallel cable, and have gotten similar results.
Yes, it should be able to read the code. I’d ask SFE about it, the board might be faulty.
Leon