ANSWERED Can't program the CoolRunner with the LTP cable

T

the_leaf

Noob Account
Dec 2, 2011
6
0
Hi!

I purchased your Xecuter Coolrunner & its LTP programming cable (I don't have a nandX) but I'm having issues programming the board.

When I connect it, the green and red LEDs light up, but somehow it's not properly recognized.

I tried with your "JTAG Tool" but when I click "flash glitch board" the command-line window that pops up tells me it can't find any programmable USB devices (even if I'm sure I've chosen LTP and not USB).

I tried with iMPACT (even tho I didn't find a guide to use it here in the forum, maybe I haven't searched properly, can someone link me to one?) but it detects the board but doesn't recognize it, it asks me for a BSDL file to identify it, but I don't have such file nor know where to get it.
 
Martin C

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
ok - can't find anything at the moment on our site. I used the RGH guide PDF published by gligli a while back.

If you're still having issues, get TeamViewer and PM me your ID and password from it and I'll take a look. Better make it quick though as I'm off to bed soon!
 
T

the_leaf

Noob Account
Dec 2, 2011
6
0
After googling a bit I tried with urJtag and with 360gcProg and they both tell me "TDO seems to be stuck at 0". I'm beginning to suspect either the board or cable is faulty... can't find anything about this error online... I may be able to get teamviewer up and running for you to access but not right now, as I'm not at home, will contact you later if I see you online, tho I don't think it'll work at this point...
 
Martin C

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
Cool - 360gcProg should work in place of iMPACT so if that's not having any of it, there might be a bigger issue at hand.

green LED in PRG mode means it's empty, so good.
red LED means it's getting power, so also good.

Are you using a native LPT port?
 
T

the_leaf

Noob Account
Dec 2, 2011
6
0
Martin C said:
Cool - 360gcProg should work in place of iMPACT so if that's not having any of it, there might be a bigger issue at hand.

green LED in PRG mode means it's empty, so good.
red LED means it's getting power, so also good.

Are you using a native LPT port?
Click to expand...
YEs, tried to set it as "bi-directional" and "ECP" in BIOS but both failed.

I'll try to build a DIY jtag cable in the afternoon, see if it solves anything.

In the meantime, any ideas are welcome ;)
 
G

gogocons

VIP Member
Nov 24, 2006
15
8
I don't know if this will help but I used gligli's schematic to build the programming cable and it didn't work. I was frustrated but after some intense google searching I found a thread that had the same schematic minus the diodes and resistors and it worked first try. Just something to think about if you're going to make your own cable.

Here's the thread to save time: http://team-xecuter.com/forums/showthread.php?t=75328
 
W

werewolfman

Full Member
Nov 1, 2011
67
0
Cairo, Egypt
isn't 360gcprog supposed to handle svf files ?
i mean 360gcprog can't not use the official timing files in the sticky because they r in XSvf format , right ?
not being a smartazz...just asking

---------- Post added at 04:42 ---------- Previous post was at 04:36 ----------
gogocons said:
I don't know if this will help but I used gligli's schematic to build the programming cable and it didn't work. I was frustrated but after some intense google searching I found a thread that had the same schematic minus the diodes and resistors and it worked first try. Just something to think about if you're going to make your own cable.

Here's the thread to save time: http://team-xecuter.com/forums/showthread.php?t=75328
Click to expand...
i think u should read the warning too . i guess using a multimeter to check the voltage supplied to the CR is not a bad idea to make sure
 
T

the_leaf

Noob Account
Dec 2, 2011
6
0
Damn, built BOTH the DIY cables and they both don't work... the one with the diodes tells me "TDO seems to be stuck at 0", while with the one wihtout the program tells me "Your device seems not to be properly powered (even tho the board has power, as the red LED shows...)

As for iMPACT, no, it doesn't detect the ID, it shows up as "unknown bypass"...

---------- Post added at 08:50 ---------- Previous post was at 08:45 ----------

Another idea: iMPACT tells me it could try to detect the chip by using a BSDL file or if I insert the device name and instruction length manually, can anyone tell me these values, or pass me a BSDL file that is good for the coolrunner?
 
G

gogocons

VIP Member
Nov 24, 2006
15
8
When I used my DIY cable with no diodes I got an error too but I switched from NORM to PROG right before programming and that worked for me, try it out.
 
W

werewolfman

Full Member
Nov 1, 2011
67
0
Cairo, Egypt
the_leaf said:
Damn, built BOTH the DIY cables and they both don't work... the one with the diodes tells me "TDO seems to be stuck at 0", while with the one wihtout the program tells me "Your device seems not to be properly powered (even tho the board has power, as the red LED shows...)

As for iMPACT, no, it doesn't detect the ID, it shows up as "unknown bypass"...

---------- Post added at 08:50 ---------- Previous post was at 08:45 ----------

Another idea: iMPACT tells me it could try to detect the chip by using a BSDL file or if I insert the device name and instruction length manually, can anyone tell me these values, or pass me a BSDL file that is good for the coolrunner?
Click to expand...
are u sure that the diode are in the right direction ???

as for the second case "Your device seems not to be properly powered" --> make sure in impact toolbar-->output--> cable setup-->communication mode= parallel cable lll , port=lpt x where is is ur port number,cable plugin (check) = xilinx_parallel PORT=LPT1 FREQUENCY=2500000 assuming 1 is ur lpt number

i had this problem when using impact at the first time although i was sure the voltage is right & red led is on & i found that i had a cold solder in one component after checking all components :facepalm:
 
T

the_leaf

Noob Account
Dec 2, 2011
6
0
Solved it guys!

Turns out your cable was too long (and my DIY one as well, in fact the piece of cable I bought for it was even longer). I chopped the cable in half, removed the middle of it and resoldered the two ends together, so it was only 5cm long. At that point the board was instantly recognized, I programmed it, installed it and I'm happily running a glitched jasper (boot times are great btw, no more than 2-3 seconds to boot)

Thanks for the suggestions and the support.
 
You must log in or register to reply here.