Mercurial > ~darius > hgwebdir.cgi > stm32temp
comparison libs/STM32F10x_StdPeriph_Lib_V3.5.0/Project/STM32F10x_StdPeriph_Examples/NVIC/DMA_WFIMode/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 NVIC_DMA_WFIMode DMA in WFI mode example | |
3 | |
4 @verbatim | |
5 ******************** (C) COPYRIGHT 2011 STMicroelectronics ******************* | |
6 * @file NVIC/DMA_WFIMode/readme.txt | |
7 * @author MCD Application Team | |
8 * @version V3.5.0 | |
9 * @date 08-April-2011 | |
10 * @brief Description of the NVIC DMA in WFI mode 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 WFI mode with DMA transfer enabled | |
24 and wake-up from this mode by the DMA End of Transfer interrupt. | |
25 | |
26 In the associated software, the system clock is set to 72 MHz (24MHz on Value line), | |
27 the DMA1 Channely is configured to transfer 10 data from the EVAL COM1 USART data | |
28 register to a predefined buffer, DST_Buffer, and to generate an interrupt at the | |
29 end of the transfer. | |
30 The EVAL COM1 USART receives data from HyperTerminal. | |
31 A LED1 is toggled with a frequency depending on the system clock, this is used | |
32 to indicate whether the MCU is in WFI or RUN mode. | |
33 | |
34 A falling edge on the selected EXTI Line will put the core in the WFI mode, | |
35 causing the led pin to stop toggling. | |
36 To wake-up from WFI mode you have to send the sequence (0, 1, 2, 3, 4, 5, 6, 7, 8, 9) | |
37 from the Hyperterminal to the EVAL COM1 USART. These bytes will be transferred | |
38 by the DMA from the EVAL COM1 receive data register to the predefined buffer, | |
39 then generates an interrupt which exits the system from WFI mode. | |
40 The LED1 restarts toggling and a LED2 will toggle if the buffer is correctly | |
41 received else a LED3 is toggled. | |
42 | |
43 | |
44 @par Directory contents | |
45 | |
46 - NVIC/DMA_WFIMode/stm32f10x_conf.h Library Configuration file | |
47 - NVIC/DMA_WFIMode/stm32f10x_it.c Interrupt handlers | |
48 - NVIC/DMA_WFIMode/stm32f10x_it.h Interrupt handlers header file | |
49 - NVIC/DMA_WFIMode/main.c Main program | |
50 - NVIC/DMA_WFIMode/system_stm32f10x.c STM32F10x system source file | |
51 | |
52 @par Hardware and Software environment | |
53 | |
54 - This example runs on STM32F10x Connectivity line, High-Density, High-Density | |
55 Value line, Medium-Density, XL-Density, Medium-Density Value line, Low-Density | |
56 and Low-Density Value line Devices. | |
57 | |
58 - This example has been tested with STMicroelectronics STM32100E-EVAL (High-Density | |
59 Value line), STM32100B-EVAL (Medium-Density Value line), STM3210C-EVAL (Connectivity line), | |
60 STM3210E-EVAL (High-Density and XL-Density) and STM3210B-EVAL (Medium-Density) | |
61 evaluation boards and can be easily tailored to any other supported device | |
62 and development board. | |
63 To select the STMicroelectronics evaluation board used to run the example, | |
64 uncomment the corresponding line in stm32_eval.h file (under Utilities\STM32_EVAL) | |
65 | |
66 - STM32100E-EVAL Set-up | |
67 - Use LED1, LED2, LED3 and LED4 leds connected respectively to PF.06, PF0.7, PF.08 | |
68 and PF.09 pins | |
69 - The USART1 signals (Rx, Tx) must be connected to a DB9 connector using a RS232 | |
70 transceiver. | |
71 - Connect a null-modem female/female RS232 cable between the DB9 connector, | |
72 CN12 on STM3210E-EVAL board, and PC serial port. | |
73 - Hyperterminal configuration: | |
74 - Word Length = 8 Bits | |
75 - One Stop Bit | |
76 - No parity | |
77 - BaudRate = 115200 baud | |
78 - flow control: None | |
79 - Use the Key push-button connected to pin PG.08 (EXTI Line8). | |
80 | |
81 - STM32100B-EVAL Set-up | |
82 - Use LED1, LED2, LED3 and LED4 leds connected respectively to PC.06, PC.07, PC.08 | |
83 and PC.09 pins | |
84 - The USART1 signals (Rx, Tx) must be connected to a DB9 connector using a RS232 | |
85 transceiver. | |
86 - Connect a null-modem female/female RS232 cable between the DB9 connector, | |
87 CN10 on STM32100B-EVAL board, and PC serial port. | |
88 - Hyperterminal configuration: | |
89 - Word Length = 8 Bits | |
90 - One Stop Bit | |
91 - No parity | |
92 - BaudRate = 115200 baud | |
93 - flow control: None | |
94 - Use the Key push-button connected to pin PB.09 (EXTI Line9). | |
95 | |
96 - STM3210C-EVAL Set-up | |
97 - Use LED1, LED2, LED3 and LED4 connected respectively to PD.07, PD.13, PF.03 | |
98 and PD.04 pins | |
99 - The USART2 signals (Rx, Tx) must be connected to a DB9 connector using a RS232 | |
100 transceiver. | |
101 - Connect a null-modem female/female RS232 cable between the DB9 connector, | |
102 CN6 on STM3210C-EVAL board, and PC serial port. | |
103 - Hyperterminal configuration: | |
104 - Word Length = 8 Bits | |
105 - One Stop Bit | |
106 - No parity | |
107 - BaudRate = 115200 baud | |
108 - flow control: None | |
109 - Use the Key push-button connected to pin PB.09 (EXTI Line9). | |
110 | |
111 - STM3210E-EVAL Set-up | |
112 - Use LED1, LED2, LED3 and LED4 leds connected respectively to PF.06, PF0.7, PF.08 | |
113 and PF.09 pins | |
114 - The USART1 signals (Rx, Tx) must be connected to a DB9 connector using a RS232 | |
115 transceiver. | |
116 - Connect a null-modem female/female RS232 cable between the DB9 connector, | |
117 CN12 on STM3210E-EVAL board, and PC serial port. | |
118 - Hyperterminal configuration: | |
119 - Word Length = 8 Bits | |
120 - One Stop Bit | |
121 - No parity | |
122 - BaudRate = 115200 baud | |
123 - flow control: None | |
124 - Use the Key push-button connected to pin PG.08 (EXTI Line8). | |
125 | |
126 - STM3210B-EVAL Set-up | |
127 - Use LED1, LED2, LED3 and LED4 leds connected respectively to PC.06, PC.07, PC.08 | |
128 and PC.09 pins | |
129 - The USART1 signals (Rx, Tx) must be connected to a DB9 connector using a RS232 | |
130 transceiver. | |
131 - Connect a null-modem female/female RS232 cable between the DB9 connector, | |
132 CN6 on STM3210B-EVAL board, and PC serial port. | |
133 - Hyperterminal configuration: | |
134 - Word Length = 8 Bits | |
135 - One Stop Bit | |
136 - No parity | |
137 - BaudRate = 115200 baud | |
138 - flow control: None | |
139 - Use the Key push-button connected to pin PB.09 (EXTI Line9). | |
140 | |
141 | |
142 @par How to use it ? | |
143 | |
144 In order to make the program work, you must do the following : | |
145 - Copy all source files from this example folder to the template folder under | |
146 Project\STM32F10x_StdPeriph_Template | |
147 - Open your preferred toolchain | |
148 - Rebuild all files and load your image into target memory | |
149 - Run the example | |
150 | |
151 @note | |
152 - Low-density Value line devices are STM32F100xx microcontrollers where the | |
153 Flash memory density ranges between 16 and 32 Kbytes. | |
154 - Low-density devices are STM32F101xx, STM32F102xx and STM32F103xx | |
155 microcontrollers where the Flash memory density ranges between 16 and 32 Kbytes. | |
156 - Medium-density Value line devices are STM32F100xx microcontrollers where | |
157 the Flash memory density ranges between 64 and 128 Kbytes. | |
158 - Medium-density devices are STM32F101xx, STM32F102xx and STM32F103xx | |
159 microcontrollers where the Flash memory density ranges between 64 and 128 Kbytes. | |
160 - High-density Value line devices are STM32F100xx microcontrollers where | |
161 the Flash memory density ranges between 256 and 512 Kbytes. | |
162 - High-density devices are STM32F101xx and STM32F103xx microcontrollers where | |
163 the Flash memory density ranges between 256 and 512 Kbytes. | |
164 - XL-density devices are STM32F101xx and STM32F103xx microcontrollers where | |
165 the Flash memory density ranges between 512 and 1024 Kbytes. | |
166 - Connectivity line devices are STM32F105xx and STM32F107xx microcontrollers. | |
167 | |
168 * <h3><center>© COPYRIGHT 2011 STMicroelectronics</center></h3> | |
169 */ |