80 lines
3.4 KiB
Plaintext
80 lines
3.4 KiB
Plaintext
/**
|
|
@page PWR_PVD PWR Programmable Voltage Detector (PVD) example
|
|
|
|
@verbatim
|
|
******************** (C) COPYRIGHT 2016 STMicroelectronics *******************
|
|
* @file PWR/PWR_PVD/readme.txt
|
|
* @author MCD Application Team
|
|
* @brief Description of the PWR Programmable Voltage Detector (PVD) 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 configure the programmable voltage detector by using an external interrupt
|
|
line. External DC supply must be used to supply Vdd.
|
|
|
|
In this example, EXTI line 16 is configured to generate an interrupt on each rising
|
|
or falling edge of the PVD output signal (which indicates that the Vdd voltage is
|
|
moving below or above the PVD threshold). As long as the voltage is above the
|
|
target threshold (2.5V), LED1 is blinking with a 200 ms-period; when the voltage drops
|
|
below the threshold, LED1 stops blinking and remains constantly on (or appears
|
|
to be turned off if the voltage is getting really low); when the voltage moves back
|
|
above the target threshold, LED1 starts blinking again.
|
|
If LED3 is on, it means that the system has generated an error.
|
|
|
|
@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_PVD/Inc/stm32f1xx_hal_conf.h HAL Configuration file
|
|
- PWR/PWR_PVD/Inc/stm32f1xx_it.h Header for stm32f1xx_it.c
|
|
- PWR/PWR_PVD/Inc/main.h Header file for main.c
|
|
- PWR/PWR_PVD/Src/system_stm32f1xx.c STM32F1xx system clock configuration file
|
|
- PWR/PWR_PVD/Src/stm32f1xx_it.c Interrupt handlers
|
|
- PWR/PWR_PVD/Src/main.c Main program
|
|
|
|
@par Hardware and Software environment
|
|
|
|
- This example runs on STM32F103xG devices
|
|
|
|
- This example has been tested with STMicroelectronics STM3210E-EVAL RevD
|
|
board and can be easily tailored to any other supported device
|
|
and development board.
|
|
|
|
- STM3210E-EVAL RevD Set-up
|
|
To apply an external power supply input, the user can resort to
|
|
pin 69 (3V3) of the daughter board extension connector CN10 and any GND pin
|
|
of the same connector (pin 1, 19 or 39)
|
|
Next,
|
|
- LED1 (GREEN) connected to PF.06 pin indicates the behavior of
|
|
the test software as explained above.
|
|
|
|
@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
|
|
|
|
|
|
|
|
*/
|