Re: [OpenOCD-user] Bus Blaster stuck in mpsse_flush()

[Tommy M. <tom...@ho...>]

Collect a verbose log using -d?
________________________________
From: Con Pistiolis <co...@kp...>
Sent: Friday, March 20, 2020 2:51:01 PM
To: ope...@li... <ope...@li...>
Subject: [OpenOCD-user] Bus Blaster stuck in mpsse_flush()

Hi,

I've just got a Bus Blaster v3c but I can't get it to work with OpenOCD.
I have tried interface/ftdi/dp_busblaster.cfg for jtag and interface/ftdi/dp_busblaster_kt-link.cfg for SWD with no luck.

Using the stock openocd of ubuntu 18.10 (version 0.10.0) or one built from git (as of today 0.10.0+dev-01137-g140fe7f7-dirty (2020-03-20-19:26) and have also tried some random older versions of git), it always gets stuck after opening ports 4444 and 6666, with no gdb interface, while if I connect via telnet it's dead.

With Ubuntu's version I see no error message, but when using my custom built version I see this:


bin/openocd -f share/openocd/scripts/interface/ftdi/dp_busblaster_kt-link.cfg -c "transport select swd" -f share/openocd/scripts/target/at91samdXX.cfg

Open On-Chip Debugger 0.10.0+dev-01137-g140fe7f7-dirty (2020-03-20-19:26)

Licensed under GNU GPL v2

For bug reports, read

        http://openocd.org/doc/doxygen/bugs.html

Info : FTDI SWD mode enabled

swd

Info : Listening on port 6666 for tcl connections

Info : Listening on port 4444 for telnet connections

Info : clock speed 400 kHz

Warn : Haven't made progress in mpsse_flush() for 2069ms.

Warn : Haven't made progress in mpsse_flush() for 4109ms.

....

which goes on forever... and when I interrupt it (with ^C) I get:


Error: libusb_handle_events() failed with LIBUSB_ERROR_INTERRUPTED

Error: MPSSE failed


and then a segmentation fault.


I had the same behaviour when trying to use jtag mode on a Microchip ATSAMA5D27-SOM1 module, both on a custom board and on an official ATSAMA5D27-SOM1-EK development board, but I'm not sure if this target is supported properly.


Any ideas?


Thanks in advance,
Con