Skip to main content ↑ ↓
Topic: Bus Blaster 4.1 - Getting it to work (Read 604 times) previous topic - next topic

Bus Blaster 4.1 - Getting it to work

I just received my bus blaster 4.1 but i cant seem to get it to work.

I am runnin on linux
I have urjtag installed

I do:
Code: [Select]
jtag
cable ft2232 pid=0x6010 vid=0x0403 interface=1
detect
and get
Code: [Select]
warning: TDO seems to be stuck at 1

Am I doing something wrong?

I then attempted to reprogram the buffer (which I am unclear on how to do, since there is little to no documentation for BBv4 on this subject so I am working off forum posts from years ago) by switching the jumper to program mode.

now I do:
Code: [Select]
jtag
cable ft2232 pid=0x6010 vid=0x0403 interface=1
detect
and get
Code: [Select]
IR length: 8
Chain Length: 1
Device Id: 00000110111001011100000010010011 (0x06E5C093)
  Manufacturer: Xilinx (0x093)
  Unknown part! (0110111001011100) (/usr/share/urjtag/xilinx/PARTS)
And I don't know what to do next

I have also tried the configuration files given in the "guide" for openOCD, but they don't seem to work either.

Working with this thing is frustrating as hell, so please help.

I have also downloaded the git repo for bus blaster https://github.com/DangerousPrototypes/Bus_Blaster so please, if you want me to use a file give me the repo directory of it, instead of a forum link

If there has been anyone able to get BBv4 to actually work - especially on linux, a step by step would be very much appreciated.

Re: Bus Blaster 4.1 - Getting it to work

Reply #1 –
I also have the same problem.
I purchased Bus Blaster 4.1a from ebay.

However, I notice the one I received doesn't have mode jumper pins. Looks like all other people have mode jumper pins.
Can you take a picture of your board?
I don't know what the behaviour would be when without mode jumpers at all
[attachment=0]

Re: Bus Blaster 4.1 - Getting it to work

Reply #2 –
Even though the one I received is without mode jumper, I just used a bend attachment clip to short holes to simulate jumper on mode pins.
So far, update "buffer logic" is successful, and self-test is successful.

However, when attempting to connect to a developement board with JTAG port (JTAG port is working verfied by Lauterbach Trace32)

Code: [Select]
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 ft2232 pid=0x6010 vid=0x0403 interface=0
Connected to libftd2xx driver.
jtag> detect
Warning: TDO seems to be stuck at 1
jtag>

Since JTAG port and bus blaster v4.1a all supposed to be working, I wonder if it's the firmware that's not working?

The firmware I flahsed is from
gitBus_Blastermanufacturing_resourcesv4.1Programmingsvfbbv4.svf

And the binary comparison shows these two files are identical
gitBus_Blastermanufacturing_resourcesv4.1Programmingsvfbbv4.svf
GITBUS_BLASTERBUFFER_LOGICBBV4-JTAGKEY-SELFTEST-V1.1.SVF

I wonder it may mean that once flash with this firmware, bus blaster v4.1a can do nothing other than self-test??

Also, the last sentence on http://dangerousprototypes.com/docs/Bus ... _resources
Quote
We highly recommend users upgrade to a non-selftest buffer immediately.

So it make me wonder I need to flash it with a "non-self test" firmware to make it work?