文件列表:

I2C_TwoBoards_ComDMA (0, 2016-11-13)
I2C_TwoBoards_ComDMA\EWARM (0, 2016-11-13)
I2C_TwoBoards_ComDMA\EWARM\Project.ewd (36880, 2016-05-28)
I2C_TwoBoards_ComDMA\EWARM\Project.ewp (29207, 2016-05-28)
I2C_TwoBoards_ComDMA\EWARM\Project.eww (161, 2016-05-28)
I2C_TwoBoards_ComDMA\EWARM\startup_stm32l053xx.s (12049, 2016-05-31)
I2C_TwoBoards_ComDMA\EWARM\stm32l053xx_flash.icf (1353, 2016-05-28)
I2C_TwoBoards_ComDMA\Inc (0, 2016-11-13)
I2C_TwoBoards_ComDMA\Inc\main.h (4451, 2016-05-31)
I2C_TwoBoards_ComDMA\Inc\stm32l0xx_hal_conf.h (11198, 2016-05-31)
I2C_TwoBoards_ComDMA\Inc\stm32l0xx_it.h (3101, 2016-05-31)
I2C_TwoBoards_ComDMA\MDK-ARM (0, 2016-11-13)
I2C_TwoBoards_ComDMA\MDK-ARM\Project.uvoptx (15892, 2016-05-28)
I2C_TwoBoards_ComDMA\MDK-ARM\Project.uvprojx (21282, 2016-05-28)
I2C_TwoBoards_ComDMA\MDK-ARM\startup_stm32l053xx.s (11053, 2016-05-31)
I2C_TwoBoards_ComDMA\Src (0, 2016-11-13)
I2C_TwoBoards_ComDMA\Src\main.c (15221, 2016-05-31)
I2C_TwoBoards_ComDMA\Src\stm32l0xx_hal_msp.c (7720, 2016-05-31)
I2C_TwoBoards_ComDMA\Src\stm32l0xx_it.c (5331, 2016-05-31)
I2C_TwoBoards_ComDMA\Src\system_stm32l0xx.c (10325, 2016-05-31)
I2C_TwoBoards_ComDMA\SW4STM32 (0, 2016-11-13)
I2C_TwoBoards_ComDMA\SW4STM32\startup_stm32l053xx.s (10976, 2016-05-31)
I2C_TwoBoards_ComDMA\SW4STM32\STM32L053R8_NUCLEO (0, 2016-11-13)
I2C_TwoBoards_ComDMA\SW4STM32\STM32L053R8_NUCLEO\.cproject (11403, 2016-05-28)
I2C_TwoBoards_ComDMA\SW4STM32\STM32L053R8_NUCLEO\.project (4805, 2016-05-28)
I2C_TwoBoards_ComDMA\SW4STM32\STM32L053R8_NUCLEO\STM32L053R8Tx_FLASH.ld (4416, 2016-05-28)
I2C_TwoBoards_ComDMA\TrueSTUDIO (0, 2016-11-13)
I2C_TwoBoards_ComDMA\TrueSTUDIO\startup_stm32l053xx.s (10976, 2016-05-31)
I2C_TwoBoards_ComDMA\TrueSTUDIO\STM32L053R8_NUCLEO (0, 2016-11-13)
I2C_TwoBoards_ComDMA\TrueSTUDIO\STM32L053R8_NUCLEO\.cproject (19126, 2016-05-28)
I2C_TwoBoards_ComDMA\TrueSTUDIO\STM32L053R8_NUCLEO\.project (7253, 2016-05-28)
I2C_TwoBoards_ComDMA\TrueSTUDIO\STM32L053R8_NUCLEO\.settings (0, 2016-11-13)
I2C_TwoBoards_ComDMA\TrueSTUDIO\STM32L053R8_NUCLEO\.settings\com.atollic.truestudio.debug.hardware_device.prefs (219, 2016-05-28)
I2C_TwoBoards_ComDMA\TrueSTUDIO\STM32L053R8_NUCLEO\STM32L053R8_FLASH.ld (4501, 2016-05-28)
I2C_TwoBoards_ComDMA\TrueSTUDIO\STM32L053R8_NUCLEO\STM32L053R8_NUCLEO.elf.launch (5494, 2016-05-28)

