Difference between revisions of "ST STM32F2"
m (Fabian moved page STM32F2 to ST STM32F2: Device family articles are supposed to be named <VendorName> <FamilyName>) |
(→Debug specific) |
||
| Line 26: | Line 26: | ||
== Debug specific == |
== Debug specific == |
||
| + | Please refer to the [[ST_STM32#Device_specific_connect | general STM32 article]] |
||
| − | * If no connection can be established the J-Link will try to connect to the device via a connect under reset. |
||
| − | * On connect, some DBGMCU registers will be written to |
||
| − | ** freeze the watchdogs during halt to prevent unintended resets while debugging. |
||
| − | ** prevent the debug connection from breaking after the CPU enters deepsleep. |
||
| − | * When closing the J-Link connection, the DBGMCU registers are reset. |
||
== Securing/unsecuring the device == |
== Securing/unsecuring the device == |
||
Latest revision as of 16:28, 21 November 2022
This article describes device specifics of the ST STM32F2 series devices. The STM32F2 devices are Cortex-M3 based MCUs with low-power functionality.
Internal Flash
The following flash regions are supported by J-Link.
| Device | Range | Total size |
|---|---|---|
| STM32F2xxxB | 0x0800_0000 - 0x0801_FFFF | 128 KB |
| STM32F2xxxC | 0x0800_0000 - 0x0803_FFFF | 256 KB |
| STM32F2xxxE | 0x0800_0000 - 0x0807_FFFF | 512 KB |
| STM32F2xxxF | 0x0800_0000 - 0x080B_FFFF | 768 KB |
| STM32F2xxxG | 0x0800_0000 - 0x080F_FFFF | 1024 KB |
| All (opt. bytes) | 0x1FFF_C000 - 0x1FFF_C00F | 16 bytes |
Reset
For the STM32F2 devices, the Cortex-M default reset strategy is used.
Debug specific
Please refer to the general STM32 article
Securing/unsecuring the device
Please refer to the related article here.
