Mallow imx8mp-verdin-wifi-mallow.dts X11 Debug UART not active?

Technical Support
, , ,
1

Running:
sudo cat /sys/kernel/debug/pinctrl/30330000.pinctrl/pinmux-pins | grep -i uart3

Gives me:
pin 140 (MX8MP_IOMUXC_UART3_RXD): 30880000.serial (GPIO UNCLAIMED) function pinctrl group uart3grp
pin 141 (MX8MP_IOMUXC_UART3_TXD): 30880000.serial (GPIO UNCLAIMED) function pinctrl group uart3grp

And running:
sudo cat /sys/kernel/debug/pinctrl/pinctrl-handles | grep -i uart3

Gives me:
type: MUX_GROUP controller 30330000.pinctrl group: uart3grp (47) function: pinctrl (0) type: CONFIGS_PIN controller 30330000.pinctrl pin MX8MP_IOMUXC_UART3_RXD (140)config 000001c4 type: CONFIGS_PIN controller 30330000.pinctrl pin MX8MP_IOMUXC_UART3_TXD (141)config 000001c4

I built Torizon from:

torizon-docker-verdin-imx8mp-Tezi_7.5.0+build.30.tar
linux/arch/arm64/boot/dts/freescale/imx8mp-verdin-wifi-mallow.dts

2

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.

I’d be glad to help you understand your UART3 pin configuration! However, to provide you with the most accurate guidance for your specific setup, could you let me know which version of Torizon OS you are running? You can get this information by running the tdx-info command on your device. (1)

I can see you’re working with a Verdin iMX8M Plus on a Mallow Carrier Board with Torizon OS, but the specific version will help me provide more targeted assistance for your pin multiplexing configuration.

Common platforms to consider:

  • Hardware: Verdin i.MX8M Plus, Verdin AM62, Aquila AM69, Apalis i.MX8QP, Colibri i.MX8X, Ivy Carrier Board, Ixora Carrier Board, Mallow Carrier Board, IMX95
  • Operational System: Yocto 7.2.0, Torizon 6.8.2, Torizon OS 6, BSP 7, BSP 6, Torizon OS 7.2.0-build.13

For more information about the tdx-info command, please refer to: Getting Device Information with Tdx-Info | Toradex Developer Center

Best regards, Toradex AI Assistant.

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

3

Distro version: VERSION_ID=7.5.0-build.30
Kernel version: 6.6.119-7.5.0-ge5c5595adb06 #1-Torizon SMP PREEMPT Mon Jan 5 09:23:13 UTC 2026

4

UART3 Pin Configuration Analysis

Based on your output, I can see that UART3 pins are properly configured on your Verdin iMX8M Plus running Torizon OS 7.5.0-build.30. Let me explain what your debug information shows: (1)

Pin Status Breakdown

Your pinmux-pins output shows:

  • Pin 140 (UART3_RXD): Assigned to 30880000.serial (UART3 peripheral) with function pinctrl in group uart3grp
  • Pin 141 (UART3_TXD): Assigned to 30880000.serial (UART3 peripheral) with function pinctrl in group uart3grp

The “(GPIO UNCLAIMED)” notation means these pins are not being used as GPIOs - they are dedicated to the UART3 peripheral, which is correct. (1)

Pin Control Configuration

Your pinctrl-handles output confirms:

  • Both pins are in the uart3grp pin control group (group 47)
  • Configuration value 000001c4 is applied to both pins
  • The pins are properly muxed for UART functionality

Device Tree Context

Since you’re using the Mallow carrier board with the imx8mp-verdin-wifi-mallow.dts device tree, UART3 should be available according to the carrier board’s pin mapping. The pin multiplexing configuration appears to be working correctly. (1)

Next Steps

If you need to modify the UART3 configuration or create a device tree overlay for additional functionality, you can refer to the pin multiplexing documentation for creating custom .dts files. (1) The process involves:

  1. Creating a device tree overlay with the appropriate pin control groups
  2. Using TorizonCore Builder to apply the overlay
  3. Checking for pin conflicts with other peripherals

Your current configuration shows UART3 is properly initialized and ready for use.

**

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.