aboutsummaryrefslogtreecommitdiff
path: root/examples
diff options
context:
space:
mode:
authorPiotr Esden-Tempski2010-01-22 17:48:16 +0100
committerPiotr Esden-Tempski2010-01-25 17:32:35 +0100
commit6ca739296d4d995ce0a17ec787b715e4807991f4 (patch)
tree8d29e85adcfc0b6b35bf41a36513c195f396a524 /examples
parentbc46b3118e06c88413242ded8da353258253ee86 (diff)
Updated example README files.
Diffstat (limited to 'examples')
-rw-r--r--examples/MB525/fancyblink/README7
-rw-r--r--examples/STM32-H103/fancyblink/README3
-rw-r--r--examples/STM32-H103/miniblink/README3
-rw-r--r--examples/STM32-H103/usart/README3
4 files changed, 6 insertions, 10 deletions
diff --git a/examples/MB525/fancyblink/README b/examples/MB525/fancyblink/README
index cd58a02..8b3b732 100644
--- a/examples/MB525/fancyblink/README
+++ b/examples/MB525/fancyblink/README
@@ -4,7 +4,7 @@ README
This is a blink example program using libopenstm32.
-It's intended for the ST STM32-based Olimex MB525 eval board (see
+It's intended for the ST STM32-based MB525 eval board (see
http://www.st.com/stonline/products/literature/um/13472.htm for details). It
should blink the LED on the board.
@@ -30,7 +30,7 @@ For a more verbose build you can use
Flashing
--------
-You can flash the generated code on the STM32-H103 board using OpenOCD:
+You can flash the generated code on the MB525 board using OpenOCD:
$ make flash
@@ -38,9 +38,8 @@ Or you can do the same manually via:
$ openocd -f interface/jlink.cfg -f board/olimex_stm32_h103.cfg
$ telnet localhost 4444
- > init
> reset halt
- > flash write_image erase fancyblink.bin 0x08000000
+ > flash write_image erase fancyblink.hex
> reset
Replace the "jlink.cfg" with whatever JTAG device you are using, and/or
diff --git a/examples/STM32-H103/fancyblink/README b/examples/STM32-H103/fancyblink/README
index 706e07e..8e7adce 100644
--- a/examples/STM32-H103/fancyblink/README
+++ b/examples/STM32-H103/fancyblink/README
@@ -38,9 +38,8 @@ Or you can do the same manually via:
$ openocd -f interface/jtagkey-tiny.cfg -f board/olimex_stm32_h103.cfg
$ telnet localhost 4444
- > init
> reset halt
- > flash write_image erase fancyblink.bin 0x08000000
+ > flash write_image erase fancyblink.hex
> reset
Replace the "jtagkey-tiny.cfg" with whatever JTAG device you are using, and/or
diff --git a/examples/STM32-H103/miniblink/README b/examples/STM32-H103/miniblink/README
index a0fc0ee..88278d9 100644
--- a/examples/STM32-H103/miniblink/README
+++ b/examples/STM32-H103/miniblink/README
@@ -38,9 +38,8 @@ Or you can do the same manually via:
$ openocd -f interface/jtagkey-tiny.cfg -f board/olimex_stm32_h103.cfg
$ telnet localhost 4444
- > init
> reset halt
- > flash write_image erase miniblink.bin 0x08000000
+ > flash write_image erase miniblink.hex
> reset
Replace the "jtagkey-tiny.cfg" with whatever JTAG device you are using, and/or
diff --git a/examples/STM32-H103/usart/README b/examples/STM32-H103/usart/README
index 59d1d89..cbb0db2 100644
--- a/examples/STM32-H103/usart/README
+++ b/examples/STM32-H103/usart/README
@@ -38,9 +38,8 @@ Or you can do the same manually via:
$ openocd -f interface/jtagkey-tiny.cfg -f board/olimex_stm32_h103.cfg
$ telnet localhost 4444
- > init
> reset halt
- > flash write_image erase usart.bin 0x08000000
+ > flash write_image erase usart.hex
> reset
Replace the "jtagkey-tiny.cfg" with whatever JTAG device you are using, and/or