We have a custom carrier board for Jetson Orin Nano SoM. We require UART0 and UART1 to be used as general purpose UARTs and UART2 as console UART.
We were able to use UART1 using the device node /dev/ttyTHS0.
UART2 is also working as console.
But we weren’t able to connect with UART0.
Output of the command sudo dmesg | grep tty is given below:
[ 0.000000] Kernel command line: root=PARTUUID=d5d74128-4329-443f-8fbd-2964fd0a3967 rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 console=ttyAMA0,115200 firmware_class.path=/etc/firmware fbcon=map:0 net.ifnames=0 nospectre_bhb nv-auto-config
[ 0.242156] 31d0000.serial: ttyAMA0 at MMIO 0x31d0000 (irq = 65, base_baud = 0) is a SBSA
[ 1.388982] printk: console [ttyAMA0] enabled
[ 4.005970] printk: console [ttyTCU0] enabled
[ 6.988540] 3100000.serial: ttyTHS0 at MMIO 0x3100000 (irq = 17, base_baud = 0) is a TEGRA_UART
[ 7.005001] 3130000.serial: ttyTHS3 at MMIO 0x3130000 (irq = 63, base_baud = 0) is a TEGRA_UART
[ 7.021473] 3140000.serial: ttyTHS4 at MMIO 0x3140000 (irq = 64, base_baud = 0) is a TEGRA_UART
[ 12.005810] systemd[1]: Created slice system-serial\x2dgetty.slice.
/dev/ttyTHS1 which maps to UART0 has not been enabled by the kernel device tree.
We assume UART0 has been locked for Bluetooth usage.
But /dev/ttyTHS3 and /dev/ttyTHS4 are available as device nodes. Do they map to UART D and UART E?
If so, what are the pin outs? Any pinmux corrections required?
Our project requires 2 general purpose UARTs in addition to the console UART. UART2 as console and UART1 as general purpose UART is already working. We require one more.
UART0 should be connected from M.2 Key E, have you connect them on the custom board to your UART device already?
Please just enable it from the dtb in use.
Hi,
Thanks for your reply.
Jetpack version is 5.1.2-b104
Yes, we have already connected UART0 from M.2 Key E.
How to enable it in dtb? Could you guide with the steps required? Does this require kernel source compilation?