Mercurial > ~darius > hgwebdir.cgi > stm32temp
comparison libs/STM32F10x_StdPeriph_Lib_V3.5.0/Project/STM32F10x_StdPeriph_Examples/WWDG/WWDG_Reset/readme.txt @ 0:c59513fd84fb
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 WWDG_Reset WWDG Reset example | |
3 | |
4 @verbatim | |
5 ******************** (C) COPYRIGHT 2011 STMicroelectronics ******************* | |
6 * @file WWDG/WWDG_Reset/readme.txt | |
7 * @author MCD Application Team | |
8 * @version V3.5.0 | |
9 * @date 08-April-2011 | |
10 * @brief Description of the WWDG Reset 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 update at regular period the WWDG counter and how to | |
24 simulate a software fault generating an MCU WWDG reset on expiry of a programmed | |
25 time period. | |
26 | |
27 The WWDG timeout is set to 65.53ms and the refresh window is set to 80. | |
28 The WWDG counter is refreshed each 50ms in the main program infinite loop to | |
29 prevent a WWDG reset. | |
30 LED2 is also toggled each 50ms indicating that the program is running. | |
31 | |
32 An EXTI Line is connected to a GPIO pin, and configured to generate an interrupt | |
33 on the rising edge of the signal. | |
34 | |
35 The EXTI Line is used to simulate a software failure: once the EXTI Line event | |
36 occurs, by pressing the Key push-button, the corresponding interrupt is served. | |
37 In the ISR, a write to invalid address generates a Hardfault exception containing | |
38 an infinite loop and preventing to return to main program (the WWDG counter is | |
39 not refreshed). | |
40 As a result, when the WWDG counter falls to 63, the WWDG reset occurs. | |
41 If the WWDG reset is generated, after the system resumes from reset, LED1 turns on. | |
42 | |
43 If the EXTI Line event does not occur, the WWDG counter is indefinitely refreshed | |
44 in the main program infinite loop, and there is no WWDG reset. | |
45 | |
46 In this example the system clock is set to 24 MHz on Value line devices and to | |
47 72 MHz on other devices. | |
48 | |
49 | |
50 @par Directory contents | |
51 | |
52 - WWDG/WWDG_Reset/stm32f10x_conf.h Library Configuration file | |
53 - WWDG/WWDG_Reset/stm32f10x_it.c Interrupt handlers | |
54 - WWDG/WWDG_Reset/stm32f10x_it.h Header for stm32f10x_it.c | |
55 - WWDG/WWDG_Reset/main.c Main program | |
56 - WWDG/WWDG_Reset/system_stm32f10x.c STM32F10x system source file | |
57 | |
58 @par Hardware and Software environment | |
59 | |
60 - This example runs on STM32F10x Connectivity line, High-Density, High-Density | |
61 Value line, Medium-Density, XL-Density, Medium-Density Value line, Low-Density | |
62 and Low-Density Value line Devices. | |
63 | |
64 - This example has been tested with STMicroelectronics STM32100E-EVAL (High-Density | |
65 Value line), STM32100B-EVAL (Medium-Density Value line), STM3210C-EVAL (Connectivity line), | |
66 STM3210E-EVAL (High-Density and XL-Density)and STM3210B-EVAL (Medium-Density) | |
67 evaluation boards and can be easily tailored to any other supported device | |
68 and development board. | |
69 To select the STMicroelectronics evaluation board used to run the example, | |
70 uncomment the corresponding line in stm32_eval.h file (under Utilities\STM32_EVAL) | |
71 | |
72 - STM32100E-EVAL Set-up | |
73 - Use LD1 and LD2 leds connected respectively to PF.06 and PF.07 pins | |
74 - Use the KEY push button connected to PG.08 pin (EXTI Line8). | |
75 | |
76 - STM32100B-EVAL Set-up | |
77 - Use LD1 and LD2 leds connected respectively to PC.06 and PC.07 pins | |
78 - Use the KEY push button connected to PB.09 pin (EXTI Line9). | |
79 | |
80 - STM3210C-EVAL Set-up | |
81 - Use LD1 and LD2 connected respectively to PD.07 and PD.13 pins | |
82 - Use the Key push-button connected to pin PB.09 (EXTI Line9). | |
83 | |
84 - STM3210E-EVAL Set-up | |
85 - Use LD1 and LD2 leds connected respectively to PF.06 and PF.07 pins | |
86 - Use the KEY push button connected to PG.08 pin (EXTI Line8). | |
87 | |
88 - STM3210B-EVAL Set-up | |
89 - Use LD1 and LD2 leds connected respectively to PC.06 and PC.07 pins | |
90 - Use the KEY push button connected to PB.09 pin (EXTI Line9). | |
91 | |
92 @par How to use it ? | |
93 | |
94 In order to make the program work, you must do the following : | |
95 - Copy all source files from this example folder to the template folder under | |
96 Project\STM32F10x_StdPeriph_Template | |
97 - Open your preferred toolchain | |
98 - Rebuild all files and load your image into target memory | |
99 - Run the example | |
100 | |
101 @note | |
102 - Low-density Value line devices are STM32F100xx microcontrollers where the | |
103 Flash memory density ranges between 16 and 32 Kbytes. | |
104 - Low-density devices are STM32F101xx, STM32F102xx and STM32F103xx | |
105 microcontrollers where the Flash memory density ranges between 16 and 32 Kbytes. | |
106 - Medium-density Value line devices are STM32F100xx microcontrollers where | |
107 the Flash memory density ranges between 64 and 128 Kbytes. | |
108 - Medium-density devices are STM32F101xx, STM32F102xx and STM32F103xx | |
109 microcontrollers where the Flash memory density ranges between 64 and 128 Kbytes. | |
110 - High-density Value line devices are STM32F100xx microcontrollers where | |
111 the Flash memory density ranges between 256 and 512 Kbytes. | |
112 - High-density devices are STM32F101xx and STM32F103xx microcontrollers where | |
113 the Flash memory density ranges between 256 and 512 Kbytes. | |
114 - XL-density devices are STM32F101xx and STM32F103xx microcontrollers where | |
115 the Flash memory density ranges between 512 and 1024 Kbytes. | |
116 - Connectivity line devices are STM32F105xx and STM32F107xx microcontrollers. | |
117 | |
118 * <h3><center>© COPYRIGHT 2011 STMicroelectronics</center></h3> | |
119 */ |