# Jp7.2 thor ttyAMA10 error

**URL:** <https://forums.developer.nvidia.com/t/jp7-2-thor-ttyama10-error/378406>\
**Category:** Jetson Thor\
**Tags:** uart, chinese\
**Created:** [July 28, 2026, 12:43pm UTC](https://forums.developer.nvidia.com/t/jp7-2-thor-ttyama10-error/378406 "2026-07-28T12:43:12Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![helianyi1](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@helianyi1](https://forums.developer.nvidia.com/u/helianyi1)\
**Post date:** [July 28, 2026, 12:43pm UTC](https://forums.developer.nvidia.com/t/jp7-2-thor-ttyama10-error/378406/1 "2026-07-28T12:43:12Z")

</div>

hi nvidia:

我对ttyAMA10做回环测试，发现当我发送超过7个字符时就会报错，比如我发送 字符串 1234567 不会报错，但是当我发送12345678时就会报错， 串口配置如下

```auto
	uart10: serial@810c540000 {
		compatible = "arm,pl011", "arm,primecell";
		reg = <0x81 0x0c540000 0x0 0x10000>;
		interrupts = <GIC_SPI 173 IRQ_TYPE_LEVEL_HIGH>;
		clocks = <&bpmp TEGRA264_CLK_UART10>,
			 <&bpmp TEGRA264_CLK_PLLP_OUT0>;
		clock-names = "uartclk", "apb_pclk";
		assigned-clocks = <&bpmp TEGRA264_CLK_UART10>;
		assigned-clock-parents = <&bpmp TEGRA264_CLK_PLLP_OUT0>;
		dmas = <&gpcdma 12 12 TEGRA_SID_GPCDMA>,
		       <&gpcdma 12 22 TEGRA_SID_GPCDMA>;
		dma-names = "rx", "tx";
		iommus = <&smmu1_mmu TEGRA264_GPCDMA_SID_UART10>;
		dma-coherent;
		arm,primecell-periphid = <0x00051011>;
		resets = <&bpmp TEGRA264_RESET_UART10>;
		reset-names = "serial";
		status = "disabled";
	};

```

错误信息

[48.394330] [TS:58296278136] uart-pl011 810c540000.serial: DMA channel TX dma0chan21  
[48.395110] [TS:58297058099] uart-pl011 810c540000.serial: DMA channel RX dma0chan11  
[69.077850] [TS:78979797355] pps-gpio: ts need to resync ts\_offset:450425712 temp64:213325 resync\_ts\_offset:30 real\_ts\_gap:999786675 real\_ts:1785242144450425712  
[82.793434] [TS:92695381713] arm-smmu-v3 8105000000.iommu: event 0x10 received:  
[82.793436] [TS:92695383648] tegra-mc 8108020000.memory-controller: ptcr: @0x0000000000000000: Read response with poison bit error status:0  
[82.793440] [TS:92695388056] arm-smmu-v3 8105000000.iommu: 0x0000080000000010  
[82.793442] [TS:92695390065] arm-smmu-v3 8105000000.iommu: 0x0000020800000000  
[82.793443] [TS:92695391000] arm-smmu-v3 8105000000.iommu: 0x00000000fffff000  
[82.793444] [TS:92695392083] arm-smmu-v3 8105000000.iommu: 0x0000000000000000  
[82.793444] [TS:92695391889] tegra-mc 8108020000.memory-controller: No interrupt in HUB/HUBC  
[82.793451] [TS:92695398907] tegra-gpcdma 8400000.dma-controller: GPCDMA CH22 mc slave error  
[82.793557] [TS:92695504454] tegra-mc 8108020000.memory-controller: gpcdmar: non-secure read @0x0000fffffffff000: EMEM address decode error (EMEM decode error)  
[99.070810] [TS:108972758025] pps-gpio: ts need to resync ts\_offset:444742688 temp64:172785 resync\_ts\_offset:30 real\_ts\_gap:999827215 real\_ts:1785242174444742688  
[99.071006] [TS:108972953562] pegasus\_cdi\_monitor processing events:2 ts:99070093077 last\_ts:99070093077  
[99.071013] [TS:108972961219] pegasus\_cdi\_monitor kfifo\_out event:20 data:1e ts:69075579681  
[100.045266] [TS:109947214145] pegasus\_cdi\_event event:13 data:0 ts:100042986972 triger done not restart hrtimer

[100.047107] [TS:109949055191] pegasus\_cdi\_event event:13 data:0 ts:0 start hrtimer 100ms later

[100.047114] [TS:109949061543] pegasus\_cdi\_event event:13 data:1 ts:0 set\_camera\_triger\_cmd

[100.047116] [TS:109949064080] pegasus\_cdi\_monitor kfifo\_out event:20 data:1e ts:99068539907  
[100.047118] [TS:109949065941] desert\_mipi\_reset:0 0 0 0  
[101.626151] [TS:111528099200] pps-gpio: real\_ts\_gap:2555380655 real\_ts:1785242177000123343 last\_index0\_real\_ts:1785242174444742688  
[102.625882] [TS:112527829598] pps-gpio: time is resync ts\_offset:-131254 temp64:254597  
[116.529598] [TS:126431545531] arm-smmu-v3 8105000000.iommu: event 0x10 received:  
[116.529603] [TS:126431551031] arm-smmu-v3 8105000000.iommu: 0x0000080000000010  
[116.529605] [TS:126431552475] arm-smmu-v3 8105000000.iommu: 0x0000020800000000  
[116.529605] [TS:126431553253] arm-smmu-v3 8105000000.iommu: 0x00000000fffff000  
[116.529607] [TS:126431554475] arm-smmu-v3 8105000000.iommu: 0x0000000000000000  
[116.529723] [TS:126431670864] tegra-mc 8108020000.memory-controller: gpcdmar: non-secure read @0x0000fffffffff000: EMEM address decode error (EMEM decode error)  
[116.529724] [TS:126431672234] tegra-mc 8108020000.memory-controller: ptcr: @0x0000000000000000: Read response with poison bit error status:0  
[116.529733] [TS:126431680734] tegra-mc 8108020000.memory-controller: No interrupt in HUB/HUBC  
[141.113333] [TS:151015281109] arm-smmu-v3 8105000000.iommu: event 0x10 received:  
[141.113339] [TS:151015286304] arm-smmu-v3 8105000000.iommu: 0x0000080000000010  
[141.113340] [TS:151015287711] arm-smmu-v3 8105000000.iommu: 0x0000020800000000  
[141.113341] [TS:151015289044] arm-smmu-v3 8105000000.iommu: 0x00000000fffff000  
[141.113342] [TS:151015290128] arm-smmu-v3 8105000000.iommu: 0x0000000000000000  
[141.113465] [TS:151015412331] tegra-mc 8108020000.memory-controller: ptcr: @0x0000000000000000: Read response with poison bit error status:0  
[141.113465] [TS:151015413239] tegra-mc 8108020000.memory-controller: gpcdmar: non-secure read @0x0000fffffffff000: EMEM address decode error (EMEM decode error)  
[141.113473] [TS:151015420452] tegra-mc 8108020000.memory-controller: No interrupt in HUB/HUBC  
[170.000834] [TS:179902781576] arm-smmu-v3 8105000000.iommu: event 0x10 received:  
[170.000833] [TS:179902781131] tegra-mc 8108020000.memory-controller: gpcdmar: non-secure read @0x0000fffffffff000: EMEM address decode error (EMEM decode error)  
[170.000838] [TS:179902785354] tegra-mc 8108020000.memory-controller: ptcr: @0x0000000000000000: Read response with poison bit error status:0  
[170.000839] [TS:179902787261] arm-smmu-v3 8105000000.iommu: 0x0000080000000010  
[170.000842] [TS:179902789752] arm-smmu-v3 8105000000.iommu: 0x0000020800000000  
[170.000843] [TS:179902790928] arm-smmu-v3 8105000000.iommu: 0x00000000fffff000  
[170.000844] [TS:179902791909] arm-smmu-v3 8105000000.iommu: 0x0000000000000000  
[170.000846] [TS:179902793955] tegra-mc 8108020000.memory-controller: No interrupt in HUB/HUBC  
[182.009437] [TS:191911384407] tegra-mc 8108020000.memory-controller: gpcdmar: non-secure read @0x0000fffffffff000: EMEM address decode error (EMEM decode error)  
[182.009438] [TS:191911386259] arm-smmu-v3 8105000000.iommu: event 0x10 received:  
[182.009444] [TS:191911391481] arm-smmu-v3 8105000000.iommu: 0x0000080000000010  
[182.009446] [TS:191911393398] arm-smmu-v3 8105000000.iommu: 0x0000020800000000  
[182.009446] [TS:191911394268] arm-smmu-v3 8105000000.iommu: 0x00000000fffff000  
[182.009447] [TS:191911395222] arm-smmu-v3 8105000000.iommu: 0x0000000000000000  
[182.009560] [TS:191911507462] tegra-mc 8108020000.memory-controller: ptcr: @0x0000000000000000: Read response with poison bit error status:0  
[182.009568] [TS:191911515555] tegra-mc 8108020000.memory-controller: No interrupt in HUB/HUBC

---

<div class="post-metadata">

**Author:** ![KevinFFF](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/kevinfff/32/15508_2.png) [@KevinFFF](https://forums.developer.nvidia.com/u/KevinFFF)\
**Post date:** [July 29, 2026, 5:30am UTC](https://forums.developer.nvidia.com/t/jp7-2-thor-ttyama10-error/378406/3 "2026-07-29T05:30:19Z")

</div>

Hi helianyi1,

Could you update the following lines in device tree to check if it could help for your case?  
[/quote]

```auto
- dmas = <&gpcdma 12 12 TEGRA_SID_GPCDMA>,
- <&gpcdma 12 22 TEGRA_SID_GPCDMA>;
+ dmas = <&gpcdma 12 12 TEGRA264_GPCDMA_SID_UART10>,
+ <&gpcdma 12 22 TEGRA264_GPCDMA_SID_UART10>;
		dma-names = "rx", "tx";
		iommus = <&smmu1_mmu TEGRA264_GPCDMA_SID_UART10>;

```

---

<div class="post-metadata">

**Author:** ![helianyi1](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@helianyi1](https://forums.developer.nvidia.com/u/helianyi1)\
**Post date:** [July 29, 2026, 5:41am UTC](https://forums.developer.nvidia.com/t/jp7-2-thor-ttyama10-error/378406/4 "2026-07-29T05:41:32Z")

</div>

ok , the patch fix this issue

---

<div class="post-metadata">

**Author:** ![SamM11](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/samm11/32/389301_2.png) [@SamM11](https://forums.developer.nvidia.com/u/SamM11)\
**Post date:** [July 29, 2026, 8:57am UTC](https://forums.developer.nvidia.com/t/jp7-2-thor-ttyama10-error/378406/5 "2026-07-29T08:57:26Z")

</div>

Hi @KevinFFF ,

I faced the same issue here at JP7.2 , but I use uart5: serial@810c510000(ttyAMA5) and uart9: serial@810c530000(ttyAMA9). and I using the custom board.

In JetPack 7.1, I only needed to change the `status` property of **UART5** and **UART9** to `"okay"` in `tegra264.dtsi`, and both UARTs worked correctly.

However, in JetPack 7.2, applying the same modification only enables **UART5** to function properly, while **UART9** still does not work.

I then applied the patch you provided to **UART9** , but it still does not function correctly.

Below are dmesg about tty:

```auto
sudo dmesg | grep tty
[0.000000] Kernel command line: root=PARTUUID=46ceeaef-cd2f-4fd7-9bfd-48585f7e5b10 rw rootwait rootfstype=ext4 mminit_loglevel=4 earlycon=tegra_utc,mmio32,0xc5a0000 console=ttyUTC0,115200 clk_ignore_unused firmware_class.path=/etc/firmware fbcon=map:0 efi=runtime audit_backlog_limit=8192 video=efifb:off console=tty0 bl_prof_dataptr=6225920@0x2004010000 bl_prof_ro_ptr=65536@0x2004000000
[0.012575] printk: legacy console [tty0] enabled
[0.113166] printk: legacy console [ttyUTC0] enabled
[5.185317] 810c510000.serial: ttyAMA5 at MMIO 0x810c510000 (irq = 124, base_baud = 0) is a PL011 rev0
[5.186988] 810c530000.serial: ttyAMA9 at MMIO 0x810c530000 (irq = 125, base_baud = 0) is a PL011 rev0
[5.193654] 810c540000.serial: ttyAMA10 at MMIO 0x810c540000 (irq = 126, base_baud = 0) is a PL011 rev0
[8.819737] systemd[1]: Created slice system-serial\x2dgetty.slice - Slice /system/serial-getty.
[8.870888] systemd[1]: Expecting device dev-ttyGS0.device - /dev/ttyGS0...
[8.877859] systemd[1]: Expecting device dev-ttyUTC0.device - /dev/ttyUTC0...

```

Thanks!!

---

<div class="post-metadata">

**Author:** ![KevinFFF](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/kevinfff/32/15508_2.png) [@KevinFFF](https://forums.developer.nvidia.com/u/KevinFFF)\
**Post date:** [July 30, 2026, 3:38am UTC](https://forums.developer.nvidia.com/t/jp7-2-thor-ttyama10-error/378406/7 "2026-07-30T03:38:13Z")

</div>

> [@SamM11](#):
>
> I then applied the patch you provided to **UART9** , but it still does not function correctly.

Please share the full dmesg and device tree in your case for further check.

For UART9, you need to update the following lines:

```auto
- dmas = <&gpcdma 10 10 TEGRA_SID_GPCDMA>,
- <&gpcdma 10 20 TEGRA_SID_GPCDMA>;
+ dmas = <&gpcdma 10 10 TEGRA264_GPCDMA_SID_UART9>,
+ <&gpcdma 10 20 TEGRA264_GPCDMA_SID_UART9>;
 			dma-names = "rx", "tx";
 			iommus = <&smmu1_mmu TEGRA264_GPCDMA_SID_UART9>;

```

---

<div class="post-metadata">

**Author:** ![SamM11](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/samm11/32/389301_2.png) [@SamM11](https://forums.developer.nvidia.com/u/SamM11)\
**Post date:** [July 30, 2026, 5:38am UTC](https://forums.developer.nvidia.com/t/jp7-2-thor-ttyama10-error/378406/8 "2026-07-30T05:38:28Z")

</div>

Hi @KevinFFF ,

below are my dtsi setting:

`tegra264.dtsi`

```auto
uart5: serial@810c510000 {
			compatible = "arm,pl011", "arm,primecell";
			reg = <0x81 0x0c510000 0x0 0x10000>;
			interrupts = <GIC_SPI 171 IRQ_TYPE_LEVEL_HIGH>;
			clocks = <&bpmp TEGRA264_CLK_UART5>,
				 <&bpmp TEGRA264_CLK_PLLP_OUT0>;
			clock-names = "uartclk", "apb_pclk";
			assigned-clocks = <&bpmp TEGRA264_CLK_UART5>;
			assigned-clock-parents = <&bpmp TEGRA264_CLK_PLLP_OUT0>;
			dmas = <&gpcdma 11 11 TEGRA264_GPCDMA_SID_UART5>,
			       <&gpcdma 11 21 TEGRA264_GPCDMA_SID_UART5>;
			dma-names = "rx", "tx";
			iommus = <&smmu1_mmu TEGRA264_GPCDMA_SID_UART5>;
			dma-coherent;
			arm,primecell-periphid = <0x00051011>;
			resets = <&bpmp TEGRA264_RESET_UART5>;
			reset-names = "serial";
			status = "disabled";
		};

```

```auto
uart9: serial@810c530000 {
			compatible = "arm,pl011", "arm,primecell";
			reg = <0x81 0x0c530000 0x0 0x10000>;
			interrupts = <GIC_SPI 172 IRQ_TYPE_LEVEL_HIGH>;
			clocks = <&bpmp TEGRA264_CLK_UART9>,
				 <&bpmp TEGRA264_CLK_PLLP_OUT0>;
			clock-names = "uartclk", "apb_pclk";
			assigned-clocks = <&bpmp TEGRA264_CLK_UART9>;
			assigned-clock-parents = <&bpmp TEGRA264_CLK_PLLP_OUT0>;
			dmas = <&gpcdma 10 10 TEGRA264_GPCDMA_SID_UART9>,
			       <&gpcdma 10 20 TEGRA264_GPCDMA_SID_UART9>;
			dma-names = "rx", "tx";
			iommus = <&smmu1_mmu TEGRA264_GPCDMA_SID_UART9>;
			dma-coherent;
			arm,primecell-periphid = <0x00051011>;
			resets = <&bpmp TEGRA264_RESET_UART9>;
			reset-names = "serial";
			status = "disabled";
		};

```

[dmesg.txt](https://forums.developer.nvidia.com/secure-uploads/nvidia/original/4X/5/a/7/5a722d1001a5403c0a69ea52c31e62998a8bfa0a.txt) (130.1 KB)

Thanks!!

---

<div class="post-metadata">

**Author:** ![KevinFFF](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/kevinfff/32/15508_2.png) [@KevinFFF](https://forums.developer.nvidia.com/u/KevinFFF)\
**Post date:** [July 31, 2026, 12:47am UTC](https://forums.developer.nvidia.com/t/jp7-2-thor-ttyama10-error/378406/10 "2026-07-31T00:47:30Z")

</div>

Your device tree configurations for UART5/UART9 look good to me.

```auto
[142.613801] uart-pl011 810c530000.serial: DMA channel TX dma0chan19
[142.613831] uart-pl011 810c530000.serial: DMA channel RX dma0chan9
[171.366592] uart-pl011 810c510000.serial: DMA channel TX dma0chan20
[171.366625] uart-pl011 810c510000.serial: DMA channel RX dma0chan10

```

Do you run any command so that it prints above messages?

Could you verify UART loopback test before connecting with other UART device?

---

<div class="post-metadata">

**Author:** ![SamM11](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/samm11/32/389301_2.png) [@SamM11](https://forums.developer.nvidia.com/u/SamM11)\
**Post date:** [July 31, 2026, 5:27am UTC](https://forums.developer.nvidia.com/t/jp7-2-thor-ttyama10-error/378406/11 "2026-07-31T05:27:24Z")

</div>

Hi @KevinFFF ,

I used a UART loopback tool for testing, and the message appeared when I used PuTTY.

Thanks!!

---

<div class="post-metadata">

**Author:** ![SamM11](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/samm11/32/389301_2.png) [@SamM11](https://forums.developer.nvidia.com/u/SamM11)\
**Post date:** [August 5, 2026, 5:20am UTC](https://forums.developer.nvidia.com/t/jp7-2-thor-ttyama10-error/378406/12 "2026-08-05T05:20:02Z")

</div>

Hi @KevinFFF ,

Any update?

Thanks!!

---

<div class="post-metadata">

**Author:** ![KevinFFF](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/kevinfff/32/15508_2.png) [@KevinFFF](https://forums.developer.nvidia.com/u/KevinFFF)\
**Post date:** [August 5, 2026, 6:00am UTC](https://forums.developer.nvidia.com/t/jp7-2-thor-ttyama10-error/378406/13 "2026-08-05T06:00:41Z")

</div>

> [@SamM11](#):
>
> I used a UART loopback tool for testing, and the message appeared when I used PuTTY.

Do you mean the issue is specific to the serial application you are using?  
(i.e. there’s no issue when you use PuTTY?)

---

<div class="post-metadata">

**Author:** ![SamM11](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/samm11/32/389301_2.png) [@SamM11](https://forums.developer.nvidia.com/u/SamM11)\
**Post date:** [August 6, 2026, 5:35am UTC](https://forums.developer.nvidia.com/t/jp7-2-thor-ttyama10-error/378406/14 "2026-08-06T05:35:52Z")

</div>

Hi @KevinFFF ,

Sorry, I may not have explained the issue clearly. Let me describe the situation again.

I am currently using a custom carrier board with **JetPack 7.2**. I found that **UART5 (`serial@810c510000`, `ttyAMA5`)** and **UART9 (`serial@810c530000`, `ttyAMA9`)** cannot be used properly.

My test method is as follows:

- I connect **UART5** to a UART loopback fixture.
- I use **PuTTY** to perform a loopback test.
- The characters I type on the keyboard should be echoed back and displayed in the PuTTY terminal.
- After testing UART5, I repeat exactly the same procedure with **UART9**.

With this test method, **both UART5 and UART9 work correctly on JetPack 7.1** , and the characters I type are echoed back as expected.

However, **on JetPack 7.2, neither UART works correctly by default**.

then I found this discussion and applied the modification you previously suggested. After applying the patch, **UART5 works correctly** , but **UART9 still does not function**.

The following `dmesg` messages appear when I connect to the UART using PuTTY:

```auto
[142.613801] uart-pl011 810c530000.serial: DMA channel TX dma0chan19
[142.613831] uart-pl011 810c530000.serial: DMA channel RX dma0chan9
[171.366592] uart-pl011 810c510000.serial: DMA channel TX dma0chan20
[171.366625] uart-pl011 810c510000.serial: DMA channel RX dma0chan10

```

Could you let me know whether these `dmesg` messages are expected, or if they indicate any issue with the UART or DMA configuration on JetPack 7.2?

Thanks!!

---

<div class="post-metadata">

**Author:** ![KevinFFF](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/kevinfff/32/15508_2.png) [@KevinFFF](https://forums.developer.nvidia.com/u/KevinFFF)\
**Post date:** [August 7, 2026, 1:48am UTC](https://forums.developer.nvidia.com/t/jp7-2-thor-ttyama10-error/378406/15 "2026-08-07T01:48:49Z")

</div>

> [@SamM11](#):
>
> With this test method, **both UART5 and UART9 work correctly on JetPack 7.1** , and the characters I type are echoed back as expected.
> 
> However, **on JetPack 7.2, neither UART works correctly by default**.

As there’s no issue with JP7.1, could you share the full device tree and dmesg for both releases?

---

<div class="post-metadata">

**Author:** ![SamM11](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/samm11/32/389301_2.png) [@SamM11](https://forums.developer.nvidia.com/u/SamM11)\
**Post date:** [August 7, 2026, 9:34am UTC](https://forums.developer.nvidia.com/t/jp7-2-thor-ttyama10-error/378406/16 "2026-08-07T09:34:37Z")

</div>

Hi @KevinFFF ,

JP7.1:  
[dmesg\_jp71.txt](https://forums.developer.nvidia.com/secure-uploads/nvidia/original/4X/4/c/5/4c55a5834b69065ba42e05e373a2c6ebb9ae690a.txt) (130.0 KB)  
[tegra264.dtsi\_jp71.txt](https://forums.developer.nvidia.com/secure-uploads/nvidia/original/4X/6/8/9/689239c7a8c626be4fdb009b1a9e78f032c31e50.txt) (283.2 KB)

JP7.2:  
[dmesg\_jp72.txt](https://forums.developer.nvidia.com/secure-uploads/nvidia/original/4X/a/d/5/ad550e264942ed6ec5d428e72f07e0a21563c7ca.txt) (130.0 KB)  
[tegra264.dtsi\_jp72.txt](https://forums.developer.nvidia.com/secure-uploads/nvidia/original/4X/8/0/e/80ee191744e6eb5bf06e568986fbfc772985a6e9.txt) (279.7 KB)

Thanks!!

---

<div class="post-metadata">

**Author:** ![KevinFFF](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/kevinfff/32/15508_2.png) [@KevinFFF](https://forums.developer.nvidia.com/u/KevinFFF)\
**Post date:** [August 11, 2026, 6:03am UTC](https://forums.developer.nvidia.com/t/jp7-2-thor-ttyama10-error/378406/17 "2026-08-11T06:03:53Z")

</div>

> [@SamM11](#):
>
> After applying the patch, **UART5 works correctly** , but **UART9 still does not function**.

The uart-pl011 … DMA channel TX/RX … messages are expected and only indicate that the UART driver successfully allocated DMA channels, so they do not by themselves imply a UART or DMA failure.  
The more likely issue is that UART9 on JetPack 7.2 still needs the same SID/device-tree fix as UART5, so it is expected that UART5 works after the patch while UART9 still does not.

```auto
uart9: serial@810c530000 {
        dmas = <&gpcdma 10 10 TEGRA264_GPCDMA_SID_UART9>,
               <&gpcdma 10 20 TEGRA264_GPCDMA_SID_UART9>;
        dma-names = "rx", "tx";
        iommus = <&smmu1_mmu TEGRA264_GPCDMA_SID_UART9>;
};

```

---

<div class="post-metadata">

**Author:** ![SamM11](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/samm11/32/389301_2.png) [@SamM11](https://forums.developer.nvidia.com/u/SamM11)\
**Post date:** [August 13, 2026, 1:48am UTC](https://forums.developer.nvidia.com/t/jp7-2-thor-ttyama10-error/378406/18 "2026-08-13T01:48:48Z")

</div>

Hi @KevinFFF ,

Thanks for reply,

Sorry, I realized that the UART 9 device tree configuration in the `tegra264.dtsi_jp72.txt` file I uploaded previously was incorrect. The actual image I flashed was indeed modified according to your suggested approach, but UART 9 is still not functioning properly.

I also provided the device tree that I modified for JP7.2 earlier in this discussion.

> [@Jp7.2 thor ttyAMA10 error](https://forums.developer.nvidia.com/t/jp7-2-thor-ttyama10-error/378406/8):
>
> Hi @KevinFFF , below are my dtsi setting: tegra264.dtsi uart5: serial@810c510000 { compatible = "arm,pl011", "arm,primecell"; reg = \<0x81 0x0c510000 0x0 0x10000\>; interrupts = \<GIC\_SPI 171 IRQ\_TYPE\_LEVEL\_HIGH\>; clocks = \<&bpmp TEGRA264\_CLK\_UART5\>, \<&bpmp TEGRA264\_CLK\_PLLP\_OUT0\>; clock-names = "uartclk", "apb\_pclk"; assigned-clocks = \<&bpmp TEGRA264\_CLK\_UART5\>; assigned-clock-parents = \<&bpmp TEGRA264\_CLK\_PLLP\_OUT0\>; dmas = \<&gpcdma 11 11 TEGRA264\_GPCDMA\_SID\_UART5\>,…

And I found a discussion where someone face the same issue with the UART 9 loopback test.  
[[Link](https://forums.developer.nvidia.com/t/unable-to-use-uarts-on-agx-thor/379821)]

Thanks!!

---

<div class="post-metadata">

**Author:** ![KevinFFF](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/kevinfff/32/15508_2.png) [@KevinFFF](https://forums.developer.nvidia.com/u/KevinFFF)\
**Post date:** [August 13, 2026, 2:11am UTC](https://forums.developer.nvidia.com/t/jp7-2-thor-ttyama10-error/378406/19 "2026-08-13T02:11:15Z")

</div>

Hi SamM11,

Could you create a new topic or move to another thread as the current one is specific to UART10(`/dev/ttyAMA10`)?  
All the UARTs should work pretty much the same since they use similar drivers.

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/system/32/68080_2.png) [@system](https://forums.developer.nvidia.com/u/system)\
**Post date:** [September 9, 2026, 5:10am UTC](https://forums.developer.nvidia.com/t/jp7-2-thor-ttyama10-error/378406/21 "2026-09-09T05:10:28Z")

</div>

Closed on September 9, 2026, 5:10am UTC

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