Strange update and its impacts

[dimaz]

                                          Hello.

I use R36 (release), REVISION: 4.3 with Orin NX board.

Recently I’ve done sudo apt upgrade procedure and got something strange. After rebooting, I observed some update process.

After the system has booted, some output symbols were abnormal.

Before this strange update, everything was OK.

Could you please clarify such behaviour?

[carolyuu]

*** Please note that this reply is generated by LLM automatically ***

Based on the provided context, it appears that you are experiencing an issue with your Jetson Orin NX board after performing a sudo apt upgrade procedure. The issue is characterized by abnormal output symbols after the system has booted.

After reviewing the context, I found several threads related to OTA updates and boot issues on Jetson devices. While none of the threads exactly match your issue, I can provide some insights and possible explanations.

1. OTA Update: The context mentions several threads related to OTA updates on Jetson devices. It’s possible that the sudo apt upgrade procedure triggered an OTA update, which might have caused the abnormal output symbols. However, the context doesn’t provide a clear link between OTA updates and the specific issue you’re experiencing.
2. Boot Issues: There are several threads related to boot issues on Jetson devices, including the Jetson Orin NX. For example, the thread “Jetson Orin NX Login Issue After OTA Update - New System Username/Password Problem” mentions a login issue after an OTA update. While this thread doesn’t exactly match your issue, it suggests that boot issues can occur after OTA updates.
3. R36 Release REVISION 43: The context mentions that you are using R36 release REVISION 43 with the Orin NX board. It’s possible that this specific revision is causing the issue. However, without more information, it’s difficult to determine if this is the root cause.

To clarify the behavior, I would recommend checking the following:

1. System Logs: Check the system logs to see if there are any error messages related to the OTA update or boot process.
2. OTA Update History: Check the OTA update history to see if any updates were applied recently.
3. Boot Configuration: Verify that the boot configuration is correct and that there are no issues with the boot process.

If you’re still experiencing issues, I would recommend seeking further assistance from the NVIDIA forums or support channels, as they may be able to provide more specific guidance on resolving the issue.

In comparison to other threads, your issue seems to be related to the boot process and OTA updates, but the exact cause is unclear. Further investigation is needed to determine the root cause of the issue.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

[dimaz]

It is not answer for my issue.

[DavidDDD]

Hi,

Some questions to confirm:

• Is your device using a developer kit or a custom board?

Thanks

[dimaz]

Hi DavidDDD

This is a custom carrier board.

[dimaz]

I’ve checked it on developer kit, and this update is also presented.
Could you please give some explanation of it?

[DavidDDD]

Hi,

The updates you’re seeing are expected when you run sudo apt upgrade.
If you want to avoid these updates, please comment out the following lines in the file /etc/apt/sources.list.d/nvidia-l4t-apt-source.list:

# SPDX-FileCopyrightText: Copyright (c) 2019-2024 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
# SPDX-License-Identifier: LicenseRef-NvidiaProprietary
#
# NVIDIA CORPORATION, its affiliates and licensors retain all intellectual
# property and proprietary rights in and to this material, related
# documentation and any modifications thereto. Any use, reproduction,
# disclosure or distribution of this material and related documentation
# without an express license agreement from NVIDIA CORPORATION or
# its affiliates is strictly prohibited.

+#deb https://repo.download.nvidia.com/jetson/common r36.4 main
+#deb https://repo.download.nvidia.com/jetson/t234 r36.4 main
+#deb https://repo.download.nvidia.com/jetson/ffmpeg r36.4 main

Thanks

[dimaz]

Hi.

I am not asking, how to escape this process.

I would like to know, what exact is being updated?
And why after this update I see the abnormal symbols on UART console?
I described it on the first message in this topic.

[DavidDDD]

Hi,

@dimaz

I would like to know, what exact is being updated?

Please refer to the Software Packages and the Update Mechanism — NVIDIA Jetson Linux Developer Guide for details.

@dimaz

And why after this update I see the abnormal symbols on UART console?

With internal team confirm, the garbled output from the UART log is expected behavior and not related to the update process.

Please see the Jetson Combined UART documentation and collect only the CCPLX logs.
If the garbled messages persist, please share the logs with us for further analysis.

Thanks

[dimaz]

Hi.

Thank you for hint, I’ve located the problem.

First of all, I separated outputs according to processors:

./nv_tcu_demuxer -d /dev/ttyUSB0
/dev/pts/2 RCE
/dev/pts/3 FSI
/dev/pts/4 PSCFW
/dev/pts/5 DCE
/dev/pts/6 BPMP
/dev/pts/7 SCE
/dev/pts/8 SPE
/dev/pts/9 TZ
/dev/pts/10 CCPLEX: 0

And have seen the warnings from /dev/pts/9 TZ, which probably is mixed with kernel output.
There are two TZ logs, left before update and right after update:

The warnings are:

I/TC: WARNING (insecure configuration): Failed to get monotonic counter for REE FS, using 0
I/TC: WARNING (insecure configuration): Failed to commit dirh counter 75

I see, that OP-TEE was rebuilt on Sep 18 2025 and after it these two warnings appeared.

Could you please clarify situation regarding these warnings and how to get rid of them.

Thank you.