Mercurial > ~darius > hgwebdir.cgi > stm32temp

comparison libs/STM32F10x_StdPeriph_Lib_V3.5.0/Project/STM32F10x_StdPeriph_Examples/DMA/SPI_RAM/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 DMA_SPI_RAM DMA SPI to RAM example
3
4 @verbatim
5 ******************** (C) COPYRIGHT 2011 STMicroelectronics *******************
6 * @file DMA/SPI_RAM/readme.txt
7 * @author MCD Application Team
8 * @version V3.5.0
9 * @date 08-April-2011
10 * @brief Description of the DMA SPI to RAM 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 provides a description of how to use four DMA channels to transfer
24 a data buffer from memory to SPI_SLAVE through SPI_MASTER and a second data buffer
25 from memory to SPI_MASTER through SPI_SLAVE in full-duplex mode.
26 SPI_MASTER and SPI_SLAVE can be SPI1 and SPI2 or SPI3 and SPI2, depending on the
27 STMicroelectronics EVAL board you are using.
28
29 For each SPI the NSS pin is configured by software (thus NSS pin is free for GPIO use)
30 and DMA Tx/Rx requests are enabled.
31
32 In this example both transmission and reception are managed through DMA and the
33 received data are stored into buffers declared in the SRAM. The DMA channels
34 involved in this transfer depend on the used SPIs (for more details please refer
35 to platform_config.h file).
36
37 A polling on all Transfer complete flags are done for all used DMA channels to
38 check the end of all DMA channels transfers. The last received data on SPI_MASTER
39 and SPI_SLAVE are the CRC values sent by each SPI to the other.
40 The transmitted and received buffers are compared to check that all data have
41 been correctly transferred.
42
43
44 @par Directory contents
45
46 - DMA/SPI_RAM/platform_config.h Evaluation board specific configuration file
47 - DMA/SPI_RAM/stm32f10x_conf.h Library Configuration file
48 - DMA/SPI_RAM/stm32f10x_it.c Interrupt handlers
49 - DMA/SPI_RAM/stm32f10x_it.h Interrupt handlers header file
50 - DMA/SPI_RAM/main.c Main program
51 - DMA/SPI_RAM/system_stm32f10x.c STM32F10x system source file
52
53 @par Hardware and Software environment
54
55 - This example runs on STM32F10x Connectivity line, High-Density, Medium-Density,
56 XL-Density, High-Density Value line, Medium-Density Value line, Low-Density
57 and Low-Density Value line Devices.
58
59 - This example has been tested with STMicroelectronics STM32100E-EVAL (High-Density Value line)
60 STM32100B-EVAL (Medium-Density Value line), STM32100E-EVAL (High-Density Value line), STM3210C-EVAL
61 (Connectivity line), STM3210E-EVAL (High-Density and XL-Density) and STM3210B-EVAL
62 (Medium-Density) evaluation boards and can be easily tailored to any other
63 supported device and development board.
64
65 - STM32100E-EVAL Set-up
66 - Connect SPI1 SCK pin (PA.05) to SPI2 SCK pin (PB.13)
67 - Connect SPI1 MISO pin (PA.06) to SPI2 MISO pin (PB.14)
68 - Connect SPI1 MOSI pin (PA.07) to SPI2 MOSI pin (PB.15)
69
70 - STM32100B-EVAL Set-up
71 - Connect SPI1 SCK pin (PA.05) to SPI2 SCK pin (PB.13)
72 - Connect SPI1 MISO pin (PA.06) to SPI2 MISO pin (PB.14)
73 - Connect SPI1 MOSI pin (PA.07) to SPI2 MOSI pin (PB.15)
74
75 - STM3210C-EVAL Set-up
76 - Connect SPI3 SCK pin (PC.10) to SPI2 SCK pin (PB.13)
77 - Connect SPI3 MISO pin (PC.11) to SPI2 MISO pin (PB.14)
78 - Connect SPI3 MOSI pin (PC.12) to SPI2 MOSI pin (PB.15)
79 @note In this case SPI3 pins are remapped by software.
80
81 - STM3210E-EVAL Set-up
82 - Connect SPI1 SCK pin (PA.05) to SPI2 SCK pin (PB.13)
83 - Connect SPI1 MISO pin (PA.06) to SPI2 MISO pin (PB.14)
84 - Connect SPI1 MOSI pin (PA.07) to SPI2 MOSI pin (PB.15)
85 @note The jumper 14 (USB Disconnect) must be set in position 1<->2 in order
86 to not interfer with SPI2 MISO pin PB14.
87
88 - STM3210B-EVAL Set-up
89 - Connect SPI1 SCK pin (PA.05) to SPI2 SCK pin (PB.13)
90 - Connect SPI1 MISO pin (PA.06) to SPI2 MISO pin (PB.14)
91 - Connect SPI1 MOSI pin (PA.07) to SPI2 MOSI pin (PB.15)
92
93
94 @par How to use it ?
95
96 In order to make the program work, you must do the following :
97 - Copy all source files from this example folder to the template folder under
98 Project\STM32F10x_StdPeriph_Template
99 - Open your preferred toolchain
100 - Rebuild all files and load your image into target memory
101 - Run the example
102
103 @note
104 - Low-density Value line devices are STM32F100xx microcontrollers where the
105 Flash memory density ranges between 16 and 32 Kbytes.
106 - Low-density devices are STM32F101xx, STM32F102xx and STM32F103xx
107 microcontrollers where the Flash memory density ranges between 16 and 32 Kbytes.
108 - Medium-density Value line devices are STM32F100xx microcontrollers where
109 the Flash memory density ranges between 64 and 128 Kbytes.
110 - Medium-density devices are STM32F101xx, STM32F102xx and STM32F103xx
111 microcontrollers where the Flash memory density ranges between 64 and 128 Kbytes.
112 - High-density Value line devices are STM32F100xx microcontrollers where
113 the Flash memory density ranges between 256 and 512 Kbytes.
114 - High-density devices are STM32F101xx and STM32F103xx microcontrollers where
115 the Flash memory density ranges between 256 and 512 Kbytes.
116 - XL-density devices are STM32F101xx and STM32F103xx microcontrollers where
117 the Flash memory density ranges between 512 and 1024 Kbytes.
118 - Connectivity line devices are STM32F105xx and STM32F107xx microcontrollers.
119
120 * <h3><center>&copy; COPYRIGHT 2011 STMicroelectronics</center></h3>
121 */