Mercurial > ~darius > hgwebdir.cgi > stm32temp

comparison libs/STM32F10x_StdPeriph_Lib_V3.5.0/Project/STM32F10x_StdPeriph_Examples/USART/HalfDuplex/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 USART_HalfDuplex USART Half Duplex example
3
4 @verbatim
5 ******************** (C) COPYRIGHT 2011 STMicroelectronics *******************
6 * @file USART/HalfDuplex/readme.txt
7 * @author MCD Application Team
8 * @version V3.5.0
9 * @date 08-April-2011
10 * @brief Description of the USART Half Duplex 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 basic communication between USARTy and USARTz in
24 Half-Duplex mode using flags. USARTy and USARTz can be USART1 and USART2 or
25 USART2 and USART3, depending on the STMicroelectronics EVAL board you are using.
26
27 First, the USARTy sends data from TxBuffer1 buffer to USARTz using TXE flag.
28 Data received using RXNE flag by USARTz is stored in RxBuffer2 then compared with
29 the sent ones and the result of this comparison is stored in the "TransferStatus1"
30 variable.
31
32 Then, the USARTz sends data from TxBuffer2 buffer to USARTy using TXE flag.
33 Data received using RXNE flag by USARTy is stored in RxBuffer1 then compared with
34 the sent ones and the result of this comparison is stored in the "TransferStatus2"
35 variable.
36
37 USARTy and USARTz configured as follow:
38 - BaudRate = 230400 baud
39 - Word Length = 8 Bits
40 - One Stop Bit
41 - Even parity
42 - Hardware flow control disabled (RTS and CTS signals)
43 - Receive and transmit enabled
44
45 @par Directory contents
46
47 - USART/HalfDuplex/platform_config.h Evaluation board specific configuration file
48 - USART/HalfDuplex/stm32f10x_conf.h Library Configuration file
49 - USART/HalfDuplex/stm32f10x_it.h Interrupt handlers header file
50 - USART/HalfDuplex/stm32f10x_it.c Interrupt handlers
51 - USART/HalfDuplex/main.c Main program
52 - USART/HalfDuplex/system_stm32f10x.c STM32F10x system source file
53
54 @par Hardware and Software environment
55
56 - This example runs on STM32F10x Connectivity line, High-Density, High-Density
57 Value line, Medium-Density, XL-Density, Medium-Density Value line, Low-Density
58 and Low-Density Value line Devices.
59
60 - This example has been tested with STMicroelectronics STM32100E-EVAL (High-Density
61 Value line), STM32100B-EVAL (Medium-Density Value line), STM3210C-EVAL (Connectivity line),
62 STM3210E-EVAL (High-Density and XL-Density) and STM3210B-EVAL (Medium-Density)
63 evaluation boards and can be easily tailored to any other supported device
64 and development board.
65 To select the STMicroelectronics evaluation board used to run the example,
66 uncomment the corresponding line in USART/HalfDuplex/platform_config.h file
67
68 - STM32100E-EVAL Set-up
69 - Connect USART1_Tx(PA.09) to USART2_Tx(PA.02).
70
71 - STM32100B-EVAL Set-up
72 - Connect USART1_Tx(PA.09) to USART2_Tx(PD.05).
73
74 - STM3210C-EVAL Set-up
75 - Connect USART2 Tx pin (PD.05) to USART3 Tx pin (PC.10) and connect a
76 pull-up resistor to this line (10K).
77 @note In this case USART3 Tx pin is remapped by software.
78 Make sure that jumpers JP19 and JP18 are open.
79
80 - STM3210E-EVAL Set-up
81 - Connect USART1_Tx(PA.09) to USART2_Tx(PA.02) and connect a pull-up resistor to
82 this line (10K).
83
84 - STM3210B-EVAL Set-up
85 - Connect USART1_Tx(PA.09) to USART2_Tx(PD.05) and connect a pull-up resistor to
86 this line (10K).
87
88 @par How to use it ?
89
90 In order to make the program work, you must do the following :
91 - Copy all source files from this example folder to the template folder under
92 Project\STM32F10x_StdPeriph_Template
93 - Open your preferred toolchain
94 - Rebuild all files and load your image into target memory
95 - Run the example
96
97 @note
98 - Low-density Value line devices are STM32F100xx microcontrollers where the
99 Flash memory density ranges between 16 and 32 Kbytes.
100 - Low-density devices are STM32F101xx, STM32F102xx and STM32F103xx
101 microcontrollers where the Flash memory density ranges between 16 and 32 Kbytes.
102 - Medium-density Value line devices are STM32F100xx microcontrollers where
103 the Flash memory density ranges between 64 and 128 Kbytes.
104 - Medium-density devices are STM32F101xx, STM32F102xx and STM32F103xx
105 microcontrollers where the Flash memory density ranges between 64 and 128 Kbytes.
106 - High-density Value line devices are STM32F100xx microcontrollers where
107 the Flash memory density ranges between 256 and 512 Kbytes.
108 - High-density devices are STM32F101xx and STM32F103xx microcontrollers where
109 the Flash memory density ranges between 256 and 512 Kbytes.
110 - XL-density devices are STM32F101xx and STM32F103xx microcontrollers where
111 the Flash memory density ranges between 512 and 1024 Kbytes.
112 - Connectivity line devices are STM32F105xx and STM32F107xx microcontrollers.
113
114 * <h3><center>&copy; COPYRIGHT 2011 STMicroelectronics</center></h3>
115 */