文件列表:

SPI_FullDuplex_ComDMA (0, 2016-11-13)
SPI_FullDuplex_ComDMA\EWARM (0, 2016-11-13)
SPI_FullDuplex_ComDMA\EWARM\Project.ewd (36880, 2016-05-28)
SPI_FullDuplex_ComDMA\EWARM\Project.ewp (29074, 2016-05-28)
SPI_FullDuplex_ComDMA\EWARM\Project.eww (161, 2016-05-28)
SPI_FullDuplex_ComDMA\EWARM\startup_stm32l053xx.s (12049, 2016-05-31)
SPI_FullDuplex_ComDMA\EWARM\stm32l053xx_flash.icf (1353, 2016-05-28)
SPI_FullDuplex_ComDMA\Inc (0, 2016-11-13)
SPI_FullDuplex_ComDMA\Inc\main.h (4703, 2016-05-31)
SPI_FullDuplex_ComDMA\Inc\stm32l0xx_hal_conf.h (11203, 2016-05-31)
SPI_FullDuplex_ComDMA\Inc\stm32l0xx_it.h (3136, 2016-05-31)
SPI_FullDuplex_ComDMA\MDK-ARM (0, 2016-11-13)
SPI_FullDuplex_ComDMA\MDK-ARM\Project.uvoptx (4288, 2016-05-28)
SPI_FullDuplex_ComDMA\MDK-ARM\Project.uvprojx (20275, 2016-05-28)
SPI_FullDuplex_ComDMA\MDK-ARM\startup_stm32l053xx.s (11053, 2016-05-31)
SPI_FullDuplex_ComDMA\Src (0, 2016-11-13)
SPI_FullDuplex_ComDMA\Src\main.c (11105, 2016-05-31)
SPI_FullDuplex_ComDMA\Src\stm32l0xx_hal_msp.c (7934, 2016-05-31)
SPI_FullDuplex_ComDMA\Src\stm32l0xx_it.c (5214, 2016-05-31)
SPI_FullDuplex_ComDMA\Src\system_stm32l0xx.c (10325, 2016-05-31)
SPI_FullDuplex_ComDMA\SW4STM32 (0, 2016-11-13)
SPI_FullDuplex_ComDMA\SW4STM32\startup_stm32l053xx.s (10976, 2016-05-31)
SPI_FullDuplex_ComDMA\SW4STM32\STM32L053R8_NUCLEO (0, 2016-11-13)
SPI_FullDuplex_ComDMA\SW4STM32\STM32L053R8_NUCLEO\.cproject (11394, 2016-05-28)
SPI_FullDuplex_ComDMA\SW4STM32\STM32L053R8_NUCLEO\.project (4604, 2016-05-28)
SPI_FullDuplex_ComDMA\SW4STM32\STM32L053R8_NUCLEO\STM32L053R8Tx_FLASH.ld (4416, 2016-05-28)
SPI_FullDuplex_ComDMA\TrueSTUDIO (0, 2016-11-13)
SPI_FullDuplex_ComDMA\TrueSTUDIO\startup_stm32l053xx.s (10976, 2016-05-31)
SPI_FullDuplex_ComDMA\TrueSTUDIO\STM32L053R8_NUCLEO (0, 2016-11-13)
SPI_FullDuplex_ComDMA\TrueSTUDIO\STM32L053R8_NUCLEO\.cproject (19301, 2016-05-28)
SPI_FullDuplex_ComDMA\TrueSTUDIO\STM32L053R8_NUCLEO\.project (7050, 2016-05-28)
SPI_FullDuplex_ComDMA\TrueSTUDIO\STM32L053R8_NUCLEO\.settings (0, 2016-11-13)
SPI_FullDuplex_ComDMA\TrueSTUDIO\STM32L053R8_NUCLEO\.settings\com.atollic.truestudio.debug.hardware_device.prefs (219, 2016-05-28)
SPI_FullDuplex_ComDMA\TrueSTUDIO\STM32L053R8_NUCLEO\STM32L053R8_FLASH.ld (4501, 2016-05-28)
SPI_FullDuplex_ComDMA\TrueSTUDIO\STM32L053R8_NUCLEO\STM32L053R8_NUCLEO.elf.launch (5518, 2016-05-28)

