mirror of
https://github.com/STMicroelectronics/STM32CubeF0.git
synced 2025-05-08 19:29:49 +08:00
115 lines
5.6 KiB
Plaintext
115 lines
5.6 KiB
Plaintext
/**
|
|
@page PWR_STOP Power Stop Mode Example
|
|
|
|
@verbatim
|
|
******************** (C) COPYRIGHT 2016 STMicroelectronics *******************
|
|
* @file PWR/PWR_STOP/readme.txt
|
|
* @author MCD Application Team
|
|
* @brief Description of the Power Stop Mode example.
|
|
******************************************************************************
|
|
*
|
|
* Redistribution and use in source and binary forms, with or without modification,
|
|
* are permitted provided that the following conditions are met:
|
|
* 1. Redistributions of source code must retain the above copyright notice,
|
|
* this list of conditions and the following disclaimer.
|
|
* 2. Redistributions in binary form must reproduce the above copyright notice,
|
|
* this list of conditions and the following disclaimer in the documentation
|
|
* and/or other materials provided with the distribution.
|
|
* 3. Neither the name of STMicroelectronics nor the names of its contributors
|
|
* may be used to endorse or promote products derived from this software
|
|
* without specific prior written permission.
|
|
*
|
|
* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
|
|
* AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
|
|
* DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
|
|
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
|
|
* SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
|
|
* CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
|
|
* OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
|
|
* OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|
*
|
|
******************************************************************************
|
|
@endverbatim
|
|
|
|
@par Example Description
|
|
|
|
How to enter the Stop mode and wake up from this mode by using the RTC wakeup
|
|
timer event or an interrupt.
|
|
|
|
In the associated software
|
|
- the system clock is set to 48 MHz
|
|
- the EXTI4_15 is configured to generate interrupt on falling edge
|
|
- the EXTI_Line22 connected internally to the RTC Wakeup event is configured
|
|
to generate an interrupt on rising edge each 4s
|
|
- the SysTick is programmed to generate an interrupt each 1 ms
|
|
In the SysTick interrupt handler, LED2 is toggled, this is used to indicate whether
|
|
the MCU is in STOP or RUN mode.
|
|
|
|
The system enters STOP mode and will wait for the RTC Wakeup event to be
|
|
generated each 4s, or Key push button is pressed.
|
|
- If the RTC WakeUp event (EXTI_Line20) is the source of wakeup from STOP, LED1 is toggled.
|
|
- If the Tamper push-button (EXTI4_15) is the source of wakeup from STOP, LED4 is toggled.
|
|
|
|
This behavior is repeated in an infinite loop.
|
|
|
|
LEDs are used to monitor the system state as following:
|
|
- LED1 toggled: system woken up from STOP using RTC WakeUp Interrupt
|
|
- LED2 toggling: system in RUN mode
|
|
- LED3 Initialization error (RTC, RCC,...)
|
|
- LED4 toggled: system woken up from STOP using EXTI4_15 (Tamper push-button)
|
|
|
|
@note To measure the current consumption in STOP mode, please refer to
|
|
@subpage PWR_CurrentConsumption example.
|
|
|
|
@note This example can not be used in DEBUG mode, this is due to the fact
|
|
that the Cortex-M0 core is no longer clocked during low power mode
|
|
so debugging features are disbaled
|
|
|
|
@note Care must be taken when using HAL_Delay(), this function provides accurate delay (in milliseconds)
|
|
based on variable incremented in SysTick ISR. This implies that if HAL_Delay() is called from
|
|
a peripheral ISR process, then the SysTick interrupt must have higher priority (numerically lower)
|
|
than the peripheral interrupt. Otherwise the caller ISR process will be blocked.
|
|
To change the SysTick interrupt priority you have to use HAL_NVIC_SetPriority() function.
|
|
|
|
@note The application need to ensure that the SysTick time base is always set to 1 millisecond
|
|
to have correct HAL operation.
|
|
|
|
@note Care must be taken when HAL_RCCEx_PeriphCLKConfig() is used to select the RTC clock source; in this
|
|
case the Backup domain will be reset in order to modify the RTC Clock source, as consequence RTC
|
|
registers (including the backup registers) and RCC_BDCR register are set to their reset values.
|
|
|
|
@par Directory contents
|
|
|
|
- PWR/PWR_STOP/Inc/stm32f0xx_conf.h HAL Configuration file
|
|
- PWR/PWR_STOP/Inc/stm32f0xx_it.h Header for stm32f0xx_it.c
|
|
- PWR/PWR_STOP/Inc/main.h Header file for main.c
|
|
- PWR/PWR_STOP/Src/system_stm32f0xx.c STM32F0xx system clock configuration file
|
|
- PWR/PWR_STOP/Src/stm32f0xx_it.c Interrupt handlers
|
|
- PWR/PWR_STOP/Src/main.c Main program
|
|
- PWR/PWR_STOP/Src/stm32f0xx_hal_msp.c HAL MSP module
|
|
|
|
@par Hardware and Software environment
|
|
|
|
- This example runs on STM32F072VB devices.
|
|
|
|
|
|
- This example has been tested with STMicroelectronics STM32072B-EVAL RevB board
|
|
and can be easily tailored to any other supported device and development board.
|
|
|
|
- STM32072B-EVAL Set-up
|
|
- Use LED1, LED2, LED3 and LED4 connected respectively to PD.08, PD.09, PD.10 and PD.11 pins
|
|
- Use the Tamper push-button connected to pin PC.13 (EXTI4_15)
|
|
|
|
@par How to use it ?
|
|
|
|
In order to make the program work, you must do the following :
|
|
- Open your preferred toolchain
|
|
- Rebuild all files and load your image into target memory
|
|
- Run the example
|
|
|
|
|
|
* <h3><center>© COPYRIGHT STMicroelectronics</center></h3>
|
|
*/
|