Print

[ravendrow]

ok so i finally got a test box to user my glitcher on hooked it up with the programmer i built using gligli's diagram, the chip gets identified perfectly in iMpact without having to do compatibility mode just like it did when i tested my programmer go to program and programming fails every time....anyone got any idea's ?? when i load the chip it brings up a programming properties screen and the general CPLD and prom tab is blocked out i think that is the issue but i cant figure it out grrr jtagging is so much easier lol

[ravendrow]

checked the log file and this is what it is saying

iMPACT Version: 13.2

iMPACT log file Started on Thu Oct 06 13:54:31 2011

Welcome to iMPACT
iMPACT Version: 13.2
// *** 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 (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 isconnected, please disconnect
and reconnect to the usb port, follow the instructions in the 'Found NewHardware 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 © 1997 - 2010 Build Date: Aug 31 2010 X86 32bit SYS14:35:41, version = 1021.
 LPT base address = 0378h.
 ECP base address = 0778h.
Cable connection established.
PROGRESS_END - End Operation.
Elapsed time =      1 sec.
Attempting to identify devices in the boundary-scan chain configuration...
INFO:iMPACT - Current time: 10/6/2011 1:54:47 PM
// *** BATCH CMD : Identify -inferir
PROGRESS_START - Starting Operation.
Identifying chain contents...'0': : Manufacturer's ID = Xilinx xc2c64, Version : 0
INFO:iMPACT:1777 -
   Reading C:/Xilinx/13.2/LabTools/LabTools/xbr/data/xc2c64.bsd...
INFO:iMPACT:501 - '1': Added Device xc2c64 successfully.
----------------------------------------------------------------------
done.
PROGRESS_END - End Operation.
Elapsed time =      1 sec.
// *** BATCH CMD : identifyMPM
The setting has been saved, to change the settings, please go toEdit->Preferences.// *** BATCH CMD : setPreference -pref StartupClock:AUTO_CORRECTION
// *** BATCH CMD : setPreference -pref AutoSignature:TRUE
// *** BATCH CMD : setPreference -pref KeepSVF:FALSE
// *** BATCH CMD : setPreference -pref ConcurrentMode:TRUE
// *** BATCH CMD : setPreference -pref UseHighz:FALSE
// *** BATCH CMD : setPreference -pref ConfigOnFailure:STOP
// *** BATCH CMD : setPreference -pref UserLevel:NOVICE
// *** BATCH CMD : setPreference -pref MessageLevel:DETAILED
// *** BATCH CMD : setPreference -pref svfUseTime:FALSE
// *** BATCH CMD : setPreference -pref SpiByteSwap:AUTO_CORRECTION
// *** BATCH CMD : setPreference -pref AutoInfer:TRUE
// *** BATCH CMD : setPreference -pref SvfPlayDisplayComments:FALSE
// *** BATCH CMD : assignFile -p 1 -file"C:/Glitch/fat/glitch48nofullpost/falcon.jed"
'1': Loading file 'C:/Glitch/fat/glitch48nofullpost/falcon.jed' ...
done.
INFO:iMPACT:1777 -
   Reading C:/Xilinx/13.2/LabTools/LabTools/xbr/data/xc2c64a.bsd...
INFO:iMPACT:501 - '1': Added Device xc2c64a successfully.
----------------------------------------------------------------------
INFO:iMPACT - Current time: 10/6/2011 1:55:30 PM
// *** BATCH CMD : Program -p 1 -v
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 :        00000110110001011000000010010011
INFO:iMPACT:1579 - '1': Expected IDCODE:    00000110111001011000000010010011
PROGRESS_END - End Operation.

any help would be greatly appreciated i built another programmer just to see if it was that and still same problem chip gets detected but not programmed

[Dicko316]

I had a similar experience, I had purchased a LPT Jtag cable and 4x Coolrunner II's, the Coolrunner II's came but the LPT cable was delayed a bit so I made up a cable myself to test it out straight away.
I ended up getting a similar error to yourself, except my chip was reporting as 00000000000001000000000000000000 or something like that. I rebuilt the cable 4-5 times and got the same result. I was going to try and build the cable without any Diodes and 3k3 resistors, just 1x 3k3 resistor on the 3.3v pin. But then my LPT cable came, plugged it in and worked first time.
So either buy a cable or maybe try without the diodes and 3k3 resistors.

[Dicko316]

This is similar to what i was talking about http://natrium42.com/projects/jtag.php

[ravendrow]

tried it ...no love....hey will this work? http://www.amazon.com/Digilent-JTAG-HS1-Pr...e/dp/B005CETF64

[Dicko316]

QUOTE(ravendrow @ Oct 7 2011, 03:27 AM)

tried it ...no love....hey will this work? http://www.amazon.co...e/dp/B005CETF64

Yeah that'll do the trick