I have a Sparkfun Xilinx FPGA Breakout Revision 2.2 with Support
Circuitry(this one here:
http://www.sparkfun.com/commerce/product_info.php?products_id=8458) and a
Digilent UBS-JTAG Programmer Cable(this one:
I have never programmed the Xilinx FPGA before, as I just recieved the
I have connected the programmer to the FPGA board with a series of wires
coming out of the ribbon cable, with female crimped ends. The pinouts are
different, and this is the only way I could determine to fix this. I have
tried connecting the programmer to both of the available programming
headers on the FPGA, with no luck.
When I try and program the FPGA with iMPACT, I get the following error:
PROGRESS_START - Starting Operation.
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 :
INFO:iMPACT:1579 - '1': Expected IDCODE:
PROGRESS_END - End Operation.
Elapsed time = 0 sec.
I have tried reducing the clock, doing a boundary scan, etc. I continue to
get the same output.
The thing that really gets me is I get the exact same result if I unplug
the programmer from the FPGA board. Also, when I scope the data lines I
don't see any change at all. Its a constant 2.4 volts, which is what I see
with the programmer unplugged as well as plugged in. I figured I should at
least see a momentary pulse on the clock line for handshake, but I see
Does anyone have any ideas? I'm really confused, and would greatly
appreciate any help anyone can offer.
This message was sent using the comp.arch.embedded web interface on
Reply by cs_p...@hotmail.com●October 12, 20092009-10-12
On Oct 9, 7:57=A0am, "lambdanator" <xelap...@gmail.com> wrote:
> The thing that really gets me is I get the exact same result if I unplug
> the programmer from the FPGA board. =A0Also, when I scope the data lines =
> don't see any change at all.
Are you sure that IMPACT or the version of it that you are using
supports the Digilent USB cable? I think that there was a time when
impact only supported their parallel cable and they had their own
software to use with their USB cable, but then maybe impact finally
added support for the digilent usb cables in addition to the xilinx
Anyway, make sure that the cable is supported, and that impact isn't
trying to program off a perhaps non-existent parallel port rather than
These things can be real headaches until you get them working...