Mercurial > ~darius > hgwebdir.cgi > stm32temp
comparison libs/STM32F10x_StdPeriph_Lib_V3.5.0/Project/STM32F10x_StdPeriph_Examples/DAC/OneChannel_NoiseWave/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 DAC_OneChannel_NoiseWave DAC one channel noise wave example | |
3 | |
4 @verbatim | |
5 ******************** (C) COPYRIGHT 2011 STMicroelectronics ******************* | |
6 * @file DAC/OneChannel_NoiseWave/readme.txt | |
7 * @author MCD Application Team | |
8 * @version V3.5.0 | |
9 * @date 08-April-2011 | |
10 * @brief Description of the DAC one channel noise wave 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 describes how to use one DAC channel to generate a signal with noise | |
24 waves on DAC Channel1 output. | |
25 | |
26 DAC channel1 conversion are configured to be triggered by software with noise wave | |
27 generation.12bit left data alignment is selected since we choose to access DAC_DHR12L1 | |
28 register. Bits 0 to 8 are masked for the Linear feedback shift register. | |
29 DAC channel1 is then enabled. DAC Channel1 DHR12L1 register is configured to have | |
30 an output voltage of VREF/2. | |
31 | |
32 Software triggers are generated continuously in an infinite loop, and on each | |
33 trigger the DAC channel1 start the conversion and calculate the noise value to | |
34 apply on the DAC channel1 output. | |
35 | |
36 The output signal with noise waves can be visualized by connecting PA.04 pin to | |
37 an oscilloscope. | |
38 | |
39 @par Directory contents | |
40 | |
41 - DAC/OneChannel_NoiseWave/stm32f10x_conf.h Library Configuration file | |
42 - DAC/OneChannel_NoiseWave/stm32f10x_it.c Interrupt handlers | |
43 - DAC/OneChannel_NoiseWave/stm32f10x_it.h Header for stm32f10x_it.c | |
44 - DAC/OneChannel_NoiseWave/main.c Main program | |
45 - DAC/OneChannel_NoiseWave/system_stm32f10x.c STM32F10x system source file | |
46 | |
47 @par Hardware and Software environment | |
48 | |
49 - This example runs on STM32F10x Connectivity line, High-Density, XL-Density, | |
50 High-Density Value line, Medium-Density Value line and Low-Density Value | |
51 line Devices. | |
52 | |
53 - This example has been tested with STMicroelectronics STM32100B-EVAL | |
54 (Medium-Density Value line),STM32100E-EVAL (High-Density Value line), | |
55 STM3210C-EVAL (Connectivity line) and STM3210E-EVAL (High-Density and | |
56 XL-Density) evaluation boards and can be easily tailored to any other | |
57 supported device and development board. | |
58 | |
59 - STM32100B-EVAL Set-up | |
60 - Connect PA.04 pin to an oscilloscope | |
61 @note JP2 should be open | |
62 | |
63 - STM3210C-EVAL Set-up | |
64 - Connect PA.04 pin to an oscilloscope | |
65 | |
66 - STM3210E-EVAL Set-up | |
67 - Connect PA.04 pin to an oscilloscope | |
68 | |
69 - STM32100E-EVAL Set-up | |
70 - Connect PA.04 pin to an oscilloscope | |
71 | |
72 @par How to use it ? | |
73 | |
74 In order to make the program work, you must do the following : | |
75 - Copy all source files from this example folder to the template folder under | |
76 Project\STM32F10x_StdPeriph_Template | |
77 - Open your preferred toolchain | |
78 - Rebuild all files and load your image into target memory | |
79 - Run the example | |
80 | |
81 @note | |
82 - Low-density Value line devices are STM32F100xx microcontrollers where the | |
83 Flash memory density ranges between 16 and 32 Kbytes. | |
84 - Low-density devices are STM32F101xx, STM32F102xx and STM32F103xx | |
85 microcontrollers where the Flash memory density ranges between 16 and 32 Kbytes. | |
86 - Medium-density Value line devices are STM32F100xx microcontrollers where | |
87 the Flash memory density ranges between 64 and 128 Kbytes. | |
88 - Medium-density devices are STM32F101xx, STM32F102xx and STM32F103xx | |
89 microcontrollers where the Flash memory density ranges between 64 and 128 Kbytes. | |
90 - High-density Value line devices are STM32F100xx microcontrollers where | |
91 the Flash memory density ranges between 256 and 512 Kbytes. | |
92 - High-density devices are STM32F101xx and STM32F103xx microcontrollers where | |
93 the Flash memory density ranges between 256 and 512 Kbytes. | |
94 - XL-density devices are STM32F101xx and STM32F103xx microcontrollers where | |
95 the Flash memory density ranges between 512 and 1024 Kbytes. | |
96 - Connectivity line devices are STM32F105xx and STM32F107xx microcontrollers. | |
97 | |
98 * <h3><center>© COPYRIGHT 2011 STMicroelectronics</center></h3> | |
99 */ |