Sorry but I only know stm32x... could you pls give a name to the "other one"?
cd src
find . | grep stm32
--
Øyvind Harboe
Can Zylin Consulting help on your project?
US toll free 1-866-980-3434 / International +47 51 87 40 27
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
=========================
I encountered the same problem while attempting to configure openocd for
use with the STM3220G-EVAL kit.
I believe this is the same kit mentioned in other posts about the
STM32F207 part.
A possible confusion point is how to configure the target driver.
As Oyvind indicated, there are several built-in STM flash drivers in
openocd.
* The "stmx" for the STM32F10x parts (default).
* The new "stm32f2xxx" for the STM32F20x parts.
The problem I encountered was, "How to select the new stm32f2xxx driver
in my private openocd script?".
My solution follows.
It's possible not the best, but it allowed me to use gdb to connect to
the eval-board.
* Go to the directory /usr/local/share/openocd/scripts/target
* Copy stmx.cfg to stm32f2xxx.cfg (may need root priv.)
* Edit the new stm32f2xxx.cfg file (may need root priv.)
* find "stmx", about 7 or so lines from the bottom of file.
* change "stmx" to "stm32f2xxx"
* save file.
* In your private run script, make the following change.
* find "source [find target/stm32x.cfg]"
* change to "src [find target/stm32f2xxx.cfg]"
* save file.
* Start openocd with your private script (above).
* Start gdb using "gdb -ex 'target remote :3333' "
You should now see that gdb connects to openocd.
You can now interact with the STM32F207 running (for example) the demo
program.
NOTE: The above method only addresses the problems of gdb access. not
writing flash.
I believe that the writing flash issues have been covered in other threads.
If the above method is significantly wrong, could someone please
describe in detail how it should be done.
BR
Robin Callender
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
