TDO seems stuck on 1
I keep getting this while trying to program my Xilinx Spartan-3A X3S200A 500k gate FPGA development board. Its weird somtimes it works fine; other times it doesnt work and I keep getting this TDO seems stuck. Somtimes the FTDI connection dies and it falls out of my hardware (windows XP).
I tried cleaning it and everything. I got it to work really well all last night after hours of struggling with it. Now its not working again... Any ideas?
Also when using urJTAG; then I do the 'cable jtagkey' if the FPGA development board is plugged in (it uses USB power; but the FTDI chip on board is for UART communication from the FPGA only; not JTAG.) it seems to connect to the FPGA's FTDI instead of the bus blaster. There are two connections the BBv2 makes; is it perhaps connecting to the wrong one? If so; which is the JTAG target connection so I can disable the other one?
Urktag attaches to the first ftdi device. You could try changing the USB id and specifying it manually in urjtag to ensure you get the right device.
Can you tell me how to go about doing that? because im struggling with this:
UrJTAG 0.10 #1502
Copyright (C) 2002, 2003 ETC s.r.o.
Copyright (C) 2007, 2008, 2009 Kolja Waschk and the respective authors
UrJTAG is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
There is absolutely no warranty for UrJTAG.
WARNING: UrJTAG may damage your hardware!
Type "quit" to exit, "help" for help.
jtag> cable jtagkey
Connected to libftd2xx driver.
jtag> detect
Warning: TDO seems to be stuck at 1
jtag> reset
jtag> cable jtagkey
Connected to libftd2xx driver.
jtag> cable jtagkey
Connected to libftd2xx driver.
jtag> detect
Warning: TDO seems to be stuck at 1
jtag>
all day...
I disconnect all FTDI devices and still; I tried changing the two BBv2 com port settings (swapping; to see if perhaps its the # order; still same results).
Any help would be appreciated. I attempted this with the xmega devices too for the first time (i want to program xmegas with this so bad!!) but i kept getting this error... so I had to give up.
Out of the ~40 times trying to connect; I have connected twice to the desired target. How do I go about changing the VID/SID?
I got it working; I use my hot air gun to reflow the board. Perhaps a loose pin on the ftdi.
When I first got it was working perfectly; The other day I accidently knocked over a table and a bunch of my stuff fell including the BBv3. I havnt tried it sence then; so im sure thats was caused it. Anyways; a reflow worked nicly :3
I want to make this clear by making it a new post. incase people saw the first one and overlooked my edit.
I am 90% sure the reason the reflow fixed the issue is because I dropped (aka abused) the device. It was working alright before that day.
thanks ;3
Argh. I wrote a long reply and it was lost on my phone I guess. I'm so sorry there were issues. For anyone else with multiple ftdi I think the way to use custom USB id is :
Cable jtagkey vid = '0000' pid = '0000'
Where 0000 and 0000 are the ids of the device. You can change the USB id with ftdis utility under windows, or robots utility unerring linux and Mac (see the wiki)
I'm struggling with this same problem with a brand-new v2.5 BB that I just received from seeed. As far as I know it hasn't been abused. :-)
I'm using it with one of your CoolRunner II breakout boards. I've successfully (re)installed BBv2-JTAGkey-v1.3.svf on the BB, thinking that that might be the problem. No change. I've successfully programmed the CPLD on the breakout board with a BusPirate, so the breakout board doesn't seem to be the issue.
I'm running jtag-rev11.exe to talk to the BB, under Windows XP SP3 (probably not relevant). I don't think that FTDI conflicts are the issue since 1) I have only the BB plugged into my PC while doing this work, and 2) I was able to reprogram the BB's own CPLD.
UrJTAG 0.10 #1869
Copyright (C) 2002, 2003 ETC s.r.o.
Copyright (C) 2007, 2008, 2009 Kolja Waschk and the respective authors
UrJTAG is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
There is absolutely no warranty for UrJTAG.
jtag.c:518 main() Warning: UrJTAG may damage your hardware!
Type "quit" to exit, "help" for help.
jtag> cable jtagkey
Connected to libftd2xx driver.
jtag> detect
discovery.c:117 urj_tap_detect_register_size() Warning: TDO seems to be stuck at
1
Error: parse.c:208 urj_parse_file() no error: Cannot open file 'C:Documents and
SettingsAdam/.jtag/rc' to parse
jtag>
I guess I could put a soldering iron tip on all of the CPLD pins to see whether I've got an open connection also; maybe BrentBXR's BB actually had the same problem as mine and the possible damage was coincidental? I'm speculating now, of course. I'm a little hesitant to start down that road since I'm brand new to using the BB and my problem could easily be operator error.
Thanks for any advice or wild guesses that anyone can provide. As it stands right now I'll have to give up on the BB and use my BP for programming CPLDs.
--Adam
Hi Adam,
First please double check that TDO and TDI are not swapped, that is a common cause of TDO stuck error. There certainly could have been a consistent manufacturing error (like one pin of a soldering stencil not fully removed). I will get one from the current batch too and check it out.
Thanks for your speedy reply!
I think I have things wired correctly, but this did cause me a bit of head-scratching and web-reading. Is it correct that TDO on the BB goes to TDO on the breakout board? Usually my JTAG connections are already wired for me so I won't be surprised if you tell me I'm wrong.
All fixed now!
Yes, I was wrong about TDO/TDI, Also, I was using JP1 rather than the JTAG connector on the BB. Yes, I've just demonstrated a significant amount of boneheadedness. :-P My apologies!
It seems to work fine now. Sorry again for any time wasted, alarm, confusion, etc.
Glad you got it, thanks for the update. Better that you had a misnake than we sold you a bad BB ;) I was getting worried, and you relieved me, that made my morning :)