Mercurial > ~darius > hgwebdir.cgi > stm32temp

comparison libs/STM32F10x_StdPeriph_Lib_V3.5.0/Project/STM32F10x_StdPeriph_Examples/PWR/STOP/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_STOP PWR STOP example
3
4 @verbatim
5 ******************** (C) COPYRIGHT 2011 STMicroelectronics *******************
6 * @file PWR/STOP/readme.txt
7 * @author MCD Application Team
8 * @version V3.5.0
9 * @date 08-April-2011
10 * @brief Description of the PWR STOP 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 enter the system to STOP mode and wake-up using EXTI
24 Line interrupts. The EXTI Line sources are PB.09/PG.08 and RTC Alarm.
25
26 The EXTI line9/8 is configured to generate interrupt on falling edge.
27 The EXTI line17(RTC Alarm) is configured to generate interrupt on rising edge and
28 the RTC time base is set to 1 second using the external low speed oscillator(LSE).
29
30 The system clock is set to 24 MHz on Value line devices and to 72 MHz on other
31 devices using the external high speed oscillator(HSE).
32
33 The system enters and exits STOP mode as following:
34 After 2 second from system start-up, the RTC is configured to generate an Alarm
35 event in 3 second then the system enters STOP mode. To wake-up from STOP mode you
36 have to apply a rising edge on EXTI line9/8, otherwise the RTC Alarm will wake-up
37 the system within 3 second. After exit from STOP the system clock is reconfigured
38 to its previous state (as HSE and PLL are disabled in STOP mode).
39 Then after a delay the system will enter again in STOP mode and exit in the way
40 described above. This behavior is repeated in an infinite loop.
41
42 Three leds LED1, LED2 and LED3 are used to monitor the system state as following:
43 - LED1 on: system in RUN mode
44 - LED1 off: system in STOP mode
45 - LED2 is toggled if EXTI Line9/8 is used to exit from STOP
46 - LED3 is toggled if EXTI line17(RTC Alarm) is used to exit from STOP
47
48
49 @par Directory contents
50
51 - PWR/STOP/stm32f10x_conf.h Library Configuration file
52 - PWR/STOP/stm32f10x_it.c Interrupt handlers
53 - PWR/STOP/stm32f10x_it.h Header for stm32f10x_it.c
54 - PWR/STOP/main.c Main program
55 - PWR/STOP/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, LED2 and LED3 leds connected respectively to PF.06, PF0.7 and PF.08 pins
73 - Use the Key push-button connected to pin PG.08 (EXTI Line8).
74
75 - STM32100B-EVAL Set-up
76 - Use LED1, LED2 and LED3 leds connected respectively to PC.06, PC.07 and PC.08 pins
77 - Use the Key push-button connected to pin PB.09 (EXTI Line9).
78
79 - STM3210C-EVAL Set-up
80 - Use LED1, LED2 and LED3 leds connected respectively to PD.07, PD.13 and PF.03 pins
81 - Use the Key push-button connected to pin PB.09 (EXTI Line9).
82
83 - STM3210E-EVAL Set-up
84 - Use LED1, LED2 and LED3 leds connected respectively to PF.06, PF0.7 and PF.08 pins
85 - Use the Key push-button connected to pin PG.08 (EXTI Line8).
86
87 - STM3210B-EVAL Set-up
88 - Use LED1, LED2 and LED3 leds connected respectively to PC.06, PC.07 and PC.08 pins
89 - Use the Key push-button connected to pin PB.09 (EXTI Line9).
90
91 @note For power consumption measurement in STOP mode you have to:
92 - Modify the example to configure all unused GPIO port pins in Analog Input mode
93 (floating input trigger OFF). Refer to GPIO\IOToggle example for more details.
94 - Replace jumper JP9 in the STM3210B-EVAL board, JP12 in the STM3210E-EVAL,
95 JP23 (position 1-2) in the STM3210C-EVAL board or JP8 (position 1-2) in the
96 STM32100B-EVAL board by an amperemeter.
97
98
99 @par How to use it ?
100
101 In order to make the program work, you must do the following :
102 - Copy all source files from this example folder to the template folder under
103 Project\STM32F10x_StdPeriph_Template
104 - Open your preferred toolchain
105 - Rebuild all files and load your image into target memory
106 - Run the example in standalone mode (without debugger connection)
107
108 @note
109 - Low-density Value line devices are STM32F100xx microcontrollers where the
110 Flash memory density ranges between 16 and 32 Kbytes.
111 - Low-density devices are STM32F101xx, STM32F102xx and STM32F103xx
112 microcontrollers where the Flash memory density ranges between 16 and 32 Kbytes.
113 - Medium-density Value line devices are STM32F100xx microcontrollers where
114 the Flash memory density ranges between 64 and 128 Kbytes.
115 - Medium-density devices are STM32F101xx, STM32F102xx and STM32F103xx
116 microcontrollers where the Flash memory density ranges between 64 and 128 Kbytes.
117 - High-density Value line devices are STM32F100xx microcontrollers where
118 the Flash memory density ranges between 256 and 512 Kbytes.
119 - High-density devices are STM32F101xx and STM32F103xx microcontrollers where
120 the Flash memory density ranges between 256 and 512 Kbytes.
121 - XL-density devices are STM32F101xx and STM32F103xx microcontrollers where
122 the Flash memory density ranges between 512 and 1024 Kbytes.
123 - Connectivity line devices are STM32F105xx and STM32F107xx microcontrollers.
124
125 * <h3><center>&copy; COPYRIGHT 2011 STMicroelectronics</center></h3>
126 */