1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
|
/**
@page SPI_FullDuplex_ComIT_Slave SPI Full Duplex IT example
@verbatim
******************************************************************************
* @file SPI/SPI_FullDuplex_ComIT_Slave/readme.txt
* @author MCD Application Team
* @brief Description of the SPI Full Duplex IT example.
******************************************************************************
*
* Copyright (c) 2019 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 Interrupt mode.
Board: P-NUCLEO-WB55 (embeds a STM32WB55RG device)
CLK Pin: PA5 (CN10, pin 11)
MISO Pin: PA6 (CN10, pin 13)
MOSI Pin: PA7 (CN10, pin 15)
_________________________ __________________________
| ______________| |______________ |
| |SPI1 | | SPI1| |
| | | | | |
| | CLK(PA.05)|______________________|CLK(PA.05) | |
| | | | | |
| | MISO(PA.06)|______________________|MISO(PA.06) | |
| | | | | |
| | MOSI(PA.07)|______________________|MOSI(PA.07) | |
| | | | | |
| |______________| |______________| |
| __ | | |
| |__| | | |
| User push-button (SW1) | | |
| GND|______________________|GND |
| | | |
|_STM32WBxx Master________| |_STM32WBxx Slave_________|
HAL architecture allows user to easily change code to move to DMA or Polling
mode. To see others communication modes please check following examples:
SPI\SPI_FullDuplex_ComPolling_Master and SPI\SPI_FullDuplex_ComPolling_Slave
SPI\SPI_FullDuplex_ComDMA_Master and SPI\SPI_FullDuplex_ComDMA_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 64 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 and NVIC). You may update this function to change SPI configuration.
The SPI communication is then initiated.
The HAL_SPI_TransmitReceive_IT() 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_ComIT_Master must be used.
If the Slave board is used, the project SPI_FullDuplex_ComIT_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 (SW1), SPI Master starts the
communication by sending aTxBuffer and receiving aRxBuffer through
HAL_SPI_TransmitReceive_IT(), at the same time SPI Slave transmits aTxBuffer
and receives aRxBuffer through HAL_SPI_TransmitReceive_IT().
The callback functions (HAL_SPI_TxRxCpltCallback and HAL_SPI_ErrorCallbackand) update
the variable wTransferState used in the main function to check the transfer status.
Finally, aRxBuffer and aTxBuffer are compared through Buffercmp() in order to
check buffers correctness.
STM32 board's LEDs can be used to monitor the transfer status:
- LED1 toggles quickly on master board waiting User push-button (SW1) 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.
@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, Interrupt, Transmission, Reception, Master, Slave, MISO, MOSI
@par Directory contents
- SPI/SPI_FullDuplex_ComIT_Slave/Inc/stm32wbxx_hal_conf.h HAL configuration file
- SPI/SPI_FullDuplex_ComIT_Slave/Inc/stm32wbxx_it.h Interrupt handlers header file
- SPI/SPI_FullDuplex_ComIT_Slave/Inc/main.h Header for main.c module
- SPI/SPI_FullDuplex_ComIT_Slave/Src/stm32wbxx_it.c Interrupt handlers
- SPI/SPI_FullDuplex_ComIT_Slave/Src/main.c Main program
- SPI/SPI_FullDuplex_ComIT_Slave/Src/system_stm32wbxx.c stm32wbxx system source file
- SPI/SPI_FullDuplex_ComIT_Slave/Src/stm32wbxx_hal_msp.c HAL MSP file
@par Hardware and Software environment
- This example runs on STM32WB55xx devices.
- This example has been tested with P-NUCLEO-WB55 board and can be
easily tailored to any other supported device and development board.
- P-NUCLEO-WB55 Set-up
- Connect Master board PA5 (CN10, pin 11) to Slave Board PA5 (CN10, pin 11)
- Connect Master board PA6 (CN10, pin 13) to Slave Board PA6 (CN10, pin 13)
- Connect Master board PA7 (CN10, pin 15) to Slave Board PA7 (CN10, pin 15)
- 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>
*/
|
