JP5.1.3 vs JP 6.1 UART serial device mapping

Hi,
I’m having trouble to enable the second uart in our system (custom carrier board)

With JP5.1.3 everything worked fine. With JP6.1 the second UART is not working.
I asked about this in the following thread:

but I think I found a problem and wish to verify that’s the cause:

In JP5.1.3 the /dev/ttyTHS0 is actually @3100000 and it worked.
In JP6.1 the /dev/ttyTHS1 is actually @3100000 and it works.

in JP5.1.3 the /dev/ttyTHS1 is actually @3110000 and it worked
in JP6.1 the /dev/ttyTHS2 is actually @3140000 and its not working.
(in JP6.1 we have /dev/ttyTHS1 and /dev/ttyTHS2 instead /dev/ttyTHS0 and /dev/ttyTHS1 like in JP5.1.3)
So is there a problem with the mapping?

source:

Thanks

Hi bsp_dev,

Some redundant serial nodes have been removed from JP6.
Please just refer to the address rather than the numbering of the node like /dev/ttyTHS*.

Are you trying to use serial@3110000 in JP6 which is from M.2 Key E?
Please share the full dmesg and device tree for further check.

So I need to use whatever device that is mapped to the @3110000 node?

I “need” to use that since this worked in JP5.1.3. and we ue the same hardware.

dt:
dt.txt (330.6 KB)

dmesg:
dmesg.txt (59.3 KB)

In our case 3110000 is /dev/ttyS0 but according to dmsg its not a “TEGRA_UART”.
If I use it I receive 0xff in the other side.

		serial@3110000 {
			resets = <0x03 0x65>;
			interrupts = <0x00 0x71 0x04>;
			clocks = <0x03 0x9c>;
-			compatible = "nvidia,tegra234-uart\0nvidia,tegra20-uart";
+			compatible = "nvidia,tegra194-hsuart";
			status = "okay";
			reg = <0x00 0x3110000 0x00 0x10000>;
		};
..
	aliases {
		i2c3 = "/bus@0/i2c@3190000";
		nvdla1 = "/bus@0/host1x@13e00000/nvdla1@158c0000";
		i2c1 = "/bus@0/i2c@c240000";
		i2c8 = "/bus@0/i2c@31e0000";
		i2c6 = "/bus@0/i2c@31c0000";
		serial1 = "/bus@0/serial@3100000";
+		serial3 = "/bus@0/serial@3110000";
		tegra-camera-rtcpu = "/rtcpu@bc00000";

Please configure the lines as above in device tree, and you should get /dev/ttyTHS3 available for serial@3110000 after reboot.

That worked. Thanks!

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.