Bus Blaster v2.5 selftest mode

[Martytoof]

Hi there,

I'm trying to run the BBv2.5 in selftest mode. I shorted the appropriate pins in the jtag connector, shorted JP4, and shorted P28/GND. According to notes I found in the wiki I should now be reading 3.3v on P19, however that does not seem to be the case.

I just flashed the BBv2.5 from the KT-Link SVR back to the JTAGKey SVF that I found in "BusBlasterPackage v2.0.zip". Does this SVF not contain a selftest mode?



As an aside, overall I am finding that the documentation/resources for the Bus Blaster are very haphazard and I need to look in twelve different locations to track down files or answers. There are a lot of pages that link to different resources, the selftest page makes reference to bat files that aren't immediately obvious, there are a few dead links on the wiki (which I assume are just there because nobody has had a chance to create them yet). I really want to enjoy my Bus Blaster experience, but I think the documentation suffers from a little bit of ADHD. Not necessarily upset or anything, just a minor nitpick. I'm still trying to get my Bus Blaster running with OpenOCD and my STM32F3Discovery board but I'm finding that most of my time is spent trying to find information about the BB instead ;)

[ian]

Hi Marty,

I'm sorry about your experience with the documentation and self test, I'll work on updating and centralizing everything. If you have any specific requests I'll take care of those first.

Please find attached a .zip with the self-test bitstream and all the manufacturing tools. This should be in the /manufacturing_resources folder of the development package too, but it may be out of date.

[Martytoof]

Hi Ian,

Thanks for your quick reply.

My frustration mostly stems from the fact that I am a relative newcomer to EE in general and perhaps some of the things I think are difficult to find are things someone more seasoned would be much more comfortable with. I can certainly give you a rundown of my thought process with regards to what I expected to find where for reference, but I think my criticism came out a little harsher than I intended it to be. Thank you for considering reworking some aspects of the documentation, however :)

Also thank you for the attachment, I will give it a try ASAP!

Thanks.

[Martytoof]

Should I be concerned that ujtag can't make a connection with the Bus Blaster until the 8th time I try the command? Is this typical or indicative of some other fault? For reference, the commands were repeated perhaps two to five seconds apart until the board was detected:

C:\Program Files (x86)\UrJTAG>jtag-rev11.exe

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 ft2232 interface=1
Couldn't connect to suitable USB device.
Error: usbconn/libftd2xx.c:406 usbconn_ftd2xx_common_open() ftdi/ftd2xx error: Unable to open TFDI device: device not opened
jtag> cable ft2232 interface=1
Couldn't connect to suitable USB device.
Error: usbconn/libftd2xx.c:406 usbconn_ftd2xx_common_open() ftdi/ftd2xx error: Unable to open TFDI device: device not opened
jtag> cable ft2232 interface=1
Couldn't connect to suitable USB device.
Error: usbconn/libftd2xx.c:406 usbconn_ftd2xx_common_open() ftdi/ftd2xx error: Unable to open TFDI device: device not opened
jtag> cable ft2232 interface=1
Couldn't connect to suitable USB device.
Error: usbconn/libftd2xx.c:406 usbconn_ftd2xx_common_open() ftdi/ftd2xx error: Unable to open TFDI device: device not opened
jtag> cable ft2232 interface=1
Couldn't connect to suitable USB device.
Error: usbconn/libftd2xx.c:406 usbconn_ftd2xx_common_open() ftdi/ftd2xx error: Unable to open TFDI device: device not opened
jtag> cable ft2232 interface=1
Couldn't connect to suitable USB device.
Error: usbconn/libftd2xx.c:406 usbconn_ftd2xx_common_open() ftdi/ftd2xx error: Unable to open TFDI device: device not opened
jtag> cable ft2232 interface=1
Couldn't connect to suitable USB device.
Error: usbconn/libftd2xx.c:406 usbconn_ftd2xx_common_open() ftdi/ftd2xx error: Unable to open TFDI device: device not opened
jtag> cable ft2232 interface=1
Connected to libftd2xx driver.
jtag> bsdl path c:/bsdl
jtag> detect
IR length: 8
Chain length: 1
Device Id: 00000110111000011100000010010011 (0x06E1C093)
Filename: c:/bsdl/xc2c32a_vq44.bsd
jtag> svf c:/bbv2.svf progress stop
Parsing 660/664 ( 99%)
Scanned device output matched expected TDO values.
jtag>

[Martytoof]

When I run run.bat in the test folder, it also has trouble detecting the board after plug-in for approximately 20 or 30 seconds. After repeating the command perhaps a dozen times it finally detects both FTDI ports and successfully runs the selftest:

C:\Users\pk\Desktop\test_plan>run.bat

C:\Users\pk\Desktop\test_plan>BusPiratev2Test_VisualC++Express.exe -delay -n0
ERROR: FT_ListDevices

C:\Users\pk\Desktop\test_plan>pause
Press any key to continue . . .

C:\Users\pk\Desktop\test_plan>BusPiratev2Test_VisualC++Express.exe -delay -n0
Select device:
Device 0 (Serial Number:
Device 1 (Serial Number: B
FT_DEVICE_NOT_FOUND
ERROR: FT_OpenEx ()

C:\Users\pk\Desktop\test_plan>pause
Press any key to continue . . .

C:\Users\pk\Desktop\test_plan>run.bat

C:\Users\pk\Desktop\test_plan>BusPiratev2Test_VisualC++Express.exe -delay -n0
Select device:
Device 0 (Serial Number: A
Device 1 (Serial Number: B

======================================================
SUCCESS (Connected to the FTDI.A)
SUCCESS (reset)
SUCCESS (usb parameters set)
SUCCESS (event chars disabled)
SUCCESS (timeouts set)
SUCCESS (latency set)
SUCCESS (flow control disabled)
SUCCESS (MSSPE reset)
SUCCESS (MPSSE on)
START TESTING

======================================================
00000001 00000001
00000010 00000010
00000100 00000100
00001000 00001000
00010000 00010000
00100000 00100000
01000000 01000000
10000000 10000000
00000000 00000000
10101010 10101010
01010101 01010101
00000000 00000000
11111111 11111111
Testing complete, errors: 0

[ian]

Thanks for the followup. That is indicative of some problem.

First, I recommend reinstalling the latest FTDI drivers, well, just because. If that doesn't help, let's replace the board and see if that is any better.

[Martytoof]

Hi Ian,

No luck with newer drivers. How would I go about getting a replacement?

Thanks!

[ian]

Please write to Seeed and reference this post. I inspected 5 random bbv25 boards today (see if you get the boxes I signed :) ) and did notice some floating solder balls here and there. I think the contract manufacturer (not Seeed in house) used old or bad or wrong-alloy solder paste on some boards. It could have been the end or beginning of the tube or something. Anyways - there seems to be higher than usual defects on this batch of boards. We will of course replace any defects and you don't need to send the old board back to China.

[Martytoof]

Thanks again for all your help ian. My concerns about the documentation are easily outweighed by the stellar support you guys deliver :)

I will give Seed a buzz and hopefully that'll be the end of my issues.