1. Article purpose[edit | edit source]
The purpose of this article is to:
- briefly introduce the USART peripheral and its main features
- indicate the level of security supported by this hardware block
- explain how each instance can be allocated to the runtime contexts and linked to the corresponding software components
- explain, when needed, how to configure the USART peripheral.
2. Peripheral overview[edit | edit source]
The USART peripheral is used to interconnect STM32 MPU devices with other systems, typically via RS232 or RS485 protocols. In addition, the USART can be used for smartcard interfacing or SPI master/slave operation and supports the Synchronous mode.
The UART peripheral is similar to the USART, but does not support the Synchronous mode nor the smartcard interfacing.
High-speed data communications can be achieved by using the DMA internal peripheral for multibuffer configuration.
2.1. Features[edit | edit source]
Refer to STM32MP13 reference manuals or STM32MP15 reference manuals for the complete list of features, and to the software components, introduced below, to see which features are implemented.
2.2. Security support[edit | edit source]
2.2.1. On STM32MP13x lines 
[edit | edit source]
USART1 and USART2 are a secure instances (under ETZPC control).
The other UARTs and USARTs are non-secure instances.
2.2.2. On STM32MP15x lines 
[edit | edit source]
USART1 is a secure instance (under ETZPC control).
The other UARTs and USARTs are non-secure instances.
3. Peripheral usage and associated software[edit | edit source]
3.1. Boot time[edit | edit source]
All USART and UART instances that are not securable via ETZPC (see #Security support) are boot devices that support serial boot for Flash programming with STM32CubeProgrammer.
3.2. Runtime[edit | edit source]
3.2.1. Overview[edit | edit source]
The STM32 MPU devices feature four USART instances (supporting both Asynchronous and Synchronous modes), and four UART instances (supporting only Asynchronous mode).
Secure USART can be allocated to:
- the Arm® Cortex®-A7 secure core to be used under OP-TEE with the USART OP-TEE driver, typically to communicate with a smartcard.
All USART and UART instances can be allocated to:
- the Arm® Cortex®-A7 non-secure core to be used under Linux® with the tty framework. However, the Linux® kernel supports only the UART Asynchronous mode (Synchronous mode not supported).
or, on STM32MP15x lines only,
- the Arm® Cortex®-M4 to be used with STM32Cube MPU Package with USART HAL driver. Both USART Synchronous and Asynchronous modes are supported by the STM32Cube MPU Package.
Chapter Peripheral assignment describes which peripheral instance can be assigned to which context.
3.2.2. Software frameworks[edit | edit source]
3.2.2.1. On STM32MP13x lines [edit | edit source]
| Domain | Peripheral | Software components | Comment | |
|---|---|---|---|---|
| OP-TEE | Linux | |||
| Low speed interface | USART | USART OP-TEE driver | Linux serial/tty framework | |
3.2.2.2. On STM32MP15x lines [edit | edit source]
| Domain | Peripheral | Software components | Comment | ||
|---|---|---|---|---|---|
| OP-TEE | Linux | STM32Cube | |||
| Low speed interface | USART | USART OP-TEE driver | Linux serial/tty framework | STM32Cube USART driver | |
3.2.3. Peripheral configuration[edit | edit source]
The configuration is applied by the firmware running in the context to which the peripheral is assigned. The configuration can be done alone via the STM32CubeMX tool for all internal peripherals, and then manually completed (particularly for external peripherals) according to the information given in the corresponding software framework article or, for Linux in the Serial TTY device tree configuration article.
3.2.4. Peripheral assignment[edit | edit source]
3.2.4.1. On STM32MP13x lines [edit | edit source]
Click on the right to expand the legend...
Check boxes illustrate the possible peripheral allocations supported by STM32 MPU Embedded Software:
- ☐ means that the peripheral can be assigned (☑) to the given runtime context.
- ⬚ means that the peripheral can be assigned to the given runtime context, but this configuration is not supported in STM32 MPU Embedded Software distribution.
- ✓ is used for system peripherals that cannot be unchecked because they are statically connected in the device.
Refer to How to assign an internal peripheral to a runtime context for more information on how to assign peripherals manually or via STM32CubeMX.
The present chapter describes STMicroelectronics recommendations or choice of implementation. Additional possiblities might be described in STM32MP13 reference manuals.
| Domain | Peripheral | Runtime allocation | Comment | ||
|---|---|---|---|---|---|
| Instance | Cortex-A7 secure (OP-TEE) |
Cortex-A7 non-secure (Linux) | |||
| Low speed interface | USART | USART1 | ☐ | ☐ | Assignment (single choice) |
| USART2 | ☐ | ☐ | Assignment (single choice) | ||
| USART3 | ☐ | ||||
| UART4 | ☐ | ||||
| UART5 | ☐ | ||||
| USART6 | ☐ | ||||
| UART7 | ☐ | ||||
| UART8 | ☐ | ||||
3.2.4.2. On STM32MP15x lines [edit | edit source]
Click on the right to expand the legend...
Check boxes illustrate the possible peripheral allocations supported by STM32 MPU Embedded Software:
- ☐ means that the peripheral can be assigned (☑) to the given runtime context.
- ⬚ means that the peripheral can be assigned to the given runtime context, but this configuration is not supported in STM32 MPU Embedded Software distribution.
- ✓ is used for system peripherals that cannot be unchecked because they are statically connected in the device.
Refer to How to assign an internal peripheral to a runtime context for more information on how to assign peripherals manually or via STM32CubeMX.
The present chapter describes STMicroelectronics recommendations or choice of implementation. Additional possiblities might be described in STM32MP15 reference manuals.
| Domain | Peripheral | Runtime allocation | Comment | |||
|---|---|---|---|---|---|---|
| Instance | Cortex-A7 secure (OP-TEE) |
Cortex-A7 non-secure (Linux) |
Cortex-M4 (STM32Cube) | |||
| Low speed interface | USART | USART1 | ☐ | ☐ | Assignment (single choice) | |
| USART2 | ☐ | ☐ | Assignment (single choice) | |||
| USART3 | ☐ | ☐ | Assignment (single choice) | |||
| UART4 | ☐ | ☐ | Assignment (single choice). Used for Linux® serial console on ST boards. | |||
| UART5 | ☐ | ☐ | Assignment (single choice) | |||
| USART6 | ☐ | ☐ | Assignment (single choice) | |||
| UART7 | ☐ | ☐ | Assignment (single choice) | |||
| UART8 | ☐ | ☐ | Assignment (single choice) | |||
4. How to go further[edit | edit source]
Additional documentation on USART peripheral is available on st.com:
- STM32 USART training [1] presents the STM32 Universal Synchronous/Asynchronous Receiver/Transmitter interface.
- STM32 USART automatic baud rate detection [2] presents STM32 USART automatic baud rate detection.
5. References[edit | edit source]
- ↑ Please refer to STM32MP1-Peripheral-USART document on st.com
- ↑ STM32 USART automatic baud rate detection application note (AN4908)
Arm® is a registered trademark of Arm Limited (or its subsidiaries) in the US and/or elsewhere. 
Arm® is a registered trademark of Arm Limited (or its subsidiaries) in the US and/or elsewhere.