Thor: How to change the UEFI console to UART3_RXD_DEBUG

Robotics & Edge Computing Jetson & Embedded Systems Jetson Thor
1

On my custom board, I connected a device on UART2, UART3_RXD_DEBUG keep output messy code after UEFI boot.

Then use minicom shows UART2, it display UEFI menu.

Apparently, the device output on UART2 was treated as a UEFI menu operation, completely disrupting the UEFI boot process.

So, how can I change the UEFI console to UART3_RXD_DEBUG? and keep UART2 clean.

3

Hi liu.jialu,

Please share the result of cat /etc/nv_tegra_release on your board.

Do you mean the UART-K? (i.e. serial@810c540000)

4

yes, it’s serial@810c540000, pins like this:

image
image702×121 13 KB

$ cat /etc/nv_tegra_release

R38 (release), REVISION: 2.0, GCID: 41844464, BOARD: generic, EABI: aarch64, DATE: Fri Aug

22 00:55:42 UTC 2025

KERNEL_VARIANT: oot

TARGET_USERSPACE_LIB_DIR=nvidia
TARGET_USERSPACE_LIB_DIR_PATH=usr/lib/aarch64-linux-gnu/nvidia
INSTALL_TYPE=openrm

5

Could you share the full dmesg and device tree for further check?

6

full demsg from minicom:

minicom_for_uart.txt (148.2 KB)

device tree:

kernel_tegra264-p4071-0000+p3834-0008-nv.dts.txt (325.2 KB)

7

Could you try to disable tegra-utc@c4e0000 in device tree source and reflash the board to apply the change?

		tegra-utc@c4e0000 {
			compatible = "nvidia,tegra264-utc";
			reg = <0x00 0xc4e8000 0x00 0x8000 0x00 0xc4e0000 0x00 0x8000>;
			reg-names = "rx\0tx";
			interrupts = <0x00 0x203 0x04>;
			current-speed = <0x1c200>;
			tx-threshold = <0x04>;
			rx-threshold = <0x04>;
-			status = "okay";
+			status = "disabled";
		};