/** @page SPI_FullDuplex_ComDMA SPI Full Duplex DMA example @verbatim ******************** (C) COPYRIGHT 2016 STMicroelectronics ******************* * @file SPI/SPI_FullDuplex_ComDMA/readme.txt * @author MCD Application Team * @version V1.7.0 * @date 31-May-2016 * @brief Description of the SPI Full Duplex 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 The communication is done with 2 boards through SPI. _________________________ _________________________ | ______________| |______________ | | |SPI2 | | SPI2| | | | | | | | | | CLK(PB13)|______________________|(PB13)CLK | | | | | | | | | | MISO(PB14)|______________________|(PB14)MISO | | | | | | | | | | MOSI(PB15)|______________________|(PB15)MOSI | | | | | | | | | |______________| |______________| | | __ | | __ | | |__| | | |__| | | USER | | USER | | GND|______________________|GND | | | | | |_STM32L0 ________________| |_STM32L0 ________________| This example guides you through the different configuration steps by mean of HAL API to ensure SPI Data buffer transmission and reception with DMA. HAL architecture allows user to easily change code to move to Polling or IT mode. To see others communication modes please check following examples: SPI\SPI_FullDuplex_ComPolling SPI\SPI_FullDuplex_ComIT 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 2 MHz. The SPI peripheral configuration is ensured by the HAL_SPI_Init() function. This later is calling the HAL_SPI_MspInit()function which core is implementing the configuration of the needed SPI resources according to the used hardware (CLOCK, GPIO, DMA and NVIC). You may update this function to change SPI configuration. The SPI communication is then initiated. The HAL_SPI_TransmitReceive_DMA() function allows the reception and the transmission of a predefined data buffer at the same time (Full Duplex 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 Key, SPI Master starts the communication by sending aTxBuffer and receiving aRxBuffer through HAL_SPI_TransmitReceive_DMA(), at the same time SPI Slave transmits aTxBuffer and receives aRxBuffer through HAL_SPI_TransmitReceive_DMA(). The end of this step is monitored through the HAL_SPI_GetState() function result. Finally, aRxBuffer and aTxBuffer are compared through Buffercmp() in order to check buffers correctness. LED2 can be used to monitor the transfer status: - LED2 turns ON on master board waiting user button to be pressed. - LED2 turns OFF on master board waiting the transmission process is complete. - LED2 turns ON when the transmission/reception process is correct. @note SPIx instance used and associated resources can be updated in "main.h" file depending hardware configuration used. @note You need to perform a reset on Slave board, then perform it on Master board to have the correct behaviour of this example. @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 - SPI/SPI_FullDuplex_ComDMA/Inc/stm32l0xx_hal_conf.h HAL configuration file - SPI/SPI_FullDuplex_ComDMA/Inc/stm32l0xx_it.h Interrupt handlers header file - SPI/SPI_FullDuplex_ComDMA/Inc/main.h Header for main.c module - SPI/SPI_FullDuplex_ComDMA/Src/stm32l0xx_it.c Interrupt handlers - SPI/SPI_FullDuplex_ComDMA/Src/main.c Main program - SPI/SPI_FullDuplex_ComDMA/Src/stm32l0xx_hal_msp.c HAL MSP module - SPI/SPI_FullDuplex_ComDMA/Src/system_stm32l0xx.c STM32L0xx system source 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 PB13 (pin 30 in CN10 connector) to Slave Board PB13 - Connect Master board PB14 (pin 28 in CN10 connector) to Slave Board PB14 - Connect Master board PB15 (pin 26 in CN10 connector) to Slave Board PB15 - Connect Master board GND to Slave Board GND - SB35 ON - SB44 OFF - SB28 ON - SB39 OFF - SB25 ON - SB36 OFF @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

*/

近期下载者：

相关文件：

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

收藏者：