Re: Parallel Cable IV in Spartan 3E???

Judging by the error you have a problem with the VCC or GND pin not being
connected.

The P-IV cable needs to 'sense' the voltage level on the board so it can
drive the JTAG pins to the correct levels.

Make sure the wires are seated properly, if they are then test the flying
leads - they are easy to break!

Ben



"Pablo" <pbantunez@xxxxxxxxx> wrote in message
news:1174568628.171929.227320@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I am trying to configure Spartan 3e (Starter Kit) with a Parallel
Cable IV (J28) with flying leads instead of USB. The reason is that I
must use flying leads with other fpga and first of all I prefer to try
with my cheap kit. Does anyone know why impact give me the following
error:

I have only connected the flying leads with the j28 six pins; TDI,
TD0, TMS, VCC...

Welcome to iMPACT
// *** BATCH CMD : setMode -bs
// *** BATCH CMD : setMode -bs
GUI --- Auto connect to cable...
// *** BATCH CMD : setCable -port auto
AutoDetecting cable. Please wait.
PROGRESS_START - Starting Operation.
Connecting to cable (Parallel Port - LPT1).
Checking cable driver.
Driver windrvr6.sys version = 8.1.1.0. LPT base address = 0378h.
ECP base address = 0778h.
ECP hardware is detected.
Cable connection established.
Connecting to cable (Parallel Port - LPT1) in ECP mode.
Checking cable driver.
Driver xpc4drvr.sys version = 1.0.4.0. LPT base address = 0378h.
Cable Type = 1, Revision = 3.
Setting cable speed to 5 MHz.
Cable connection established.
PROGRESS_END - End Operation.
Elapsed time = 1 sec.
Attempting to identify devices in the boundary-scan chain
configuration...Command: Identify
// *** BATCH CMD : Identify
ERROR:iMPACT:2243 - A reference voltage has not been detected on the
ribbon cable
interface to the target system ( pin 2 ). Check that power is
applied
to the target system and that the ribbon cable is properly seated at
both ends. The status LED on Parallel Cable IV will be GREEN if
target
voltage is in the proper range and applied to the correct pin.// ***
BATCH CMD : identifyMPM
ERROR:iMPACT:2243 - A reference voltage has not been detected on the
ribbon cable
interface to the target system ( pin 2 ). Check that power is
applied
to the target system and that the ribbon cable is properly seated at
both ends. The status LED on Parallel Cable IV will be GREEN if
target
voltage is in the proper range and applied to the correct pin.


Regards Pablo



.

Relevant Pages

  • Parallel Cable IV in Spartan 3E???
    ... Cable IV with flying leads instead of USB. ... Connecting to cable in ECP mode. ... interface to the target system (pin 2). ...
    (comp.arch.fpga)
  • Re: I picked up an Onyx 1640 ...
    ... constant voltage between pins 2 and 3 but allows the voltage between ... Pin 2 and ground and Pin 3 and ground to stttle wherever the component ... The advantage of this system is when connecting it to an unbalanced ... connecting a balanced output to an unbalanced input" problem. ...
    (rec.audio.pro)
  • Re: I picked up an Onyx 1640 ...
    ... constant voltage between pins 2 and 3 but allows the voltage between ... Pin 2 and ground and Pin 3 and ground to stttle wherever the component ... The advantage of this system is when connecting it to an unbalanced ... connecting a balanced output to an unbalanced input" problem. ...
    (rec.audio.pro)
  • nighthawk 550 electrical problem
    ... > Maybe you're not clear on the concept of the rectifier regulator unit. ... The rectifier and the *voltage* regulator. ... > on the voltage regulator to the DC positive output pin. ... check with the black lead from the AC input pin to the DC ...
    (rec.motorcycles.tech)
  • Re: nighthawk 550 electrical problem
    ... >> Maybe you're not clear on the concept of the rectifier regulator unit. ... >> You test the voltage regulator operation by doing the "charging ... >> on the voltage regulator to the DC positive output pin. ... >> check the first three diodes, touch the black lead's probe to the AC ...
    (rec.motorcycles.tech)