1. Article Purpose[edit | edit source]
This article explains how to configure the USART when it is assigned to the Linux® OS. In that case, it is controlled by the Serial and TTY frameworks.
The configuration is performed using the device tree mechanism that provides a hardware description of the USART peripheral, used by the stm32-usart Linux driver.
If the peripheral is assigned to another execution context, refer to How to assign an internal peripheral to an execution context article for guidelines on peripheral assignment and configuration.
2. DT bindings documentation[edit | edit source]
The USART is a multifunction device.
Each function is represented by a separate binding document:
- Generic UART bindings[1] used by UART framework.
- STM32 USART driver bindings[2] used by stm32-usart driver. This bindings documentation explains how to write device tree files for STM32 USARTs.
3. DT configuration[edit | edit source]
This hardware description is a combination of the STM32 microprocessor device tree files (.dtsi extension) and board device tree files (.dts extension). See the Device tree for an explanation of the device tree file split.
STM32CubeMX can be used to generate the board device tree. Refer to How to configure the DT using STM32CubeMX for more details.
3.1. DT configuration (STM32 level)[edit | edit source]
The STM32MP1 USART node is located
- for STM32MP13x lines
in stm32mp131.dtsi [3] - for STM32MP15x lines in stm32mp151.dtsi [4]
- for STM32MP21x lines in stm32mp211.dtsi [5]
- for STM32MP23x lines in stm32mp231.dtsi [6]
- for STM32MP25x lines in stm32mp251.dtsi [7]
uart4: serial@40010000 {
compatible = "st,stm32h7-uart";
reg = <0x40010000 0x400>;
interrupts-extended = <&exti 30 IRQ_TYPE_LEVEL_HIGH>;
clocks = <&rcc UART4_K>;
wakeup-source;
power-domains = <&pd_core>;
dmas = <&dmamux1 63 0x400 0x15>,
<&dmamux1 64 0x400 0x11>;
dma-names = "rx", "tx";
access-controllers = <&etzpc 32>;
status = "disabled";
};
It describes the hardware register address, clocks, interrupts and DMA resources.
The required and optional properties are fully described in the bindings files.
3.2. DT configuration (Board level)[edit | edit source]
Part of the device tree is used to describe the USART hardware used on a given board:
- Which USART instances are enabled (by setting status to "okay")
- Which features are used (such as DMA transfer or direct transfer, transfer speed or parity)
- Which pins are configured via pinctrl.
- Which serial aliases are linked to UART instances. Please check the alias already used in other device tree files to avoid alias conflicts. The alias defines the index of the ttySTMx instance linked the UART.
Note:
- As the pin configuration can be different for each board, several DT configurations can be defined for each UART instance.
- The pin configuration is described in board datasheet. Each new pin configuration described in boards datasheet needs to be defined in device tree.
Three device tree configurations can be defined for each pin muxing configuration:
- "default": for standard usage (mandatory)
- "sleep": for Sleep mode, when the UART instance is not a wake up source (mandatory)
- "idle": for Sleep mode, when the UART instance is a wake up source (optional)
3.3. DT configuration examples[edit | edit source]
3.3.1. Activation of a USART or UART instance[edit | edit source]
 Information
