mirror of
https://github.com/STMicroelectronics/STM32CubeF4.git
synced 2025-05-11 19:29:45 +08:00
139 lines
7.4 KiB
Plaintext
139 lines
7.4 KiB
Plaintext
/**
|
|
@page SPI_FullDuplex_ComPolling SPI Two Boards Communication example
|
|
|
|
@verbatim
|
|
******************** (C) COPYRIGHT 2017 STMicroelectronics *******************
|
|
* @file Examples_MIX/SPI/SPI_FullDuplex_ComPolling/readme.txt
|
|
* @author MCD Application Team
|
|
* @brief Description of the SPI Full Duplex Polling 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 shows how to ensure SPI data buffer transmission/reception in Polling
|
|
mode between two boards.
|
|
|
|
_________________________ _________________________
|
|
| ________CN7_______| |_______CN7__________ |
|
|
| |SPI3 | | SPI3 | |
|
|
| | | | | |
|
|
| |(pin 1) CLK(PC10)|______________________|(PC10)CLK (pin 1) | |
|
|
| | | | | |
|
|
| |(pin 2) MISO(PC11)|______________________|(PC11)MISO (pin 2) | |
|
|
| | | | | |
|
|
| |(pin 3) MOSI(PC12)|______________________|(PC12)MOSI (pin 3) | |
|
|
| | | | | |
|
|
| |__________________| |____________________| |
|
|
| __ | | |
|
|
| |__| | | |
|
|
| USER | | |
|
|
| GND|______________________|GND |
|
|
| | | |
|
|
|_STM32F4 Master _________| |_STM32F4 Slave __________|
|
|
|
|
|
|
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 100 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). You may update this function to change SPI configuration.
|
|
The Full-Duplex SPI transfer (16bit) is done using LL Driver functions
|
|
LL_SPI_TransmitData16 and LL_SPI_ReceiveData16.
|
|
|
|
Example execution:
|
|
First step, press the User push-button, this action initiates a Full-Duplex transfer
|
|
between Master and Slave.
|
|
After end of transfer, aRxBuffer and aTxBuffer are compared through Buffercmp() in order to
|
|
check buffers correctness.
|
|
|
|
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.
|
|
|
|
STM32 board's LEDs can be used to monitor the transfer status:
|
|
- LED2 toggles quickly on master board waiting User push-button to be pressed.
|
|
- LED2 turns ON on both board if transmission/reception is complete and OK.
|
|
- LED2 toggles slowly when there is a timeout or an error in transmission/reception process.
|
|
|
|
@note SPIx instance used and associated resources can be updated in "main.h"
|
|
file depending hardware configuration used.
|
|
|
|
|
|
@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
|
|
|
|
- Examples_MIX/SPI/SPI_FullDuplex_ComPolling/Inc/stm32f4xx_hal_conf.h HAL configuration file
|
|
- Examples_MIX/SPI/SPI_FullDuplex_ComPolling/Inc/stm32f4xx_it.h SPI interrupt handlers header file
|
|
- Examples_MIX/SPI/SPI_FullDuplex_ComPolling/Inc/main.h Header for main.c module
|
|
- Examples_MIX/SPI/SPI_FullDuplex_ComPolling/Src/stm32f4xx_it.c SPI interrupt handlers
|
|
- Examples_MIX/SPI/SPI_FullDuplex_ComPolling/Src/main.c Main program
|
|
- Examples_MIX/SPI/SPI_FullDuplex_ComPolling/Src/system_stm32f4xx.c STM32F4xx system source file
|
|
- Examples_MIX/SPI/SPI_FullDuplex_ComPolling/Src/stm32f4xx_hal_msp.c HAL MSP file
|
|
|
|
|
|
@par Hardware and Software environment
|
|
|
|
- This example runs on STM32F411RE devices.
|
|
|
|
- Take care to cable connection between Master and Slave Board:
|
|
Cable shall be smaller than 5 cm and rigid if possible.
|
|
|
|
- This example has been tested with NUCLEO-F411RE board and can be
|
|
easily tailored to any other supported device and development board.
|
|
|
|
- NUCLEO-F411RE Set-up
|
|
- Connect Master board PC10 to Slave Board PC10 (pin 1 in CN7 connector)
|
|
- Connect Master board PC11 to Slave Board PC11 (pin 2 in CN7 connector)
|
|
- Connect Master board PC12 to Slave Board PC12 (pin 3 in CN7 connector)
|
|
- 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
|
|
|
|
* <h3><center>© COPYRIGHT STMicroelectronics</center></h3>
|
|
*/
|
|
|