163 lines
8.1 KiB
Plaintext
163 lines
8.1 KiB
Plaintext
/**
|
|
@page SPI_FullDuplex_AdvComIT SPI Full Duplex Interrupt example
|
|
|
|
@verbatim
|
|
******************** (C) COPYRIGHT 2017 STMicroelectronics *******************
|
|
* @file SPI/SPI_FullDuplex_AdvComIT/Readme.txt
|
|
* @author MCD Application Team
|
|
* @brief Description of the SPI Full Duplex Interrupt example.
|
|
******************************************************************************
|
|
* @attention
|
|
*
|
|
* Copyright (c) 2017 STMicroelectronics.
|
|
* All rights reserved.
|
|
*
|
|
* This software is licensed under terms that can be found in the LICENSE file
|
|
* in the root directory of this software component.
|
|
* If no LICENSE file comes with this software, it is provided AS-IS.
|
|
*
|
|
******************************************************************************
|
|
@endverbatim
|
|
|
|
@par Example Description
|
|
|
|
Configuration of the HAL SPI API to transmit/receive a data buffer using Interrupt mode
|
|
in an advanced communication mode:
|
|
The master board always sends the command to the slave before performing any transmission;
|
|
the slave board sends back an acknowledgement before proceeding.
|
|
|
|
- Hardware Description
|
|
|
|
To use this example, you need to load it on two STM32 boards (let's call them
|
|
BoardA and BoardB) then connect these two boards through SPI lines and GND.
|
|
In the firmware example two project are provided to use the SPI peripheral as STM32
|
|
Master device or as STM32 Slave .
|
|
_________________________ _________________________
|
|
| ______________| |______________ |
|
|
| |SPI3 | | SPI3| |
|
|
| | | | | |
|
|
| | CLK(PC10)|______________________|(PC10)CLK | |
|
|
| | | | | |
|
|
| | MISO(PC11)|______________________|(PC11)MISO | |
|
|
| | | | | |
|
|
| | MOSI(PC12)|______________________|(PC12)MOSI | |
|
|
| | | | | |
|
|
| |______________| |______________| |
|
|
| __ | | |
|
|
| |__| | | |
|
|
| USER | | |
|
|
| GND|______________________|GND |
|
|
| | | |
|
|
|_STM322xG________________| |_STM322xG________________|
|
|
|
|
- Software Description
|
|
|
|
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 120 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 peripheral is configured in full duplex mode with baudrate = FCPU/128.
|
|
|
|
In Master board, when the user button is pressed (used for only synchronization at startup)
|
|
these steps are executed:
|
|
- Synchro with the Slave
|
|
- Requests read operation by sending specific command to the slave that contain
|
|
the master read command and the number of data to be read
|
|
- Synchro with the Slave
|
|
- Receive the ACK from the Slave
|
|
- Synchro with the Slave
|
|
- Receive the requested data "aRxBuffer" from the slave
|
|
- Synchro with the Slave
|
|
- Send the ACK to the Slave
|
|
- Checks the correctness of data and in case of mismatch between sent and received data,
|
|
LED3 is On and communication is stopped (using infinite loop). Otherwise LED2 is Toggle
|
|
indicate that the data is received correctly.
|
|
- Synchro with the Slave
|
|
- Requests write operation by sending specific command to the slave that contain
|
|
the master write command and the number of data to be written
|
|
- Synchro with the Slave
|
|
- Receive the ACK from the Slave
|
|
- Synchro with the Slave
|
|
- Send the requested data "aTxMasterBuffer" to the slave
|
|
- Synchro with the Slave
|
|
- Receive the ACK from the Slave
|
|
These previously steps are repeated in an infinitely loop and a delay 100ms is inserted at
|
|
the end of data transfer to permit the user to see LED4 toggling.
|
|
|
|
In Slave board, these steps are executed:
|
|
- Synchro with the Master
|
|
- Receive requests from the master
|
|
- Synchro with the Master
|
|
- Send the ACK to the Master
|
|
- Synchro with the Master
|
|
- If the "ADDRCMD_MASTER_READ" command is received:
|
|
- Send the requested data "aTxSlaveBuffer" to the Master
|
|
- Synchro with the Master
|
|
- Receive the ACK from the Master
|
|
- If the "ADDRCMD_MASTER_WRITE" command is received:
|
|
- Receive the requested data "aRxBuffer" from the Master
|
|
- Synchro with the Master
|
|
- Send the ACK to the Master
|
|
- checks the correctness of data is performed and in case of mismatch between sent and
|
|
received data, LED3 is On and communication is stopped (using infinite loop).
|
|
Otherwise LED2 Toggles indicating that the data is received correctly.
|
|
|
|
These previously steps are repeated in an infinitely loop.
|
|
|
|
STM322xG-EVAL board's LEDs can be used to monitor the transfer status:
|
|
- LED1 (green) toggles on Master board waiting for user button to be pushed.
|
|
- LED2 (orange) toggles on Master side at end of each loop.
|
|
- LED4 (blue) toggles on when the read comparison is OK.
|
|
- LED3 (red) turns ON when there is 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
|
|
|
|
- SPI/SPI_FullDuplex_AdvComIT/Inc/stm32f2xx_hal_conf.h HAL configuration file
|
|
- SPI/SPI_FullDuplex_AdvComIT/Inc/stm32f2xx_it.h SPI interrupt handlers header file
|
|
- SPI/SPI_FullDuplex_AdvComIT/Inc/main.h Header for main.c module
|
|
- SPI/SPI_FullDuplex_AdvComIT/Src/stm32f2xx_it.c SPI interrupt handlers
|
|
- SPI/SPI_FullDuplex_AdvComIT/Src/main.c Main program
|
|
- SPI/SPI_FullDuplex_AdvComIT/Src/system_stm32f2xx.c STM32F2xx system source file
|
|
- SPI/SPI_FullDuplex_AdvComIT/Src/stm32f2xx_hal_msp.c HAL MSP file
|
|
|
|
|
|
@par Hardware and Software environment
|
|
- This example runs on STM32F2xxxx devices.
|
|
- This example has been tested with STMicroelectronics STM322xG-EVAL RevC
|
|
boards and can be easily tailored to any other supported device
|
|
and development board.
|
|
|
|
- STM322xG-EVAL Set-up
|
|
- Use LED1, LED2, LED3 and LED4 connected respectively to PG.6, PG.8, PG.9
|
|
and PG.7 pins
|
|
- Use the USer Push Button
|
|
- Connect BoardA SPI3 SCK pin (PC10) to BoardB SPI3 SCK pin (PC10) (Pin36 in CN4)
|
|
- Connect BoardA SPI3 MOSI pin (PC12) to BoardB SPI2 MOSI pin (PC12) (Pin34 in CN4)
|
|
- Connect BoardA SPI3 MISO pin (PC11) to BoardB SPI2 MOSI pin (PC11) (Pin35 in CN4)
|
|
- Connect BoardA GND to BoardB 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
|
|
- Firstly, Run the Master example, then run the Slave example
|
|
|
|
*/
|