Re: spartan-3e idcode
- From: jonpry@xxxxxxxxx
- Date: Sun, 15 Jul 2007 19:49:18 -0000
I am not totally sure if the 0x000c1003 is what is being sent by the
fpga. I don't have a logic analyzer so its hard to tell when the
bitstream starts. On my scope it looks like this:
---------- -- --- ----------------
------- ------ --------------
Which does not exactly correspond 11000001000000000011. I'm not sure
what the id should be and if there is any correlation between what is
read and the correct value.
My scope is only 100mhz, but the edges look really sharp to me. I
doubt the jtag circuits are fast enough to respond to anything above
this speed.
I was using a home made parallel 3. I know people have tons of trouble
with these, but the data going in/out seems to be really clean. Just
in case, i hooked my board into the jtag chain of digilent nexsys
board with a spartan-3e on it. It also has a integrated usb
programmer. My device was shown in the chain with the same garbage id
i see on my parallel 3. When trying to program the other devices, it
fails, leading me to believe the device cannot enter bypass mode.
Is there some combination of tdo,tdi,tms,tck that could be shorted
togeather to cause this? Are these kinds of things symptomatic of a
bad chip. I've also noticied some strange behavior on the
configuration port. The chip is setup to configure over SPI. CCLK is
going, but cso_b never goes low, and mosi never toggles. I've checked
the connections a thousand times.
.
- Follow-Ups:
- Re: spartan-3e idcode
- From: Alan Nishioka
- Re: spartan-3e idcode
- References:
- spartan-3e idcode
- From: jonpry
- Re: spartan-3e idcode
- From: Alan Nishioka
- Re: spartan-3e idcode
- From: austin
- spartan-3e idcode
- Prev by Date: Re: Which embedded O/S for a 32-bit RISC microcontroller?
- Next by Date: Re: spartan-3e idcode
- Previous by thread: Re: spartan-3e idcode
- Next by thread: Re: spartan-3e idcode
- Index(es):
Relevant Pages
|