|
| Some UART pins are available on GPIO expansion and Arduino connectors (depending on the connectors available on the board).[8] |
To communicate with a UART instance, an RS232 card must be plugged on the UART pins.
The example below shows how to configure and enable a UART instance at board level, based on STM32MP157C-EV1 board USART3 example.
Note: For STM32 boards, the configuration is already defined in the device tree. Only the device activation is needed.
To activate a UART instance, please follow steps below:
- Define the instance pin configuration (ex: stm32mp15-pinctrl.dtsi [9]).
usart3_pins_c: usart3-2 {
pins1 {
pinmux = <STM32_PINMUX('B', 10, AF7)>, /* USART3_TX */
<STM32_PINMUX('G', 8, AF8)>; /* USART3_RTS */
bias-disable;
drive-push-pull;
slew-rate = <0>;
};
pins2 {
pinmux = <STM32_PINMUX('B', 12, AF8)>, /* USART3_RX */
<STM32_PINMUX('B', 13, AF7)>; /* USART3_CTS_NSS */
bias-pull-up;
};
};
usart3_idle_pins_c: usart3-idle-2 {
pins1 {
pinmux = <STM32_PINMUX('B', 10, ANALOG)>, /* USART3_TX */
<STM32_PINMUX('B', 13, ANALOG)>; /* USART3_CTS_NSS */
};
pins2 {
pinmux = <STM32_PINMUX('G', 8, AF8)>; /* USART3_RTS */
bias-disable;
drive-push-pull;
slew-rate = <0>;
};
pins3 {
pinmux = <STM32_PINMUX('B', 12, AF8)>; /* USART3_RX */
bias-pull-up;
};
};
usart3_sleep_pins_c: usart3-sleep-2 {
pins {
pinmux = <STM32_PINMUX('B', 10, ANALOG)>, /* USART3_TX */
<STM32_PINMUX('G', 8, ANALOG)>, /* USART3_RTS */
<STM32_PINMUX('B', 13, ANALOG)>, /* USART3_CTS_NSS */
<STM32_PINMUX('B', 12, ANALOG)>; /* USART3_RX */
};
};
| Information
|
| In the UART specification, pull-up must be added on the TX and RX side. On console UART this avoid fuzzy characters when UART is unconnected.
This is usually done with an external pull-up, but instead it is also possible to use the internal pull-up by adding in the DTS on the RX and TX pins: bias-pull-up; (An example with the pin UART7_RX is visible in "stm32mp15-pinctrl.dtsi" [9]) |
- Define the serial alias for this instance at board level (ex: stm32mp157c-ev1.dts [10]).
/* Serial1 alias (ie ttySTM1) assigned to usart3 */
aliases {
serial1 = &usart3;
};
- Configure and activate the instance at board level (ex: stm32mp157c-ev1.dts [10]).
&usart3 {
pinctrl-names = "default", "sleep", "idle"; /* pin configurations definition */
pinctrl-0 = <&usart3_pins_a>; /* default pin configuration selection */
pinctrl-1 = <&usart3_sleep_pins_a>; /* sleep pin configuration selection */
pinctrl-2 = <&usart3_idle_pins_a>; /* idle pin configuration selection */
status = "okay"; /* device activation */
};
Note: The pin configuration selected has to be aligned with the pin configuration described in the board datasheet.
- Default behavior of stm32-usart driver is to use DMA. You can switch to interrupt mode by removing DMA properties:
&usart3 {
pinctrl-names = "default", "sleep", "idle";
pinctrl-0 = <&usart3_pins_a>;
pinctrl-1 = <&usart3_sleep_pins_a>;
pinctrl-2 = <&usart3_idle_pins_a>;
/delete-property/dmas;
/delete-property/dma-names;
status = "okay";
};
4. How to configure the DT using STM32CubeMX[edit | edit source]
The STM32CubeMX tool can be used to configure the STM32MPU device and get the corresponding platform configuration device tree files.
The STM32CubeMX may not support all the properties described in the above DT bindings documentation paragraph. If so, the tool inserts user sections in the generated device tree. These sections can then be edited to add some properties and they are preserved from one generation to another. Refer to STM32CubeMX user manual for further information.
5. References[edit | edit source]
- ↑ Documentation/devicetree/bindings/serial/serial.yaml , UART generic device tree bindings
- ↑ Documentation/devicetree/bindings/serial/st,stm32-uart.yaml , STM32 USART device tree bindings
- ↑ stm32mp131.dtsi
- ↑ stm32mp151.dtsi
- ↑ stm32mp211.dtsi
- ↑ stm32mp231.dtsi
- ↑ stm32mp251.dtsi
- ↑ STM32MP157x-DKx | STM32MP157x-EV1 | STM32MP135x-DK | STM32MP257x-EV1 | STM32MP257x-DKx
- ↑ 9.0 9.1 arch/arm/boot/dts/st/stm32mp15-pinctrl.dtsi , STM32MP15 pinctrl device tree file
- ↑ 10.0 10.1 arch/arm/boot/dts/st/stm32mp157c-ev1.dts , STM32MP157c ev1 board device tree file