Skip to main content
Topic: 5.9 and 5.10 firmware still no OpenOCD? (Read 32808 times) previous topic - next topic

Re: 5.9 and 5.10 firmware still no OpenOCD?

Reply #15
Thanks, ds30 Loader GUI works for me on Windows, although I had to get the latest version from internet.

Re: 5.9 and 5.10 firmware still no OpenOCD?

Reply #16
[EDIT - removed last comment and supplied new info.]

So I basically got the same results as the other guys after updating to Firmware V6.0RC!!

$ openocd.exe -f bitpirate.cfg
Code: [Select]
Open On-Chip Debugger 0.5.0-dev-00858-g3c6af51-dirty (2011-04-21-20:38)
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
Info : Buspirate Interface ready!
Error: Translation from jtag_speed to khz not implemented
Info : adapter-specific clock speed value 0
Warn : There are no enabled taps.  AUTO PROBING MIGHT NOT WORK!!
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: IR capture error at bit 0, saw 0x00 not 0x...3
Warn : Bypassing JTAG setup events due to errors
Warn : gdb services need one or more targets defined
[HANG!]

I particularly don't like the error:
Quote
Error: Translation from jtag_speed to khz not implemented

I can accept the other errors as I am not connecting to anything and neither specifying a board... So instead I tried:

$ openocd -f bitpirate.cfg -f stm32.cfg -c "init"

Code: [Select]
Open On-Chip Debugger 0.5.0-dev-00858-g3c6af51-dirty (2011-04-21-20:38)
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
1000 kHz
adapter_nsrst_delay: 100
jtag_ntrst_delay: 100
cortex_m3 reset_config sysresetreq
Info : Buspirate Interface ready!
Error: Translation from jtag_speed to khz not implemented
Info : adapter-specific clock speed value 1000
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: stm32.cpu: IR capture error; saw 0x00 not 0x01
Warn : Bypassing JTAG setup events due to errors
Warn : Invalid ACK 0 in JTAG-DP transaction
Polling target failed, GDB will be halted. Polling again in 100ms
Polling target failed, GDB will be halted. Polling again in 300ms
Polling target failed, GDB will be halted. Polling again in 700ms
Polling target failed, GDB will be halted. Polling again in 1500ms
Polling target failed, GDB will be halted. Polling again in 3100ms
Polling target failed, GDB will be halted. Polling again in 6300ms
Polling target failed, GDB will be halted. Polling again in 6300ms
Polling target failed, GDB will be halted. Polling again in 6300ms
...
[CTRL-C]
And this seem to work, since it is very similar to the result from one of the comments here:
https://michaldemin.wordpress.com/2010/ ... d-openocd/
although I don't know for sure since I don't have any (supported) board to try it with...

Does anyone know where I can get a OpenOCD config file to some (any really) Broadcom 63xx board? Google didn't give me a jack...

Re: 5.9 and 5.10 firmware still no OpenOCD?

Reply #17
Hi,
It's very nice to state the gui loader does not have a problem but that does not help me running linux which does not have a gui so is there any way to load the openocd enabled firmware under linux i.e what to do about error

thanks
Frits

Re: 5.9 and 5.10 firmware still no OpenOCD?

Reply #18
Hi,
I knew as soon as I ask the question I'll find the answer. It was in the development section apparently pirate-loader uses uppercase and the hex file has lower case so just change it with the following and pirate-loader is happy.

cat busPirate.production.hex |tr a-f A-F>  busPirate.production2.hex

Thanks
Frits

Re: 5.9 and 5.10 firmware still no OpenOCD?

Reply #19
[quote author="ian"]As far as I know openOCD support is in 5.9 and at least 5.10.  If it is commented in SVN it is probably for development reasons, but should not be removed from an actual release as far as I know.[/quote]

After a couple days' frustration I downloaded a bunch of firmware images and tested them each. It's in 5.8, but it's not in 5.9 or 5.10. If you look in SVN, you can see that openOCD support was commented out in revision 524, which was between the 5.8 and 5.9 releases. Which explains why nobody can get it to work: it's not there!

I added a list of versions to the wiki page, so that people will hopefully spend less time trying to use the broken firmware.

Re: 5.9 and 5.10 firmware still no OpenOCD?

Reply #20
Thanks for the investigation and sorry for the frustration caused. It should be enabled in v6+ though right?
Got a question? Please ask in the forum for the fastest answers.

Re: 5.9 and 5.10 firmware still no OpenOCD?

Reply #21
I know this topic is ooold, but this was my first result on many google searchs and this info may be useful for some.

OpenOCD is still not enabled on the latest releases nor SVN, so i downloaded everything and compiled the latest SVN with OpenOCD enabled. I flashed this with the pirate-loader.exe tool without any issue on a Bus Pirate v3a + Bootloader v4.4. I hope that this helps someone trying to get this working.

Edit: The attached firmware is Firmware v6.0RC (r612)

Re: 5.9 and 5.10 firmware still no OpenOCD?

Reply #22
Given the above observations, the top remark on the JTAG wiki page is also quite confusing:

Quote
NOTE: As of v5.9 the JTAG terminal library was moved to the Bus Pirate bonus/extras firmware.

Bus Pirate firmware v5+ (main firmware) includes support for the OpenOCD JTAG debugger instead, this is a much better option.

AFAIK, there is no JTAG support (neither openocd or terminal) support in the 5.9 extras firmware. Also, as the list added by wiml to this wiki page shows, the second statement is also untrue (at least not for 5.9 and above).

I would like to correct this, but I can't really document this properly unless I know what the plans for subsequent firmware updates are. Ian?

Re: 5.9 and 5.10 firmware still no OpenOCD?

Reply #23
Another note: I've been trying to get the JTAG _terminal_ mode working, but it seems that one is gone from the firmwares for a long time now (I've tried 5.0, 5.4, 5.8, 5.9 and 5.10, none of which seem to contain the JTAG terminal mode...). I guess I'll have to dive into openocd, then.

Re: 5.9 and 5.10 firmware still no OpenOCD?

Reply #24
One more observation: The 6.0 and 6.1 firmwares _do_ contain the binary JTAG mode, as promised. I've added these to the table in the wiki.