我使用AGX Orin模组和jetpack5.1.4版本，没有修改源码情况的下，进行了刷机操作，命令sudo ./flash.sh jetson-agx-o
[com COM4] (2026-01-08_164902) COM5 (USB Serial Port (COM5)).log (51.8 KB)
rin-devkit mmcblk0p1 ，刷机正常完成，但是模组无法启动，日志见[com COM4] (2026-01-08_164902) COM5 (USB Serial Port (COM5)).log，麻烦帮忙是什么原因导致的。
*** Please note that this reply is generated by LLM automatically ***
The provided information appears to be a log output from flashing a Jetson AGX Orin module using the flash.sh command. Here’s a breakdown of the information:
jetpack5.1.4: This indicates that the JetPack 5.1.4 version is being used for flashing the module.sudo flash.sh: This is the command used to flash the module. The sudo prefix is used to run the command with superuser privileges.jetson-agx-orin-devkit mmcblk0p1: This specifies the target device, which is the Jetson AGX Orin development kit, and the partition to flash (mmcblk0p1).COM4 and COM5: These are the serial ports used for communication with the module. COM4 is likely the port used for flashing, while COM5 is used for logging.20260108164902: This is a timestamp indicating when the flashing process started.USB Serial Port COM5: This confirms that the logging is being done through the USB serial port COM5.log 518 KB: This indicates that the log file size is approximately 518 KB.Comparing this output to the provided context, we can see that the flashing process is using the jetson-agx-orin-devkit target, which is consistent with the information provided in the context. The context also mentions that the Jetson AGX Orin module can be flashed using the l4t_initrd_flash.sh command, but this is not the case in the provided log output.
In terms of flashing support, the context mentions that the Jetson Orin Nano 4GB-DRAM and 8GB-DRAM modules can be flashed using the l4t_initrd_flash.sh command, while the Jetson AGX Orin module can be flashed using the flash.sh command. The provided log output is consistent with this information.
Overall, the provided log output appears to be a successful flashing process for the Jetson AGX Orin module using the flash.sh command.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
According to below log,
I guess you are using a custom board there but not NV devkit, right…?
[2026-01-08 16:49:05] HSIO UPHY reset has been de-asserted 0x0
[2026-01-08 16:49:05] start PLL 8 calibration timeout
[2026-01-08 16:49:05]
[2026-01-08 16:49:05] FATAL ERROR [FILE=platform/drivers/uphy/uphy-tegra234.c, ERR_UID=2251]: start PLL 8 calibration failed
Then you may need to modify the ODMDATA to disable some I/O if your custom board does not have that interface…