90 lines
		
	
	
		
			3.5 KiB
		
	
	
	
		
			Plaintext
		
	
	
	
			
		
		
	
	
			90 lines
		
	
	
		
			3.5 KiB
		
	
	
	
		
			Plaintext
		
	
	
	
| /**
 | |
|   @page PWR_STANDBY PWR standby example
 | |
|   
 | |
|   @verbatim
 | |
|   ******************** (C) COPYRIGHT 2016 STMicroelectronics *******************
 | |
|   * @file    PWR/PWR_STANDBY/readme.txt 
 | |
|   * @author  MCD Application Team
 | |
|   * @brief   Description of the PWR STANDBY example.
 | |
|   ******************************************************************************
 | |
|   * @attention
 | |
|   *
 | |
|   * Copyright (c) 2016 STMicroelectronics.
 | |
|   * All rights reserved.
 | |
|   *
 | |
|   * This software is licensed under terms that can be found in the LICENSE file
 | |
|   * in the root directory of this software component.
 | |
|   * If no LICENSE file comes with this software, it is provided AS-IS.
 | |
|   *
 | |
|   ******************************************************************************
 | |
|   @endverbatim
 | |
| 
 | |
| @par Example Description 
 | |
|  
 | |
| How to enter the Standby mode and wake up from this mode by using an external 
 | |
| reset or the WKUP pin.
 | |
| 
 | |
| This example shows also how to configure the stm32f1xx system to measure 
 | |
| STANDBY mode current consumption.
 | |
| 
 | |
| In the associated software
 | |
|   - the system clock is set to 64 MHz.
 | |
|   - PA.00 is configured to wake up the system after entering Standby mode.
 | |
|   - the SysTick is programmed to generate an interrupt each 1 ms.
 | |
|   
 | |
| The system enters STANDBY mode after 5s and will wait for injecting 3.3V on PA.00
 | |
| PWR_WAKEUP_PIN1. Current consumption could be monitored through an amperemeter connected to JP6.
 | |
| 
 | |
|     - STANDBY Mode 
 | |
|     ===============
 | |
|             - VREFINT OFF with fast wakeup enabled
 | |
|             - No IWDG
 | |
|             - Wakeup using PWR_WAKEUP_PIN1 (PA.00)
 | |
| 
 | |
| @note This example can not be used in DEBUG mode, this is due to the fact 
 | |
|       that the Cortex-M3 core is no longer clocked during low power mode 
 | |
|       so debugging features are disabled
 | |
| 
 | |
| @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.
 | |
| 
 | |
| @par Directory contents 
 | |
| 
 | |
|   - PWR/PWR_STANDBY/Inc/stm32f1xx_conf.h         HAL Configuration file
 | |
|   - PWR/PWR_STANDBY/Inc/stm32f1xx_it.h           Header for stm32f1xx_it.c
 | |
|   - PWR/PWR_STANDBY/Inc/main.h                   Header file for main.c
 | |
|   - PWR/PWR_STANDBY/Src/system_stm32f1xx.c       STM32F1xx system clock configuration file
 | |
|   - PWR/PWR_STANDBY/Src/stm32f1xx_it.c           Interrupt handlers
 | |
|   - PWR/PWR_STANDBY/Src/main.c                   Main program
 | |
| 
 | |
| @par Hardware and Software environment
 | |
| 
 | |
|   - STM32F103RB-Nucleo Set-up
 | |
|     - Wake-up will be done in putting 3.3V to PA.00 pin (present on pin28 of CN7).
 | |
|       Wired should be put between PA.00 and GND before running test. Connect to 3V3 to awake board.
 | |
|     - Connect an amperemeter to JP6 to measure the IDD current
 | |
| 
 | |
|   - This example runs on STM32F1xx devices
 | |
|       
 | |
|   - This example has been tested with STMicroelectronics STM32F103RB-Nucleo
 | |
|     evaluation board and can be easily tailored to any other supported device 
 | |
|     and development board.
 | |
| 
 | |
| @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
 | |
| 
 | |
| 
 | |
| 
 | |
|  */
 |