You will need to dedicate one pin on your controller as a separate CS line for each peripheral you wish to communicate with. All of the lines are shared except for the CS line. SPI is a bus, which means you can use multiple peripheral devices for one controller. Note that for STM32 parts, the shared data line for half-duplex communication should be connected to the SDO (or MOSI) pin. The shared data line might be labeled as serial in/out (SI/O, SIO) or serial data in/out (SDIO). Sometimes, you will come across devices that only support half-duplex mode in order to save pins. Select: chip select (CS), slave select (SS)īy default, SPI is full-duplex, which means you can transmit and receive at the same time.

Controller data in: serial data in (SDI), master in slave out (MISO), controller in slave out (CIPO) (note that the SDI pin of the controller should be connected to the SDO pin of the controller).

Controller data out: serial data out (SDO), master out slave in (MOSI), controller out peripheral in (COPI) (note that the SDO pin of the controller should be connected to the SDI pin of the peripheral).

Note that because SPI is a de facto standard, you will come across different names for the lines: The first, and probably most common, is the simple point-to-point connection scheme. SPI can be connected in a variety of configurations. You will find many hardware peripheral devices that support SPI, including sensors like accelerometers, memory chips (e.g. I find that speeds in the 1-10 MHz range work well for most of my needs (and work well enough on breadboards).

However, you will often run into transmission line issues (cross talk, spurious signals, weak signals, etc.) when working above a few MHz. Because SPI is a synchronous communication scheme (there is a separate clock line), it can theoretically work up to any speed. SPI is often used when a simple communication scheme is needed with faster speeds than what UART and I2C can provide. As a result, it has become a de facto standard in the industry. It was never formalized into a standard, but other companies started using it soon after. Serial Peripheral Interface (SPI) was created by Motorola in the 1980s as a way to communicate between a microcontroller and various peripherals. See Matrix of tested boards.Please refer to this tutorial if you need a refresher on using STM32CubeIDE and working with GPIO in HAL. These headers give access to all STM32 pins.

mbed-dev library in (source files of the mbed library used on mbed compiler IDE).ARMmbed/mbed-os repository on GitHub ( up-to-date version, used with mbed CLI commands).You can find more details on the available pins and labels in the PeripheralPins.c and PinNames.h files. Mass storage (USB Disk drive) for drag'n'drop programming.USB re-enumeration capability: three different interfaces supported on USB.USB VBUS or external source (3.3 V, 5 V, 7 - 12 V).Selection-mode switch to use the kit as a standalone ST-LINK/V2-1.On-board ST-LINK/V2-1 debugger/programmer with SWD connector.STMicroelectronics Morpho extension pin headers for full access to all STM32 I/Os.GPIO (51) with external interrupt capability.Adaptive real-time accelerator (ART Accelerator™) allowing 0-wait state execution from Flash memory.The STM32 Nucleo board does not require any separate probe as it integrates the ST-LINK/V2-1 debugger/programmer. The Arduino™ connectivity support and ST Morpho headers make it easy to expand theįunctionality of the STM32 Nucleo open development platform with a wide choice of The STM32 Nucleo board provides an affordable and flexible way for users to try out new ideas and build prototypes with any STM32 microcontroller line, choosing from the various combinations of performance, power consumption and features.

Nucleo stm32 schematic