MCBSTM32EXL Keil, MCBSTM32EXL Datasheet - Page 967

• Manufacturer Part Number: MCBSTM32EXL
• Description: BOARD EVALUATION FOR STM32F103ZE
• Manufacturer: Keil

Specifications of MCBSTM32EXL

• Lead Free Status / RoHS Status: Lead free / RoHS Compliant

RM0008
Note:
29.11
Note:
29.12
Important: these registers are not reset by a system reset. They are only reset by a power-
on reset.
Refer to the Cortex-M3 r1p1 TRM for further details.
To Halt on reset, it is necessary to:
●
●
Capability of the debugger host to connect under system
reset
The STM32F10xxx MCU reset system comprises the following reset sources:
●
●
●
●
The Cortex-M3 differentiates the reset of the debug part (generally PORRESETn) and the
other one (SYSRESETn)
This way, it is possible for the debugger to connect under System Reset, programming the
Core Debug Registers to halt the core when fetching the reset vector. Then the host can
release the system reset and the core will immediately halt without having executed any
instructions. In addition, it is possible to program any debug features under System Reset.
It is highly recommended for the debugger host to connect (set a breakpoint in the reset
vector) under system reset.
FPB (Flash patch breakpoint)
The FPB unit:
●
●
The use of a Software Patch or a Hardware Breakpoint is exclusive.
The FPB consists of:
●
●
enable the bit0 (VC_CORRESET) of the Debug and Exception Monitor Control
Register
enable the bit0 (C_DEBUGEN) of the Debug Halting Control and Status Register.
POR (power-on reset) which asserts a RESET at each power-up.
Internal watchdog reset
Software reset
External reset
implements hardware breakpoints
patches code and data from code space to system space. This feature gives the
possibility to correct software bugs located in the Code Memory Space.
2 literal comparators for matching against literal loads from Code Space and remapping
to a corresponding area in the System Space.
6 instruction comparators for matching against instruction fetches from Code Space.
They can be used either to remap to a corresponding area in the System Space or to
generate a Breakpoint Instruction to the core.
Doc ID 13902 Rev 9
Debug support (DBG)
967/995