edit1 Q was shorted>
Hello,
I'm new user at Yagarto toolchain.
I bought Bus Blaster v2 and I want to use it to program (flash) STM32F103RB target.
I follow the checklist given by the guide:
"Using_Open_Source_Tools_for_AT91SAM7S_Cross_Development_revision_C.pdf" (James P. Lynch).
Now I stand at the point:
------------------------
I want program the STM32F103RB target (olimex board). I think it is done by adding "program" rule to "makefile" as the guide says. But it doesn't work. There is an "openocd-flash-program.cfg". Where could I get it please? Next question: Is there a guide how to set the toolchain (eclipse) to work with Bus Blaster v2 as debug tool for STM32 target? Could anyone point me please to correct makefile for "program" and "debug"?
Hi frpr,
Is there a guide how to set the toolchain (eclipse) to work with Bus Blaster v2 as debug tool for STM32 target? Could anyone point me please to correct makefile for "program" and "debug"?
I don't know of any yet. The Bus Blaster v2 is a common JTAGkey compatible programmer by default, so any tutorial that uses a JTAGkey should work for Bus Blaster v2 without any changes.
There is an "openocd-flash-program.cfg". Where could I get it please?
I'm sorry, I don't know where to get this file. I have had problems myself with OpenOCD missing example files discussed in the documentation. Probably the best answer will come from the OpenOCD mailing list, they are very active and usually reply to all emails.
Thank you for the reply,
I ended up with working BusBlaster v2 under WinXP under Cygwin. I simply copy the BB2 config from "dangerousprototypes.com" to
"myWinHome/openocd/tcl/interface/busblaster.cfg". Now it works fine.
$openocd -f ../tcl/interface/busblaster.cfg -f ../tcl/target/stm32f1x.cfg. Im going to setup the yagarto IDE to co-operate with OOCD and GDB but I don't know how to do it. Anyway the BusBlaster v2 is great and cheap tool.
As a suggestion, it would help if there were lists of known working setups linked to all Bus Blaster device pages, the V3 seems particularly confusing from this perspective.