Ten minutes and a cup of tea later, and I've already detected the scan chain and have read access to the memory map of the device. Happy hacking indeed :-)
I tried the last suggestion, and enabled debugging on openocd - I have snipped the opening setup and just copied the buspirate-specific bit at the end:
It seems that there was a response to the initial mode change, but then something gave up partway through. Does this mean anything? I'm seeing the 20x00, followed by BBIO1, but this seems to be being sent twice. It doesn't entirely match with what I'd expect from the documentation...
Is there any way I can manually step through the connection steps that OpenOCD? Or is there some other way of debugging why I might not be getting a response?
I have just received my new bus-pirate, and upgraded it to the latest firmware. All good so far. I would like to use it with OpenOCD and an STM32 chip. I decided to see if OpenOCD would recognise it before I hooked it up to my development board. However, whenever I run openocd and point it to the interface configuration file I get the following error:
Open On-Chip Debugger 0.5.0-dev-00615-g8902789 (2010-11-25-22:11) Licensed under GNU GPL v2 For bug reports, read http://openocd.berlios.de/doc/doxygen/bugs.html Warn : Adapter driver 'buspirate' did not declare which transports it allows; assuming legacy JTAG-only Info : only one transport option; autoselect 'jtag' srst_only separate srst_gates_jtag srst_open_drain Error: Error sending data Error: Buspirate did not respond restart everything
Should I expect it to be able to connect without a target connected? Or have I missed some other step?