![Ronetix PEEDI User Manual Download Page 64](http://html1.mh-extra.com/html/ronetix/peedi/peedi_user-manual_1485040064.webp)
Using PEEDI
Example:
http://download.ronetix.at/peedi/cfg_examples/coldfire/mcf5282.cfg
Freescale MPC5000 programming
Example:
http://download.ronetix.at/peedi/cfg_examples/powerpc/mpc5554.cfg
ST STM32 programming
In the STM32 microcontrollers, the FLASH may be write-protected. The protection is set using the
STM32 option bytes. Option bytes are used to configure also other STM32 CPU settings - for more
information see the STM32F10xxx Flash programming.
For managing STM32 option bytes, PEEDI has the
flash this option
command. To erase all option
bytes use f
lash this option erase
. To write a single option byte, use
flash this option BYTE
VALUE
. An option byte can be written only once after it is erased. If you want to change the value
of previously written byte you must erase it - this will erase all other option values, so you may
need to set them again.
Example:
http://download.ronetix.at/peedi/cfg_examples/cortex-m/stm32.cfg
ST STR7 programming
In the STR7 microcontrollers, several memory regions may be mapped at address 0x00000000,
including the internal FLASH. So these are the acceptable values for the BASE_ADDR parameter
in the FLASH section:
•
0x00000000 (STR71x and STR73x)
•
0x40000000 (STR71x)
•
0x80000000 (STR73x)
If the SECURE_FLASH target configuration parameter is set to YES. The first time, the device is
secured by programming the DBGP bit of the NVAPR0 register. Each time after, the device is
secured programming the next un-programmed bit PEN bit of the NVAPR1 register.
Keep in mind that once secured, the device may be temporary or permanently unsecured only by the
code that is programmed in the FLASH, so avoid securing the device if the code inside it can not
unlock it, because the devise may become unusable.
PEEDI User’s Manual
64