Orin nx 很低概率发生system Configuration

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin NX
1

orin nx 8g/16g jp5.1.1 客户自定板子

orin nx reboot或者关机 之后很低概率发生system Configuration，一开始设备能正常运行，但是重启或者关机之后有很低概率出现如下情况，需要重新配置之后才能进入系统。有不少客户反馈此问题。请问一下这是什么原因导致的，感谢

1ba7671b2f67b83b66d9ba5b7d1b323
1ba7671b2f67b83b66d9ba5b7d1b3231920×2560 1.13 MB

2

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

The provided information appears to be a system configuration and reboot details for a Jetson Orin NX device. Here’s a breakdown of the information:

  • Jetson Orin NX: This is the device model, which is part of the NVIDIA Jetson Orin series.
  • orin nx 8g16g: This likely refers to the device’s memory configuration, with 8 GB of RAM and 16 GB of storage.
  • jp511: This is probably a device identifier or a specific configuration for the Jetson Orin NX.
  • orin nx reboot system: This indicates that the system has rebooted.
  • Configuration 1ba7671b2f67b83b66d9ba5b7d1b323: This is a unique configuration identifier, possibly a hash or a serial number.
  • 19202560: This number is likely a timestamp or a system identifier.
  • 113 MB: This is probably the amount of memory used or available on the system.

Comparing this information to the provided context, we can see that the Jetson Orin NX is part of the NVIDIA Jetson Orin series, which includes the Jetson Orin Nano Series, Jetson Orin NX Series, and Jetson AGX Orin Series. The context also mentions the Jetson Software Architecture, Boot Architecture, and Partition Configuration, but it does not provide specific details about the Jetson Orin NX device.

In terms of debugging and system configuration, the provided information suggests that the system has rebooted, and the configuration identifier and timestamp may be useful for troubleshooting or identifying specific system states. However, without more context or information about the system’s behavior, it is difficult to provide a more detailed analysis.

To better understand the system configuration and behavior, it would be helpful to have more information about the system’s logs, error messages, or specific issues that are being encountered. Additionally, referencing the NVIDIA Jetson Linux Developer Guide and the Jetson Orin Fuse Specification Application Note may provide more insight into the system’s configuration and behavior.

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

6

聽起來跟系统不能正常启动 - #16 by WayneWWW

請確認一下 /etc/systemd/system/default.target是否在問題發生後又產生出來

7

default.zip (338 Bytes)

/etc/systemd/system/default.target 文档如下：

[Unit]
Description=OEM Configuration
Requires=basic.target
Conflicts=rescue.service rescue.target multi-user.target
After=basic.target rescue.service rescue.target
AllowIsolate=yes
Wants=oem-config.service network-manager.service getty-static.service systemd-user-sessions.service systemd-resolved.service
8

Hi,

這裡不是請你貼這個內容… 我們不需要這個
我們的問題是當問題發生前後你有沒有看到 “/etc/systemd/system/default.target” 這個檔案又跑出來…

9

这个是客户使用过过程中出现，客户一般都不会关注有没有这个文档

10

因為現在沒有任何方法可以複製出問題, 所以可以請客戶或是你們那邊先來關注一下這個檔案的狀況嗎?

簡單來說, oem-config做完之後會主動刪除/etc/systemd/system/default.target.
如果這個檔案不知道為何又重新跑出來, 那oem config就會重新跳出來…

11

确实有这个文件，但是不知道为什么会出现这个文档。

是否删除此文档，就不会出现此配置

12

現在的問題是/etc/systemd/system/default.target刪除之後看起來會因為不明原因又生成回來.

所以需要詢問客戶那邊是否在oem-config回來之前有特別做什麼步驟.

13

没有做什么特别步骤，断电之后，再插电，就出现了系统配置，然后在系统配置这个环境下查看到了有 default.target

15

hi,

請問你在這裡貼的檔案內容是客戶發生問題之後提供給你的,還是你自己隨意從bsp中找出來的?

16

是的，是从客户的机器里面拷贝出来的

17

請問客戶在問題發生之後重新設定一次oem config過後/etc/systemd/system/default.target 的內容有變嗎?
(預期應該要變)

18

还没设置，客户准备把机器寄给我们，等收到设备之后我设置一下之后看看会不会变

1 Like
19

Is this still an issue to support? Any result can be shared?