Mode Entry Module (MC_ME) RM0046
172/936 Doc ID 16912 Rev 5
SAFE (on SAFE mode request), or DRUN (on reset), and an invalid mode interrupt is not
generated.
This mode is intended as a first-level low-power mode with
â—Ź the core clock frozen
â—Ź only a few peripherals running
and to be used by software
â—Ź to wait until it is required to do something and then to react quickly (i.e., within a few
system clock cycles of an interrupt event)
STOP0 Mode
The device enters this mode on the following events:
● from one of the RUN0…3 modes when the TARGET_MODE bit field of the ME_MCTL
register is written with “1010”.
As soon as any of the above events has occurred, a STOP0 mode transition request is
generated. The mode configuration information for this mode is provided by the
ME_STOP0_MC register. This mode is fully configurable, and the ME_STOP0_MC register
should be programmed according to the system needs. The following clock sources are
switched off in this mode:
â—Ź the system PLL
The flashes can be put in power-down mode as needed. If there is a STOP0 mode request
while any interrupt or wakeup event is active, the transition to STOP0 is aborted with the
resultant mode being the current mode, SAFE (on SAFE mode request), or DRUN (on
reset), and an invalid mode interrupt is not generated.
This can be used as an advanced low-power mode with the core clock frozen and almost all
peripherals stopped.
This mode is intended as an advanced low-power mode with
â—Ź the core clock frozen
â—Ź almost all peripherals stopped
and to be used by software
â—Ź to wait until it is required to do something with no need to react quickly (e.g., allow for
system clock source to be re-started)
This mode can be used to stop all clock sources and thus preserve the device status. When
exiting the STOP0 mode, the 16 MHz internal RC oscillator clock is selected as the system
clock until the target clock is available.
6.4.3 Mode Transition Process
The process of mode transition follows the following steps in a pre-defined manner
depending on the current device mode and the requested target mode. In many cases of
mode transition, not all steps need to be executed based on the mode control information,
and some steps may not be applicable according to the mode definition itself.
Target Mode Request
The target mode is requested by accessing the ME_MCTL register with the required keys.
This mode transition request by software must be a valid request satisfying a set of pre-