The system seems to get stuck for a considerable amount of time during the startup process at the location indicated by the arrow in the below screenshot, just before this log message is printed. Is it possible to optimize this boot time?
Hi 258633901,
Please share the full serial console log with timestamp enabled to check if there’s unexpected delay in your case.
The point you mentioned is about bootloader stage(i.e. UEFI).
There’re no prints since it does not use debug binary by default.
please refer to the full_log.log , there is about 43 second during the “silent stage” :
[15-54-02.115]
[15-54-43.410]
[15-54-43.490]
[15-54-43.490]
[15-54-43.490]
[15-54-43.492]
[15-54-43.504]
[15-54-44.210]Jetson System firmware version 36.4.3-gcid-38968081 date 2025-01-08T01:18:20+00:
full_log.log (96.3 KB)
It seems the longer delay than normal case.
Could you try using debug UEFI to check what cause delay in your case?
You can refer to the instruction in Build with docker · NVIDIA/edk2-nvidia Wiki · GitHub to do so.
Are you using the devkit or custom board for AGX Orin?
We’re using the original core board paired with our self make carrier board. The GitHub solution looks overly complex—are there any simpler debugging approaches?
To further investigate the issue, it is necessary to build a debug UEFI binary.
The problem appears to be specific to your custom carrier board, as we have not observed the same delay on the AGX Orin devkit.
You would likely have the best understanding of the design differences between your board and the reference devkit.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.