Difference between revisions of "Setting read out protection on STM32F0 devices"
(Created page with "The STM32F0 series devices have different levels of read protection. The level of read protection has to be specified in the RDP byte which is part of the option bytes at addr...") |
|||
| Line 1: | Line 1: | ||
| − | The STM32F0 series devices have different levels of read protection. The level of read protection has to be specified in the RDP byte which is part of the option bytes at address 0x1FFFF800. A special sequence, persisting of different read / write accesses to special function registers are required to change the value of the RDP byte ( |
+ | The STM32F0 series devices have different levels of read protection. The level of read protection has to be specified in the RDP byte which is part of the option bytes at address 0x1FFFF800. A special sequence, persisting of different read / write accesses to special function registers are required to change the value of the RDP byte (examples below). |
The table below describes the different configuration options: |
The table below describes the different configuration options: |
||
Revision as of 11:44, 26 November 2015
The STM32F0 series devices have different levels of read protection. The level of read protection has to be specified in the RDP byte which is part of the option bytes at address 0x1FFFF800. A special sequence, persisting of different read / write accesses to special function registers are required to change the value of the RDP byte (examples below).
The table below describes the different configuration options:
| RDP byte value | RDP complement value | Read protection level |
|---|---|---|
| 0xAA | 0x55 | Level 0 - No protection |
| ((!= 0xAA) && (!= 0xCC)) | Any value | Level 1 (default) - Read protection |
| 0xCC | 0x33 | Level 2 - No debug access |
Script files and sample projects
J-Link Commander:
J-Flash:
