Mercurial > ~darius > hgwebdir.cgi > stm32temp

comparison libs/STM32F10x_StdPeriph_Lib_V3.5.0/Project/STM32F10x_StdPeriph_Examples/PWR/STANDBY/readme.txt @ 0:c59513fd84fb

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Initial commit of STM32 test code.
author Daniel O'Connor <darius@dons.net.au>
date Mon, 03 Oct 2011 21:19:15 +1030
parents
children
comparison
equal deleted inserted replaced
-1:000000000000 0:c59513fd84fb
1 /**
2 @page PWR_STANDBY PWR STANDBY example
3
4 @verbatim
5 ******************** (C) COPYRIGHT 2011 STMicroelectronics *******************
6 * @file PWR/STANDBY/readme.txt
7 * @author MCD Application Team
8 * @version V3.5.0
9 * @date 08-April-2011
10 * @brief Description of the PWR STANDBY example.
11 ******************************************************************************
12 * THE PRESENT FIRMWARE WHICH IS FOR GUIDANCE ONLY AIMS AT PROVIDING CUSTOMERS
13 * WITH CODING INFORMATION REGARDING THEIR PRODUCTS IN ORDER FOR THEM TO SAVE
14 * TIME. AS A RESULT, STMICROELECTRONICS SHALL NOT BE HELD LIABLE FOR ANY
15 * DIRECT, INDIRECT OR CONSEQUENTIAL DAMAGES WITH RESPECT TO ANY CLAIMS ARISING
16 * FROM THE CONTENT OF SUCH FIRMWARE AND/OR THE USE MADE BY CUSTOMERS OF THE
17 * CODING INFORMATION CONTAINED HEREIN IN CONNECTION WITH THEIR PRODUCTS.
18 ******************************************************************************
19 @endverbatim
20
21 @par Example Description
22
23 This example shows how to enters the system to STANDBY mode and wake-up from this
24 mode using: external RESET, RTC Alarm or WKUP pin.
25
26 In the associated software, the system clock is set to 24 MHz on Value line devices
27 and to 72 MHz on other devices using the external high speed oscillator(HSE), an EXTI line
28 is configured to generate an interrupt on falling edge and the SysTick is programmed
29 to generate an interrupt each 250 ms. In the SysTick interrupt handler, the LED1 is
30 toggled, this is used to indicate whether the MCU is in STANDBY or RUN mode.
31
32 When a falling edge is detected on the EXTI line an interrupt is generated. In the
33 EXTI handler routine the RTC is configured to generate an Alarm event in 3 second
34 then the system enters STANDBY mode causing the LED1 to stop toggling.
35 A rising edge on WKUP pin or an external RESET will wake-up the system from
36 STANDBY. If within 3 second neither rising edge on WKUP pin nor external RESET
37 are generated, the RTC Alarm will wake-up the system.
38
39 After wake-up from STANDBY mode, program execution restarts in the same way as after
40 a RESET, the LED1 restarts toggling, LED2 is turned on and the RTC configuration
41 (clock source, enable, prescaler,...) is kept.
42 As result there is no need to configure the RTC.
43
44 Two leds LED1 and LED2 are used to monitor the system state as following:
45 - LED1 toggling: system in RUN mode
46 - LED1 off / LED2 off: system in STANDBY mode
47 - LED2 on: system resumed from STANDBY mode
48
49 @par Directory contents
50
51 - PWR/STANDBY/stm32f10x_conf.h Library Configuration file
52 - PWR/STANDBY/stm32f10x_it.c Interrupt handlers
53 - PWR/STANDBY/stm32f10x_it.h Header for stm32f10x_it.c
54 - PWR/STANDBY/main.c Main program
55 - PWR/STANDBY/system_stm32f10x.c STM32F10x system source file
56
57 @par Hardware and Software environment
58
59 - This example runs on STM32F10x Connectivity line, High-Density, High-Density
60 Value line, Medium-Density, XL-Density, Medium-Density Value line, Low-Density
61 and Low-Density Value line Devices.
62
63 - This example has been tested with STMicroelectronics STM32100E-EVAL (High-Density
64 Value line), STM32100B-EVAL (Medium-Density Value line), STM3210C-EVAL (Connectivity line),
65 STM3210E-EVAL (High-Density and XL-Density) and STM3210B-EVAL (Medium-Density)
66 evaluation boards and can be easily tailored to any other supported device
67 and development board.
68 To select the STMicroelectronics evaluation board used to run the example,
69 uncomment the corresponding line in stm32_eval.h file (under Utilities\STM32_EVAL)
70
71 - STM32100E-EVAL Set-up
72 - Use LED1 and LED2 connected respectively to PF.06 and PF.07 pins
73 - Use the Key push-button connected to pin PG.08 (EXTI Line8).
74 - Use the Wakeup push-button connected to WKUP(PA.00) pin
75
76 - STM32100B-EVAL Set-up
77 - Use LED1 and LED2 connected respectively to PC.06 and PC.07 pins
78 - Use the Key push-button connected to pin PB.09 (EXTI Line9).
79 - Use the Wakeup push-button connected to WKUP(PA.00) pin
80
81 - STM3210C-EVAL Set-up
82 - Use LED1 and LED2 connected respectively to PD.07 and PD.13 pins
83 - Use the Key push-button connected to pin PB.09 (EXTI Line9).
84 - Use the Wakeup push-button connected to WKUP(PA.00) pin, make sure
85 that jumper JP14 is in position 2-3.
86
87 - STM3210E-EVAL Set-up
88 - Use LED1 and LED2 connected respectively to PF.06 and PF.07 pins
89 - Use the Key push-button connected to pin PG.08 (EXTI Line8).
90 - Use the Wakeup push-button connected to WKUP(PA.00) pin
91 @note the jumper JP4 must be not fit to be able to use the Wakeup push-button
92
93 - STM3210B-EVAL Set-up
94 - Use LED1 and LED2 connected respectively to PC.06 and PC.07 pins
95 - Use the Key push-button connected to pin PB.09 (EXTI Line9).
96 - Use the Wakeup push-button connected to WKUP(PA.00) pin
97
98 @note For power consumption measurement in STANDBY mode, you have to replace
99 jumper JP9 in the STM3210B-EVAL board, JP12 in the STM3210E-EVAL or
100 JP23 (position 1-2) in the STM3210C-EVAL board by an amperemeter.
101
102
103 @par How to use it ?
104
105 In order to make the program work, you must do the following :
106 - Copy all source files from this example folder to the template folder under
107 Project\STM32F10x_StdPeriph_Template
108 - Open your preferred toolchain
109 - Rebuild all files and load your image into target memory
110 - Run the example in standalone mode (without debugger connection)
111
112 @note
113 - Low-density Value line devices are STM32F100xx microcontrollers where the
114 Flash memory density ranges between 16 and 32 Kbytes.
115 - Low-density devices are STM32F101xx, STM32F102xx and STM32F103xx
116 microcontrollers where the Flash memory density ranges between 16 and 32 Kbytes.
117 - Medium-density Value line devices are STM32F100xx microcontrollers where
118 the Flash memory density ranges between 64 and 128 Kbytes.
119 - Medium-density devices are STM32F101xx, STM32F102xx and STM32F103xx
120 microcontrollers where the Flash memory density ranges between 64 and 128 Kbytes.
121 - High-density Value line devices are STM32F100xx microcontrollers where
122 the Flash memory density ranges between 256 and 512 Kbytes.
123 - High-density devices are STM32F101xx and STM32F103xx microcontrollers where
124 the Flash memory density ranges between 256 and 512 Kbytes.
125 - XL-density devices are STM32F101xx and STM32F103xx microcontrollers where
126 the Flash memory density ranges between 512 and 1024 Kbytes.
127 - Connectivity line devices are STM32F105xx and STM32F107xx microcontrollers.
128
129 * <h3><center>&copy; COPYRIGHT 2011 STMicroelectronics</center></h3>
130 */