/** @page I2C_TwoBoards_ComDMA I2C Two Boards Communication DMA example @verbatim ******************** (C) COPYRIGHT 2016 STMicroelectronics ******************* * @file I2C/I2C_TwoBoards_ComDMA/readme.txt * @author MCD Application Team * @version V1.7.0 * @date 31-May-2016 * @brief Description of the I2C Two Boards Communication DMA example. ****************************************************************************** * * Redistribution and use in source and binary forms, with or without modification, * are permitted provided that the following conditions are met: * 1. Redistributions of source code must retain the above copyright notice, * this list of conditions and the following disclaimer. * 2. Redistributions in binary form must reproduce the above copyright notice, * this list of conditions and the following disclaimer in the documentation * and/or other materials provided with the distribution. * 3. Neither the name of STMicroelectronics nor the names of its contributors * may be used to endorse or promote products derived from this software * without specific prior written permission. * * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" * AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE * DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR * SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER * CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. * ****************************************************************************** @endverbatim @par Example Description This example guides you through the different configuration steps by mean of HAL API to ensure I2C Data buffer transmission and reception with DMA. The communication is done with 2 Boards through I2C. _________________________ _________________________ | ______________| |______________ | | | I2C1 | | I2C1| | | | | | | | | | SCL(PB8)|______________________|(PB8)SCL | | | | | | | | | | | | | | | | | | | | | | SDA(PB9)|______________________|(PB9)SDA | | | | | | | | | |______________| |______________| | | __ | | __ | | |__| | | |__| | | USER | | USER | | GND|______________________|GND | |_STM32L0 ________________| |_________________STM32L0_| At the beginning of the main program the HAL_Init() function is called to reset all the peripherals, initialize the Flash interface and the systick. Then the SystemClock_Config() function is used to configure the system clock (SYSCLK) to run at 32 MHz. The I2C peripheral configuration is ensured by the HAL_I2C_Init() function. This later is calling the HAL_I2C_MspInit()function which core is implementing the configuration of the needed I2C resources according to the used hardware (CLOCK, GPIO, DMA and NVIC). You may update this function to change I2C configuration. The I2C communication is then initiated. The project is splitted in two parts the Master Board and the Slave Board - Master Board The HAL_I2C_Master_Receive_DMA() and the HAL_I2C_Master_Transmit_DMA() functions allow respectively the reception and the transmission of a predefined data buffer in Master mode. - Slave Board The HAL_I2C_Slave_Receive_DMA() and the HAL_I2C_Slave_Transmit_DMA() functions allow respectively the reception and the transmission of a predefined data buffer in Slave mode. The user can choose between Master and Slave through "#define MASTER_BOARD" in the "main.c" file. If the Master board is used, the "#define MASTER_BOARD" must be uncommented. If the Slave board is used the "#define MASTER_BOARD" must be commented. For this example the aTxBuffer is predefined and the aRxBuffer size is same as aTxBuffer. In a first step after the user press the User Button on the Master Board, I2C Master starts the communication by sending aTxBuffer through HAL_I2C_Master_Transmit_DMA() to I2C Slave which receives aRxBuffer through HAL_I2C_Slave_Receive_DMA(). The second step starts when the user press the User Button on the Master Board, the I2C Slave sends aTxBuffer through HAL_I2C_Slave_Transmit_DMA() to the I2C Master which receives aRxBuffer through HAL_I2C_Master_Receive_DMA(). The end of this two steps are monitored through the HAL_I2C_GetState() function result. Finally, aRxBuffer and aRxBuffer are compared through Buffercmp() in order to check buffers correctness. LED2 can be used to monitor the transfer status: - LED2 turns OFF on master board waiting the transmission process is complete. - LED2 turns ON when the transmission/reception process is correct. @note I2Cx instance used and associated resources can be updated in "main.h" file depending hardware configuration used. @note Timeout is set to 10 Seconds which means that if no communication occurs during 10 Seconds, a Timeout Error will be generated. @note Care must be taken when using HAL_Delay(), this function provides accurate delay (in milliseconds) based on variable incremented in SysTick ISR. This implies that if HAL_Delay() is called from a peripheral ISR process, then the SysTick interrupt must have higher priority (numerically lower) than the peripheral interrupt. Otherwise the caller ISR process will be blocked. To change the SysTick interrupt priority you have to use HAL_NVIC_SetPriority() function. @note The application need to ensure that the SysTick time base is always set to 1 millisecond to have correct HAL operation. @par Directory contents - I2C/I2C_TwoBoards_ComDMA/Inc/stm32l0xx_hal_conf.h HAL configuration file - I2C/I2C_TwoBoards_ComDMA/Inc/stm32l0xx_it.h DMA interrupt handlers header file - I2C/I2C_TwoBoards_ComDMA/Inc/main.h Header for main.c module - I2C/I2C_TwoBoards_ComDMA/Src/stm32l0xx_it.c DMA interrupt handlers - I2C/I2C_TwoBoards_ComDMA/Src/main.c Main program - I2C/I2C_TwoBoards_ComDMA/Src/system_stm32l0xx.c STM32L0xx system source file - I2C/I2C_TwoBoards_ComDMA/Src/stm32l0xx_hal_msp.c HAL MSP file @par Hardware and Software environment - This example runs on STM32L051xx, STM32L052xx, STM32L053xx STM32L062xx and STM32L063xx device lines RevZ - This example has been tested with STM32L053R8-Nucleo RevC and can be easily tailored to any other supported device and development board. - STM32L053R8-Nucleo RevC Set-up - Connect Master board PB8 (Arduino SCL/D15) to Slave Board PB8 (Arduino SCL/D15) - Connect Master board PB9 (Arduino SDA/D14) to Slave Board PB9 (Arduino SDA/D14) - Connect Master board GND to Slave Board GND @par How to use it ? In order to make the program work, you must do the following : - Open your preferred toolchain - Rebuild all files and load your image into target memory o Uncomment "#define MASTER_BOARD" and load the project in Master Board o Comment "#define MASTER_BOARD" and load the project in Slave Board - Run the example *

© COPYRIGHT STMicroelectronics

*/

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：