Skip to main content ↑ ↓
Topic: Bus Blaster V3 TDO stuck at 1 (Read 6641 times) previous topic - next topic

Bus Blaster V3 TDO stuck at 1

I recently bought a bus blaster v3. My operating system is: Ubuntu 12.04 64 bit.

I have pulled the latest version of urjtag from the SVN configured with: --with-ftd2xx --without-libftdi

The bus blaster is not powering the target, the jumper is open.

If I connect the bus blaster to my machine without any target connected I get this:

Code: [Select]
jtag> cable ft2232 pid=0x6010 vid=0x403 interface=1
Connected to libftd2xx driver.
jtag> detect
IR length: 8
Chain length: 1
Device Id: 00000110111000011100000010010011 (0x06E1C093)
  Manufacturer: Xilinx (0x093)
  Part(0):      xc2c32a-vq44 (0x6E1C)
  Stepping:     0
  Filename:     /usr/local/share/urjtag/xilinx/xc2c32a-vq44/xc2c32a-vq44

I am assuming that channel 1 goes to the CPLD itself and channel 0 is for access to the JTAG header.

Connect the cables to my target and power on target:

Code: [Select]
jtag> cable ft2232 pid=0x6010 vid=0x403 interface=0
Connected to libftd2xx driver.
jtag> detect
warning: TDO seems to be stuck at 1
jtag> detect

Now I get: TDO seems stuck at 1.

The most baffling part is that this works with an Altera byteblaster using urjtag.

Anyone have any suggestions to what I might be doing wrong ?

Re: Bus Blaster V3 TDO stuck at 1

Reply #1 –
Just to be sure, please load the latest bitstream to the CPLD.

I had a similar problem, moved to a new computer and had to install urjtag from scratch. I had to try getting it from Ubuntu repo, compiling a couple of times but no good. Then one of my tries succeeded, I don't know what happened, probably I changed one of the flags during config but not sure.

Re: Bus Blaster V3 TDO stuck at 1

Reply #2 –
[quote author="tayken"]Just to be sure, please load the latest bitstream to the CPLD.[/quote]

I can do that, do you have a link to where I can find the latest bitstream and instructions to do the download please ?

I have a V3 so I guess it has a different bitstream than V2 ?

Re: Bus Blaster V3 TDO stuck at 1

Reply #3 –
[quote author="tormod"]I can do that, do you have a link to where I can find the latest bitstream and instructions to do the download please ?[/quote]
Here you go:
Instructions: http://dangerousprototypes.com/docs/Bus ... _resources
SVN: http://code.google.com/p/dangerous-prot ... ffer_logic

[quote author="tormod"]I have a V3 so I guess it has a different bitstream than V2 ?[/quote]
I thought the only difference was board placement but after checking out the schematics, I saw that some connections have changed. There should be a bitstream in the forum that Ian published. I'll have to check it out later as it's getting pretty late here.

Re: Bus Blaster V3 TDO stuck at 1

Reply #4 –
Thanks for the links tayken!

[quote author="tayken"]I thought the only difference was board placement but after checking out the schematics, I saw that some connections have changed. There should be a bitstream in the forum that Ian published. I'll have to check it out later as it's getting pretty late here.[/quote]

Thank you very much, I'll wait for Ian's reply to make sure I program the correct bitstream.

Re: Bus Blaster V3 TDO stuck at 1

Reply #5 –
Hi,

I just received two Bus Blaster v3c from Seeedstudio and I face the same problems (TDO stuck at 1 ...).
With the original firmware I couldn't get any result with UrJTAG (from SVN) or any other tool.
So I built a programming file (.svf) using the constraints file from JTAGkey_test directory on the SVN [0] (with some lines commented out) and the Verilog source file used for BusBlaster v2 [1].
The resulting .svf file and the modified constraints file should be attached to this post (but I can't see them in preview mode).
Now I can get some results, but it's not reliable. It works once every ten tries.
I tried lowering the frequency, but with no significant result. Most of time I still get the "TDO stuck" error.
Sometimes it just simply works, and I can access the 5 chips of my test board. Then with no apparent reason it just stops working ...
Access to the onboard CPLD using the second channel is working flawlessly.
Next I will try to bypass the CPLD  and I will try to solder the probe wires on both sides instead of using jumper wires.

Chip soldering looks correct compared to my old BBv2.

Ideas are welcome ...

Wil

[0] trunk/Bus_Blaster/buffer_logic/JTAGkey_test/BBv3JTAGKEY.ucf
[1] trunk/Bus_Blaster/buffer_logic/JTAGkey-Verilog/jtagkey.v

Re: Bus Blaster V3 TDO stuck at 1

Reply #6 –
Missing files from previous post.

Wil

Re: Bus Blaster V3 TDO stuck at 1

Reply #7 –
Did this new bitstream clear it up? I didn't have any problems with v3 or v4 on my test setup, but that doesn't mean something hasn't gone horrifically wrong :(
Got a question? Please ask in the forum for the fastest answers.