Programing Coolrunner failed

[SOloNon]

hi . when i wanna programing my coolrunner with impact , impact show me error and programing failed
thi is the impact's console details :

INFO:iMPACT - Current time: 11/30/2011 12:04:30 �.// *** BATCH CMD : Program -p 1 -e -v
PROGRESS_START - Starting Operation.
Maximum TCK operating frequency for this device chain: 0.
Validating chain...
Boundary-scan chain validated successfully.
'1': Erasing device...
'1': Erasure completed successfully.
'1': Programming device...
done.
'1': Verifying device...
'1': Verification terminated due to errors
'1': Failed at address 1.
'1': Programming of user selected options failed.
PROGRESS_END - End Operation.
Elapsed time = 2 sec..

 

[Martin C]

Are you using the LPT or USB Cable?

 

[SOloNon]

lpt cable for programing coolrunner

 

[Martin C]

Which one - Team Xecuter or Xilinx?

 

[SOloNon]

team xecuter

 

[Martin C]

And you have the extra 3.3v power cable from the CK3, yes?

 

[SOloNon]

And you have the extra 3.3v power cable from the CK3, yes?

no i dont took any power from any other external supply . is that problem ?

 

[seanr28]

oh yes, must have external 3.3v supply

 

[SOloNon]

oh yes, must have external 3.3v supply

but impact detected the coolrunner

 

[Martin C]

No it didn't.

You removed the original log which gave it a device id of 0000000000000000000000000001 or something like that.

You MUST give it 3.3v from the CK3.

 

[SOloNon]

No it didn't.

You removed the original log which gave it a device id of 0000000000000000000000000001 or something like that.

You MUST give it 3.3v from the CK3.

so if even ben detected it cant be programed without external supply ?

 

[Martin C]

Post the information from the Error/Warning tab on iMPACT.

 

[SOloNon]

Welcome to iMPACT
iMPACT Version: 13.3
Project: C:\Xilinx\\auto_project.ipf created.
// *** BATCH CMD : setMode -bs
// *** BATCH CMD : setMode -bs
// *** BATCH CMD : setMode -bs
// *** BATCH CMD : setMode -bs
GUI --- Auto connect to cable...
// *** BATCH CMD : setCable -port auto
INFO:iMPACT - Digilent Plugin: no JTAG device was found.
AutoDetecting cable. Please wait.
PROGRESS_START - Starting Operation.
Connecting to cable (Usb Port - USB21).
Checking cable driver.
Source driver files not found.
The Platform Cable USB is not detected. Please connect a cable.If a cable is connected, please disconnect
and reconnect to the usb port, follow the instructions in the 'Found New Hardware Wizard', then retry
the Cable Setup operation.
Cable connection failed.
Connecting to cable (Parallel Port - LPT1).
Checking cable driver.
Driver windrvr6.sys version = 10.2.1.0. WinDriver v10.21 Jungo (c) 1997 - 2010 Build Date: Aug 31 2010 X86 32bit SYS 14:35:41, version = 1021.
LPT base address = 0378h.
ECP base address = 0778h.
Cable connection established.
PROGRESS_END - End Operation.
Elapsed time = 0 sec.
Attempting to identify devices in the boundary-scan chain configuration...
INFO:iMPACT - Current time: 11/30/2011 12:46:45 �.// *** BATCH CMD : Identify -inferir
PROGRESS_START - Starting Operation.
Identifying chain contents...'0': : Manufacturer's ID = Xilinx xc2c64a, Version : 0
INFO:iMPACT:1777 -
Reading C:/Xilinx/13.3/LabTools/LabTools/xbr/data/xc2c64a.bsd...
INFO:iMPACT:501 - '1': Added Device xc2c64a successfully.
----------------------------------------------------------------------
----------------------------------------------------------------------
done.
PROGRESS_END - End Operation.
Elapsed time = 2 sec.
// *** BATCH CMD : identifyMPM
// *** BATCH CMD : assignFile -p 1 -file "C:/Users/oveis/Desktop/jed/jasper.jed"
'1': Loading file 'C:/Users//Desktop/jed/jasper.jed' ...
done.
INFO:iMPACT:501 - '1': Added Device xc2c64a successfully.
----------------------------------------------------------------------
----------------------------------------------------------------------
INFO:iMPACT - Current time: 11/30/2011 12:47:05 �.// *** BATCH CMD : Program -p 1 -e -v
PROGRESS_START - Starting Operation.
Maximum TCK operating frequency for this device chain: 0.
Validating chain...
Boundary-scan chain validated successfully.
'1': Erasing device...
'1': Erasure completed successfully.
'1': Programming device...
done.
'1': Verifying device...
'1': Verification terminated due to errors
'1': Failed at address 0.
'1': Programming of user selected options failed.
PROGRESS_END - End Operation.
Elapsed time = 2 sec.

this

 

[Martin C]

No, that's not what you posted.

Open the warning tab on the GUI when it fails.

 

[SOloNon]

they are empty no errors or warnings

 

[splatem]

You need to power the cool runner, this can be with a ck3 cable or you can simply solder the gnd and 3.3v pads straight to your xbox as per final installation.

 

[Martin C]

Ok - thread will be closed as you are now wasting my time.

Your initial post, before you edited it had warnings of device ID not matching. You then EDITED this and have replaced it since.

Therefore unless you've now resolved the problem since, you're not giving all information which is being asked = waste of my time and others.

So - are you going to replace that information or not?

 

[SOloNon]

sry its cause in first post i use wrong port to impact . but my problem is the last information of imapct i posted .

 

[MODCUS]

You had your question answered. Now power it with 3.3v and then if you have a problem still post about it.

 

[Martin C]

ok, so if you're able to verify the write to the Coolrunner, you're good to go!