1
Bus Blaster JTAG debugger / Re: Bus Blaster 4.1 - Getting it to work
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?