Prev: ISE7.1 PAR Warinng: excessive skew because 1 NON-CLK pins...
Next: errors during MAP
From: damidar on 16 Jun 2005 12:17
Thanks I have made as you have said... unfortunately nothing... not
work.... :( :(

I have installed the last version of impact.....is the same... :cry:
:oops:

From: Gabor on 16 Jun 2005 16:54
This is the "catch-all" error for impact when the JTAG loop doesn't
work. I've seen this problem when there was a break in the TDI to
TDO chain, especially when the break was in TDI at the programming
connector of the board to be programmed.

If your chain first shows up (parts correctly identified) and then
won't respond to any programming commands I would look at the TDI
line to the first device in the chain.

Also check that all devices in the chain have core and I/O power
and that PROGB and INITB lines are high (for FPGA's).

No version of impact will work if the chain is improperly connected.

Good Luck,
Gabor

damidar wrote:
> Thanks I have made as you have said... unfortunately nothing... not
> work.... :( :(
>
> I have installed the last version of impact.....is the same... :cry:
> :oops:

From: damidar on 17 Jun 2005 12:17
now I will try to make it

thanks too gabor

From: damidar on 18 Jun 2005 20:16
Unfortunately xilinx dont't work :(

I'm using last versione webpack (impact) 7.1i

A question: but what's idcode? and where is idcode for xc9536xl

Thanks again

From: AMDyer@gmail.com on 18 Jun 2005 23:33
The IDCODE is part of the jtag interface. You load an
idcode instruction in the jtag instruction register and
the part will connect it's idcode register into the jtag
data register chain. The s/w will then switch to shift
the data register out and can get a mfg., device, and
revision number from it.

If you have non-xilinx devices in your chain, make sure
you're driving their TRST/ (async tap reset) pin inactive.

Also it's been my experience in the past with impact that
you should just do the most straightforward path to
programming your parts - define the chain, set the config
file and program. Using any other 'features' of impact
is likely to get it confused.

First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: ISE7.1 PAR Warinng: excessive skew because 1 NON-CLK pins...
Next: errors during MAP