diff options
Diffstat (limited to 'thirdparty/STM32F10x_StdPeriph_Lib_V3.5.0/Project/STM32F10x_StdPeriph_Examples/DMA/I2C_RAM')
-rw-r--r-- | thirdparty/STM32F10x_StdPeriph_Lib_V3.5.0/Project/STM32F10x_StdPeriph_Examples/DMA/I2C_RAM/readme.txt | 103 |
1 files changed, 103 insertions, 0 deletions
diff --git a/thirdparty/STM32F10x_StdPeriph_Lib_V3.5.0/Project/STM32F10x_StdPeriph_Examples/DMA/I2C_RAM/readme.txt b/thirdparty/STM32F10x_StdPeriph_Lib_V3.5.0/Project/STM32F10x_StdPeriph_Examples/DMA/I2C_RAM/readme.txt new file mode 100644 index 0000000..f5118ec --- /dev/null +++ b/thirdparty/STM32F10x_StdPeriph_Lib_V3.5.0/Project/STM32F10x_StdPeriph_Examples/DMA/I2C_RAM/readme.txt @@ -0,0 +1,103 @@ +/** + @page DMA_I2C_RAM DMA I2C to RAM example + + @verbatim + ******************** (C) COPYRIGHT 2011 STMicroelectronics ******************* + * @file DMA/I2C_RAM/readme.txt + * @author MCD Application Team + * @version V3.5.0 + * @date 08-April-2011 + * @brief Description of the DMA I2C to RAM example. + ****************************************************************************** + * THE PRESENT FIRMWARE WHICH IS FOR GUIDANCE ONLY AIMS AT PROVIDING CUSTOMERS + * WITH CODING INFORMATION REGARDING THEIR PRODUCTS IN ORDER FOR THEM TO SAVE + * TIME. AS A RESULT, STMICROELECTRONICS SHALL NOT BE HELD LIABLE FOR ANY + * DIRECT, INDIRECT OR CONSEQUENTIAL DAMAGES WITH RESPECT TO ANY CLAIMS ARISING + * FROM THE CONTENT OF SUCH FIRMWARE AND/OR THE USE MADE BY CUSTOMERS OF THE + * CODING INFORMATION CONTAINED HEREIN IN CONNECTION WITH THEIR PRODUCTS. + ****************************************************************************** + @endverbatim + +@par Example Description + +This example provides a description of how to use two DMA channels to transfer a +data buffer from memory to I2C2 through I2C1. + +I2C1 is set as the master transmitter and I2C2 as the slave receiver. DMA1 Channel5 is +configured to store the data received from I2C2 into the Rx buffer (reception buffer). +DMA1 Channel6 is configured to transfer data from the Tx buffer (transmission buffer) +to the I2C1 DR register. After the generation of the Start condition and once the slave +address has been acknowledged, DMA capability is enabled for both I2C1 and I2C2. +As soon as the two I2C DMAEN bits are set in the I2C1_CR2 and I2C2_CR2 registers, +the transmission of the Tx buffer is started by DMA1 Channel5 and at the same time the +data received on I2C2 is stored in Rx buffer using DMA1 Channel6 . +The transmitted and the received buffers are compared to check that all data have been +correctly transferred. + + +@par Directory contents + + - DMA/I2C_RAM/stm32f10x_conf.h Library Configuration file + - DMA/I2C_RAM/stm32f10x_it.c Interrupt handlers + - DMA/I2C_RAM/stm32f10x_it.h Interrupt handlers header file + - DMA/I2C_RAM/main.c Main program + - DMA/I2C_RAM/system_stm32f10x.c STM32F10x system source file + + +@par Hardware and Software environment + + - This example runs on STM32F10x Connectivity line, High-Density, Medium-Density, + XL-Density, High-Density Value line, Medium-Density Value line, Low-Density + and Low-Density Value line Devices. + + - This example has been tested with STMicroelectronics STM3210E-EVAL (High-Density + and XL-Density) and STM3210B-EVAL (Medium-Density) evaluation boards and can + be easily tailored to any other supported device and development board. + This example can't be tested with STMicroelectronics STM3210C-EVAL (STM32F10x + Connectivity-Line) evaluation boards since the I2C2 pins (PB10 and PB11) are + already used by Ethernet PHY module. + This example can't be tested with STMicroelectronics STM32100B-EVAL (STM32F10x + Medium-Density Value line) and STM32100E-EVAL (High-Density Value line) + evaluation boards since the I2C1/I2C2 pins (PB6/PB10 and PB7/PB11) are already + used by HDMI-CEC module. + + - STM3210E-EVAL Set-up + - Connect I2C1 SCL pin (PB.06) to I2C2 SCL pin (PB.10) + - Connect I2C1 SDA pin (PB.07) to I2C2 SDA pin (PB.11) + - Check that a pull-up resistor is connected on one I2C SDA pin + - Check that a pull-up resistor is connected on one I2C SCL pin + + - STM3210B-EVAL Set-up + - Connect I2C1 SCL pin (PB.06) to I2C2 SCL pin (PB.10) + - Connect I2C1 SDA pin (PB.07) to I2C2 SDA pin (PB.11) + - Check that a pull-up resistor is connected on one I2C SDA pin + - Check that a pull-up resistor is connected on one I2C SCL pin + +@par How to use it ? + +In order to make the program work, you must do the following : + - Copy all source files from this example folder to the template folder under + Project\STM32F10x_StdPeriph_Template + - Open your preferred toolchain + - Rebuild all files and load your image into target memory + - Run the example + +@note + - Low-density Value line devices are STM32F100xx microcontrollers where the + Flash memory density ranges between 16 and 32 Kbytes. + - Low-density devices are STM32F101xx, STM32F102xx and STM32F103xx + microcontrollers where the Flash memory density ranges between 16 and 32 Kbytes. + - Medium-density Value line devices are STM32F100xx microcontrollers where + the Flash memory density ranges between 64 and 128 Kbytes. + - Medium-density devices are STM32F101xx, STM32F102xx and STM32F103xx + microcontrollers where the Flash memory density ranges between 64 and 128 Kbytes. + - High-density Value line devices are STM32F100xx microcontrollers where + the Flash memory density ranges between 256 and 512 Kbytes. + - High-density devices are STM32F101xx and STM32F103xx microcontrollers where + the Flash memory density ranges between 256 and 512 Kbytes. + - XL-density devices are STM32F101xx and STM32F103xx microcontrollers where + the Flash memory density ranges between 512 and 1024 Kbytes. + - Connectivity line devices are STM32F105xx and STM32F107xx microcontrollers. + + * <h3><center>© COPYRIGHT 2011 STMicroelectronics</center></h3> + */ |