142 lines
7.5 KiB
Plaintext
142 lines
7.5 KiB
Plaintext
/**
|
|
@page SPI_FullDuplex_ComPolling_Slave SPI Full Duplex Polling example
|
|
|
|
@verbatim
|
|
******************************************************************************
|
|
* @file SPI/SPI_FullDuplex_ComPolling_Slave/readme.txt
|
|
* @author MCD Application Team
|
|
* @brief Description of the SPI Full Duplex Polling example.
|
|
******************************************************************************
|
|
*
|
|
* Copyright (c) 2020 STMicroelectronics. All rights reserved.
|
|
*
|
|
* This software component is licensed by ST under BSD 3-Clause license,
|
|
* the "License"; You may not use this file except in compliance with the
|
|
* License. You may obtain a copy of the License at:
|
|
* opensource.org/licenses/BSD-3-Clause
|
|
*
|
|
******************************************************************************
|
|
@endverbatim
|
|
|
|
@par Example Description
|
|
|
|
Data buffer transmission/reception between two boards via SPI using Polling mode.
|
|
|
|
Board: NUCLEO-WL55JC RevC (embeds a STM32WL55JC device)
|
|
CLK Pin: PA5 (pin 11 on CN10 connector (Arduino pin 6 CN5))
|
|
MISO Pin: PA6 (pin 13 on CN10 connector (Arduino pin 5 CN5))
|
|
MOSI Pin: PA7 (pin 15 on CN10 connector (Arduino pin 4 CN5))
|
|
_________________________ __________________________
|
|
| ______________| |______________ |
|
|
| |SPI1 | | SPI1| |
|
|
| | | | | |
|
|
| | CLK(PA.05)|______________________|CLK(PA.05) | |
|
|
| | | | | |
|
|
| | MISO(PA.06)|______________________|MISO(PA.06) | |
|
|
| | | | | |
|
|
| | MOSI(PA.07)|______________________|MOSI(PA.07) | |
|
|
| | | | | |
|
|
| |______________| |______________| |
|
|
| __ | | |
|
|
| |__| | | |
|
|
| User push-button (B1) | | |
|
|
| GND|______________________|GND |
|
|
| | | |
|
|
|_STM32WLxx Master________| |_STM32WLxx Slave_________|
|
|
|
|
HAL architecture allows user to easily change code to move to IT or DMA mode.
|
|
To see others communication modes please check following examples:
|
|
SPI\SPI_FullDuplex_ComDMA_Master and SPI\SPI_FullDuplex_ComDMA_Slave
|
|
SPI\SPI_FullDuplex_ComIT_Master and SPI\SPI_FullDuplex_ComIT_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 48 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 SPI communication is then initiated.
|
|
The HAL_SPI_TransmitReceive() function allows the reception and the
|
|
transmission of a predefined data buffer at the same time (Full Duplex Mode).
|
|
If the Master board is used, the project SPI_FullDuplex_ComPolling_Master must be used.
|
|
If the Slave board is used, the project SPI_FullDuplex_ComPolling_Slave must be used.
|
|
|
|
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 push-button (B1), SPI Master starts the
|
|
communication by sending aTxBuffer and receiving aRxBuffer through
|
|
HAL_SPI_TransmitReceive(), at the same time SPI Slave transmits aTxBuffer
|
|
and receives aRxBuffer through HAL_SPI_TransmitReceive().
|
|
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.
|
|
|
|
@note Timeout is set to 5 seconds which means that if no communication occurs during 5 seconds,
|
|
a timeout error is generated.
|
|
|
|
STM32 board's LEDs can be used to monitor the transfer status:
|
|
- LED1 toggles quickly on master board waiting User push-button (B1) to be pressed.
|
|
- LED1 turns ON when the transmission process is complete.
|
|
- LED2 turns ON when the reception process is complete.
|
|
- LED3 turns ON when there is an error in transmission/reception process.
|
|
- LED3 toggles when there is a timeout error in transmission/reception process.
|
|
|
|
@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 Keywords
|
|
|
|
Connectivity, SPI, Full-duplex, Polling, Transmission, Reception, Master, Slave, MISO, MOSI,
|
|
|
|
@par Directory contents
|
|
|
|
- SPI/SPI_FullDuplex_ComPolling_Slave/Inc/stm32wlxx_nucleo_conf.h BSP configuration file
|
|
- SPI/SPI_FullDuplex_ComPolling_Slave/Inc/stm32wlxx_hal_conf.h HAL configuration file
|
|
- SPI/SPI_FullDuplex_ComPolling_Slave/Inc/stm32wlxx_it.h Interrupt handlers header file
|
|
- SPI/SPI_FullDuplex_ComPolling_Slave/Inc/main.h Header for main.c module
|
|
- SPI/SPI_FullDuplex_ComPolling_Slave/Src/stm32wlxx_it.c Interrupt handlers
|
|
- SPI/SPI_FullDuplex_ComPolling_Slave/Src/main.c Main program
|
|
- SPI/SPI_FullDuplex_ComPolling_Slave/Src/system_stm32wlxx.c stm32wlxx system source file
|
|
- SPI/SPI_FullDuplex_ComPolling_Slave/Src/stm32wlxx_hal_msp.c HAL MSP file
|
|
|
|
@par Hardware and Software environment
|
|
|
|
- This example runs on STM32WL55JCIx devices.
|
|
|
|
- This example has been tested with NUCLEO-WL55JC RevC board and can be
|
|
easily tailored to any other supported device and development board.
|
|
|
|
- NUCLEO-WL55JC RevC Set-up
|
|
- Connect Master board PA5 (pin 11 on CN10 connector (Arduino pin 6 CN5)) to Slave Board PA5 (pin 11 on CN10 connector (Arduino pin 6 CN5))
|
|
- Connect Master board PA6 (pin 13 on CN10 connector (Arduino pin 5 CN5)) to Slave Board PA6 (pin 13 on CN10 connector (Arduino pin 5 CN5))
|
|
- Connect Master board PA7 (pin 15 on CN10 connector (Arduino pin 4 CN5)) to Slave Board PA7 (pin 15 on CN10 connector (Arduino pin 4 CN5))
|
|
- 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 (master project) and load your image into target memory
|
|
o Load the project in Master Board
|
|
- Rebuild all files (slave project) and load your image into target memory
|
|
o Load the project in Slave Board
|
|
- Run the example
|
|
|
|
* <h3><center>© COPYRIGHT STMicroelectronics</center></h3>
|
|
*/
|
|
|