STMicroelectronics X-NUCLEO-S2868A1 User Manual
Pubblicità
Pubblicità
UM1904
User manual
Getting started with X-CUBE-SUBG1, Sub-1 GHz RF software expansion for
STM32Cube
Introduction
X-CUBE-SUBG1 is an expansion software package for STM32Cube . The software runs on the STM32 and includes drivers that recognize the Sub-1 GHz RF communication for SPIRIT1 SPSGRF modules and S2-LP .
The expansion is built on STM32Cube software technology to ease portability across different STM32 microcontrollers.
The software comes with sample applications of P2P, wM-Bus and 6LoWPAN communication protocols, running on a compatible SPIRIT1 or S2-LP expansion board when connected to a compatible STM32 Nucleo development board.
RELATED LINKS
Visit the STM32Cube ecosystem web page on www.st.com for further information
UM1904 - Rev 4 - December 2019
For further information contact your local STMicroelectronics sales office.
www.st.com
1 Acronyms and abbreviations
Acronym
AMR
BSP
EEPROM
GHz
GUI
HAL
LED
MCU
P2P
RF
SPI
USB wM-Bus
WSN
Table 1. List of acronyms
Description
Automatic meter reading
Board support package
Electrically erasable programmable read-only memory
Giga Hertz
Graphical user interface
Hardware abstraction layer
Light emitting diode
Microcontroller unit
Point-to-Point communication
Radio frequency communication
Serial peripheral interface
Universal serial bus
Wireless metering bus
Wireless sensor network
UM1904
Acronyms and abbreviations
UM1904 - Rev 4 page 2/29
2
2.1
UM1904
X-CUBE-SUBG1 software expansion for STM32Cube
X-CUBE-SUBG1 software expansion for STM32Cube
Overview
•
•
•
•
•
•
•
X-CUBE-SUBG1 is a software package that expands the functionality of STM32Cube .
The key features of the package are:
Firmware package to start developing using SPIRIT1 or S2-LP expansion boards
Complete middleware to build wireless meter bus (wM-Bus) applications using the wM-Bus library ( X-
NUCLEO-S2868A2 and X-NUCLEO-IDS01A4 only)
•
•
Middleware library with Contiki OS and Contiki 6LoWPAN protocol stack 3.x ( NUCLEO-F401RE and
NUCLEO-L152RE only)
Point-to-point communication sample application for simple buffer transmission and acknowledgement implementation
Low-power optimizations for the STM32 MCU family
Easy portability across different MCU families thanks to STM32Cube
PC-based application (Windows ® ) for wM-Bus to log meter data
Free user-friendly license terms
Sample implementation available on X-NUCLEO-IDS01A4 or X-NUCLEO-IDS01A5 and X-NUCLEO-
S2868A2 or X-NUCLEO-S2915A1 expansion boards when connected to NUCLEO-F401RE , NUCLEO-
L053R8 or NUCLEO-L152RE boards
•
•
•
•
Starting from this software, it is possible to develop other applications, such as:
• automatic meter reading home and building automation
WSN (wireless sensors network) industrial monitoring and control wireless fire and security alarm systems
The firmware partitioning among the STM32 microcontroller on the STM32 Nucleo development boards, the
SPIRIT1 and the S2-LP is:
• STM32 MCU
– P2P application implementation
– low power mode handling
•
– interrupt services
SPIRIT1 role
– basic/stack modes
– header, sync and trailer fields
– encoding/decoding
– sync detection
•
– TX and RX FIFO
S2-LP role
– basic/stack modes
– header, sync and trailer fields
– encoding/decoding
– sync detection
– RX and TX 128 bytes FIFO buffers
– IEEE 802.15.4g hardware packet support with whitening, FEC, CRC and dual sync word detection.
UM1904 - Rev 4 page 3/29
2.2
UM1904
Architecture
Architecture
This software is fully compliant with and expands STM32Cube to enable development of applications using X-
NUCLEO-IDS01Ax ( X- NUCLEO-IDS01A4 or X-NUCLEO-IDS01A5 ) or X-NUCLEO-S2868A2 / X-NUCLEO-
S2915A1 boards hosting the SPIRIT1 and S2-LP devices.
The software is based on the STM32CubeHAL hardware abstraction layer for the STM32 microcontroller. The package extends STM32Cube by providing a board support package (BSP) for the SPIRIT1 or S2-LP expansion board and some example firmware for P2P communication.
The software layers used by the application software to access and use the SPIRIT1 or S2-LP expansion board are:
• STM32Cube HAL layer: provides a generic, multi-instance set of APIs to interact with the upper layers (the application, libraries and stacks). It consists of generic and extension APIs based on a common architecture which allows other layers like the middleware layer to function without specific Microcontroller Unit (MCU) hardware configurations. This structure improves library code reusability and guarantees easy device portability.
• Board support package (BSP) Layer: includes the software to support the peripherals on the STM32 Nucleo board (apart from the MCU). It is a set of APIs which provides a programming interface for certain boardspecific peripherals (LED, user button etc.). The BSP firmware layer of the X-NUCLEO-IDS01Ax boards contains APIs for the hardware components and consists of two parts:
– Component: this is the driver related to the external device on the board and not related to the STM32.
The SPIRIT1 BSP driver is known as the firmware component. The SPIRIT1 component driver provides specific APIs and can be ported to and used on any board.
•
•
– BSP driver: enables the component driver to be linked to a specific board and provides a set of userfriendly APIs.
Middleware: includes the wM-Bus, USB, touch sensing etc. libraries. There is no middleware component For
Point-to-Point applications as the demo/application layer interacts with the SPIRIT1 link layer directly
Application layer: provides a Point-to-Point communication example which involves sending a buffer from one node to another and acknowledgments using the features in the SPIRIT1 link layer.
Figure 1. X-CUBE-SUBG1 software architecture
Application
Applications
(Border Router, UDP Sender, UDP Receiver, P2P, wM-Bus)
Middleware
Hardware
Abstraction
6LoWPAN wM-Bus
STM32Cube Hardware Abstraction Layer (HAL)
Hardware
STM32 Nucleo expansion boards
X-NUCLEO-IDS01A4/X-NUCLEO-IDS01A5 (Connect)
X-NUCLEO-S2868A2/X-NUCLEO-S2915A1 (Connect)
STM32 Nucleo development board
UM1904 - Rev 4 page 4/29
2.3
Folder structure
Figure 2. X-CUBE-SUBG1 package folder structure
UM1904
Folder structure
2.4
2.5
•
•
The following folders are included in the software package:
• ‘Documentation’: contains a compiled HTML file generated from the source code and detailed documentation of the software components and APIs
• ‘Drivers’: contains the HAL drivers and the board-specific drivers for supported board and hardware platforms, including those for the on-board components and the CMSIS vendor-independent hardware abstraction layer for the Cortex-M processor series
‘Middlewares’: contains libraries for wM-Bus and 6LoWPAN protocol stack
•
‘Projects’: contains a sample application used for wM-Bus and P2P firmware examples for the NUCLEO-
L053R8 and NUCLEO-F401RE or NUCLEO-L152RE platforms with three development environments, IAR
Embedded Workbench for ARM ( IAR-EWARM ), RealView Microcontroller Development Kit ( MDK-ARM-
STR ), System Workbench for STM32 ( SW4STM32 )
‘Utilities’: this folder contains a ‘PC_software’ subfolder with a Windows PC utility for wM-Bus usage and testing.
APIs
Detailed descriptions of all the functions and parameters of the user APIs user can be found in a compiled HTML file located inside the ‘Documentation’ folder.
Selecting radio board configuration
X-CUBE-SUBG1 software package supports both SPIRIT1 and S2-LP radio application in a single package.
The figure below shows how to select the firmware configuration in the workspace, according to the radio used
( SPIRIT1 or S2-LP ).
UM1904 - Rev 4 page 5/29
UM1904
Selecting radio board configuration
Figure 3. Selecting the radio board firmware configuration
UM1904 - Rev 4 page 6/29
3
3.1
UM1904
Point-to-Point (P2P) demo firmware description
Point-to-Point (P2P) demo firmware description
The following section explains how the demo firmware is implemented, the user settings and configurations available and how to modify the firmware for other applications.
P2P application details
The P2P application operates using two nodes ( STM32 Nucleo board plus SPIRIT1 or S2-LP expansion board) as follows:
1.
by pressing the STM32 Nucleo board user button (shown in the picture below), each node can transmit a buffer to the other node
2.
on receiving the signal, the receiver node LED lights up and an acknowledgment (ACK) signal is returned to the transmitter node
3.
on reception of the ACK signal, the transmitter node LED flashes four times and switches off after a delay period
Figure 4. X-NUCLEO-IDS01Ax plus STM32 Nucleo used as a node (transmitter/receiver) in P2P communication
3.2
Application state diagram
This section explains how to run the demo sample with the STM32 Nucleo boards.
SPIRIT1 or S2-LP remains by default in receive mode but changes to transmit mode when the user button is pressed. Once transmission has terminated, the transceiver returns to its default receive mode. On successful completion of the two-way communication (Command/ Ack), the MCU enters low-power mode.
To limit low-power mode current consumption, the LED is switched off by default.
P2P nodes have the same functionality; the address of each node is set in the firmware by the user.
UM1904 - Rev 4 page 7/29
UM1904 - Rev 4
UM1904
Application state diagram
Figure 5. Application state diagram when Node 1 user button is pressed
If the user presses the other node user button, the functionality is the same: Node 2 wakes up from low-power mode, prepares the command for transmission, sends the data packet and waits for acknowledgment.
Figure 6. Application state diagram when Node 2 user button is pressed page 8/29
UM1904
SPIRIT1 packet handler overview
The following diagram shows the transmit and receive states for data communication in the firmware low-power mode.
Figure 7. Application state diagram (low-power mode)
3.3
SPIRIT1 packet handler overview
Before on-air transmission, raw data is arranged in a packet structure. SPIRIT1 offers a highly flexible and fully programmable packet which lets you configure the structure of the packet, the number, the type, and the dimension of the fields inside the packet.
Through a register, the user can choose from one of the formats shown in the tables below.
Preamble Sync Length Destination address
Table 2. Stack
Source address Control Seq. no.
No ACK Payload CRC
UM1904 - Rev 4 page 9/29
UM1904
Transmit and receive (command and response) packet structure
Note:
3.4
Preamble
Preamble Sync Length
Sync
Table 3. wM-Bus
Payload
Table 4. Basic
Destination address
Postamble
Control Payload CRC
See SPIRIT1 datasheet for further details on the embedded packet handler.
Since P2P communication requires the receiving node destination address, the P2P demo is based on stack and basic packet handlers.
The wM-Bus packet format is not used in this sample demonstration.
Table 5. Packet handler feature comparison
Features
Destination address filtering
Broadcast and multicast addressing
Source address filtering
Custom filtering
CRC filtering
LLP: automatic acknowledgment
LLP: automatic acknowledgment with piggybacking
LLP: automatic retransmission
1. Link layer protocol
Stack
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Transmit and receive (command and response) packet structure wM-Bus
No
No
No
No
No
No
No
No
•
•
Command packet features:
• command with data sent at the same time
• SPIRIT1 can handle 65535 bytes of data customizable command structure customizable data packet maximum size
Figure 8. Command data packet structure
Basic
Yes
Yes
No
Yes
Yes
No
No
No
UM1904 - Rev 4
Response packet features: page 10/29
UM1904
User configuration
•
• data buffer is replied from the node tag contains the number associated with the command so the receiver can associate the response with the specific command
Figure 9. Response packet structure
3.4.1
3.5
•
•
•
•
•
•
Packet field description
Cmd Length : the basic command is 1 byte long, but you can set multiple command bytes
Cmd Tag : a unique tag number is linked to each command issued from the node and the response must replicate the same number
Cmd Type : flag to identify application level or network command
Commands : the actual command set sent from the source to destination (it may include parameters)
Data Length : the data packet length
Data buffer : the actual data associated with the command
User configuration
You can modify the configuration file spirit1_appli.h on the basis of the application used.
Figure 10. User configuration
UM1904 - Rev 4 page 11/29
UM1904
User configuration
3.5.1
3.5.2
3.5.3
3.5.4
Selecting the SPIRIT1 expansion board platform
You can select the desired SPIRIT1 expansion board platform by uncommenting the macros:
/* Platform definition: Uncomment the used expansion board*/
#define X_NUCLEO_IDS01A4
// #define X_NUCLEO_IDS01A5
#if defined(X_NUCLEO_IDS01A4)
#define USE_SPIRIT1_868MHz
#elif defined(x_NUCLEO_IDS01AS)
#define USE_SPIRIT1_915MHz
#else
#error SPIRIT1 Nucleo expansion board undefined or unsupported
#endif
Once the SPIRIT1 expansion board platform is selected, the operating frequency is handled by the firmware itself.
For example, if X-NUCLEO-IDS01A4 is selected as the SPIRIT1 expansion board, the operating frequency automatically selected by the firmware is 868 MHz.
Selecting packet handler
The user can select the desired features by uncommenting the relevant macros:
/* Uncomment the Link Layer features to be used */
// #define USE_AUTO_ACK
// #define USE_AUTO_ACK_PIGGYBACKING
// #define USE_AUTO_RETRANSMISSION
#if defined(USE_AUTO_ACK)&& defined(USE_AUTO_ACK_PIGGYBACKING)&& defined(USE_AUTO_RETRANSMISSION)
#define USE_STack_PROTOCOL
/* LLP configuration parameters */
#define EN_AUTOACK S_ENABLE
#define EN_PIGGYBACKING S_ENABLE
#define MAX_RETRANSMISSIONS PKT_N_RETX_2
#else
#define USE_BASIC_PROTOCOL
#endif
By default, the SPIRIT1 works with the basic packet handler.
SPIRIT1 uses the STack packet handler only if the link layer features (such as auto-ack, piggybacking and autoretransmission) are defined.
Setting low-power mode
The P2P application supports low-power mode, enabled by default. It allows the MCU to either enter stop or sleep mode.
/* Uncomment the system Low Power Operating mode */
#define USE_LOW_POWER_MODE
#if defined (USE_LOW_POWER_MODE)
#define LPM_ENABLE
//#define MCU_STOP _MODE
#define MCU_SLEEP MODE
//#define RF _STANDBY
#endif
SPIRIT1 can be set to standby and after to lower-power consumption mode.
Setting radio configuration parameters
You can set the radio parameters in the configuration file, even though it is not recommended to change them.
UM1904 - Rev 4 page 12/29
UM1904
User configuration
3.5.5
3.5.6
/* Radio configuration parameters */
#define XTAL_OFFSET_PPM 0
#define INFINITE_TIMEOUT 0.0
#ifdef USE_RADIO_433MHz
#define BASE_FREOUENCY 433.0e6
#endif
#ifdef USE_RADIO_868MHz
#define BASE_FREQUENCY 868.0e6
#endif
#ifdef USE_RADIO_915MHz
#define BASE_FREOUENCY 915.0e6
#endif
#define CHANNEL_SPACE 20e3
#sefine CHANNEL_NUMBER 0
#define MODULATION_SELECT FSK
#define DATARATE 38400
#define FREQ_DEVIATION 20e3
#define BANDWIDTH 100E3
#define POWER_DBM 11.6
#define POWER_INDEX 7
#define RECEIVE_TIMEOUT 2000.0/*change the value for required timeout period*/
/* Radio configuration parameters */
Setting packet configuration parameters
You can set the packet configuration, even though it is not recommended to change default settings.
*/ Packet configuration parameters */
#define PREAMBLE_LENGTH PKT_PREAMBLE_LENGTH_04BYTES
#define SYNC_LENGTH PKT_SYNC_LENGTH_4BYTES
#define SYNC_WORD 0x1A2635A8
#define LENGTH_TYPE PKT_LENGTH_VAR
#define LENGTH_WIDTH 7
#define CRC_MODE PKT_CRC_MODE_8BITS
#define CONTROL_LENGTH PKT_ CONTROL_LENGTH_0BYTES
#define EN_ADDRESS S_DISABLE
#define EN_FEC S_DISABLE
Setting address of the nodes
Node ddresses can be set in following section of the system setup guide.
*/ Addresses configuration parameters */
#define EN_FILT_MY_ADDRESS S_DISABLE
#define MY_ADDRESS 0x34
#define EN_FILT_MULTICAST_ADDRESS S_DISABLE
#define MULTICAST_ADDRESS 0xEE
#define EN_FILT_BROADCAST_ADDRESS S_DISABLE
#define BROADCAST_ADDRESS 0xFF
#define DESTINATION_ADDRESS 0x44
#define EN_FIL T _SOURCE_ADDRESS S_DISABLE
#define SOURCE ADDR MASK 0xf0
UM1904 - Rev 4 page 13/29
3.5.7
User defined commands and macros
/* User Command */
#define APPLI_CMD 0x11
#define NWK_CMD 0x22
#define LED_TOGGLE 0xff
#define ACK_OK 0x01
#define MAX_BUFFER_LEN 96
#define TIME_TO_EXIT_RX 3000
#define DELAY_RX_LED_TOGGLE 200
#define DELAY_TX_LED_GLOW 1000
#define LPM WAKEUP TIME 100
UM1904
User configuration
UM1904 - Rev 4 page 14/29
UM1904
Hardware configuration
3.6
3.6.1
Hardware configuration
STM32 Nucleo
STM32 Nucleo development boards provide an affordable and flexible way for users to test solutions and build prototypes with any STM32 microcontroller line.
The Arduino™ connectivity support and ST morpho connectors make it easy to expand the functionality of the
STM32 Nucleo open development platform with a wide range of specialized expansion boards to choose from.
The STM32 Nucleo board does not require separate probes as it integrates the ST-LINK/V2-1 debugger/ programmer.
The STM32 Nucleo board comes with the comprehensive STM32 software HAL library together with various packaged software examples.
Figure 11. STM32 Nucleo board
3.6.2
Information regarding the STM32 Nucleo board is available at www.st.com/stm32nucleo
X-NUCLEO-IDS01Ax expansion board
The X-NUCLEO-IDS01A4 and X-NUCLEO-IDS01A5 evaluation boards allow you to evaluate the features and capabilities of the SPIRIT1 low data rate, low power sub-1 GHz transceiver device.
These expansion boards include on-board SPI EEPROM to store parameters and user interface signal LED.
The X-NUCLEO-IDS01A4 board operates the SPIRIT1 transceiver at 868MHz, while the X-NUCLEO-IDS01A5 board operates the SPIRIT1 transceiver at 915MHz.
UM1904 - Rev 4 page 15/29
Figure 12. X-NUCLEO-IDS01Ax expansion board
UM1904
Hardware configuration
3.6.3
Information regarding the X-NUCLEO-IDS01A4 and X-NUCLEO-IDS01A5 expansion boards is available on www.st.com at www.st.com/x-nucleo .
X-NUCLEO-S2868A2 and X-NUCLEO-S2915A1 expansion boards
The X-NUCLEO-S2868A2 expansion board is based on the S2-LP radio and operates in the 868 MHz ISM frequency band.
The X-NUCLEO-S2915A1 expansion board is based on the S2-LP radio and operates in the 915 MHz ISM frequency band.
The expansion boards are compatible with ST morpho and Arduino UNO R3 connectors, and interface with the
STM32 Nucleo microcontroller via SPI connections and GPIO pins.
You can change some of the GPIOs by mounting or removing the resistors.
Figure 13. X-NUCLEO-S2868A2 expansion board
UM1904 - Rev 4 page 16/29
Figure 14. X-NUCLEO-S2915A1 expansion board
UM1904
Software description
3.7
3.8
3.9
Software description
To use STM32 Nucleo development boards with the X-NUCLEO-IDS01Ax or X-NUCLEO-S2868A2 / X-NUCLEO-
S2915A1 expansion boards, the following software specification are required:
• X-CUBE-SUBG1 expansion for STM32Cube . The X-CUBE-SUBG1 firmware and related documentation is available on st.com.
• Development tool-chain and Compiler supported by the STM32Cube expansion software:
– IAR Embedded Workbench for ARM ® toolchain + ST-LINK
– RealView Microcontroller Development Kit ( MDK-ARM-STR ) toolchain + ST-LINK
– System Workbench for STM32 ( SW4STM32 ) + ST-LINK
Hardware setup
The following hardware components are required:
• an STM32 Nucleo development board (order code: NUCLEO- F401RE or NUCLEO-L053R8 )
•
• a SPIRIT1 or an S2-LP expansion board (order code: X-NUCLEO-IDS01A4 , X- NUCLEO-IDS01A5 , X-
NUCLEO-S2868A2 or X-NUCLEO-S2915A1 ) a USB type A to Mini-B USB cable to connect the STM32 Nucleo to the PC
Board setup
Step 1.
Check that the jumper on J1 connector is connected to provide the required voltage to the board devices.
UM1904 - Rev 4 page 17/29
UM1904
Board setup
Step 2.
Connect the X-NUCLEO-IDS01Ax or X-NUCLEO-S2868A2 / X-NUCLEO-S2915A1 to the STM32
Nucleo board
Figure 15. X-NUCLEO-IDS1Ax expansion board plugged to STM32 Nucleo board
UM1904 - Rev 4 page 18/29
UM1904
6LoWPAN application
Figure 16. X-NUCLEO-S2868A2 expansion board plugged to STM32 Nucleo board
3.10
3.10.1
Step 3.
Power the STM32 Nucleo board using the Mini-B USB cable
Step 4.
Program the firmware in the STM32 on the Nucleo development board using the firmware sample provided
Step 5.
Press the reset button on the STM32 Nucleo board
The demonstration kit is ready-to-use
6LoWPAN application
•
•
•
Contiki6LP software description
Contiki6LP is a middleware library ready to be integrated in projects based on STM32Cube and X-CUBE-SUBG1 expansion software.
The software includes samples for sending messages via UDP over 6LoWPAN, using the SPIRIT1 or S2-LP sub-1GHz radio transceiver.
•
•
The key features are:
• Middleware library with Contiki OS and Contiki 6LoWPAN protocol stack 3.x
•
Support for mesh networking technology via the standard RPL protocol
Built-in support for STM32 L1 and F4 platforms
Sample applications (such as UPD sender and receiver, serial siffer and border router)
Samples available for NUCLEO-F401RE and NUCLEO-L152RE
Easy portability across different MCU families, thanks to STM32Cube
Free and user-friendly license terms
UM1904 - Rev 4 page 19/29
UM1904
6LoWPAN application
3.10.2
UDP sender and receiver sample application overview
This sample application works as follows:
1.
the UDP sender node transmits the packets continuously over the air and wait for any receiver node to receive the data packets
2.
the receiver node is indefinitely listening for UDP packets, until it receives the data packets from the sender node
3.
the receiver node sends acknowledgement and outputs the message packet received in the terminal window
4.
the sender node prints the data successfully sent to the receiver node address
Figure 17. 6LoWPAN UDP sender and receiver node communication with a PC
3.10.3
Run the application firmware
Step 1.
Download and unpack X-CUBE-SUBG1 package.
Figure 18. X-CUBE-SUBG1 package folders
UM1904 - Rev 4
Step 2.
Select the UDP receiver application and build the project using a supported IDE.
Alternatively you can use a pre-built binary provided to run this application with the selected STM32
Nucleo board.
page 20/29
Step 3.
Select the radio configuration to be used.
Figure 19. Radio configuration selection
UM1904
6LoWPAN application
UM1904 - Rev 4
Step 4.
Compile the firmware for UDP receiver node.
Step 5.
Repeat the same steps for the UDP sender application node.
page 21/29
UM1904 - Rev 4
UM1904
6LoWPAN application
Step 6.
Launch the terminal application and set the UART port to 115200 bps, 8 bit, No Parity, 1 stop bit.
The terminal shows the window below
Figure 20. UDP sender window
After setting the right parameters, the terminal output becomes
Figure 21. UDP sender terminal output
The received UDP messages are shown as
Figure 22. UDP receiver window page 22/29
4 Reference
Freely available on www.st.com:
1.
SPIRIT1 device datasheet
2.
SPSGRF module datasheet
3.
STM32 Nucleo board datasheet
4.
UM1872: Getting started with the Sub-1 GHz expansion board based on the SPSGRF- 868 and
SPSGRF-915 modules for STM32 Nucleo
5.
S2-LP datasheet
UM1904
Reference
UM1904 - Rev 4 page 23/29
UM1904
Revision history
Table 6. Document revision history
Date
10-Jun-2015
09-Jun-2017
14-May-2018
09-Dec-2019
Revision Changes
1 Initial release.
2
3
4
Updated text in Introduction, Section 2.1: Overview, and Section 2.3: Folders structure.
Replaced Architecture and Application state diagram.
Minor text updates throughout the document.
Text and formatting changes throughout document.
Added references to X-NUCLEO-S2868A1 and S2-LP.
Added Section 3.5 Selecting radio board configuration and Section 4.10 6LoWPAN application.
Updated
Section 2.1 Overview , Section 2.2 Architecture .
Removed Section 2. What is STM32Cube? and replaced it by a link on the cover page.
Added X-NUCLEO-S2868A2 and X-NUCLEO-S2915A1 compatibility information.
UM1904 - Rev 4 page 24/29
UM1904
Contents
Contents
X-NUCLEO-S2868A2 and X-NUCLEO-S2915A1 expansion boards . . . . . . . . . . . . . . . . . 16
UM1904 - Rev 4 page 25/29
UM1904
Contents
UM1904 - Rev 4 page 26/29
UM1904
List of figures
List of figures
UM1904 - Rev 4 page 27/29
UM1904
List of tables
List of tables
UM1904 - Rev 4 page 28/29
UM1904
IMPORTANT NOTICE – PLEASE READ CAREFULLY
STMicroelectronics NV and its subsidiaries (“ST”) reserve the right to make changes, corrections, enhancements, modifications, and improvements to ST products and/or to this document at any time without notice. Purchasers should obtain the latest relevant information on ST products before placing orders. ST products are sold pursuant to ST’s terms and conditions of sale in place at the time of order acknowledgement.
Purchasers are solely responsible for the choice, selection, and use of ST products and ST assumes no liability for application assistance or the design of
Purchasers’ products.
No license, express or implied, to any intellectual property right is granted by ST herein.
Resale of ST products with provisions different from the information set forth herein shall void any warranty granted by ST for such product.
ST and the ST logo are trademarks of ST. For additional information about ST trademarks, please refer to www.st.com/trademarks . All other product or service names are the property of their respective owners.
Information in this document supersedes and replaces information previously supplied in any prior versions of this document.
© 2019 STMicroelectronics – All rights reserved
UM1904 - Rev 4 page 29/29
Scarica
Link pubblico aggiornato
Il link pubblico alla tua chat è stato aggiornato. Puoi visualizzare e gestire i tuoi link di chat dopo la registrazione qui.
Link pubblico del documento
Pubblicità