Jetson UEFI r36.4.3 takes an excessively long time during the cold boot process of Orin NX (jetpack6.2), how to optimize UEFI boot time

The attached log file is the debug uart log for Orin NX 16G(jetpack6.2) during cold boot

From debug uart log during boot,we can see the followings:
(1)It takes nearly 30 seconds from UEFI start to Ubuntu system user login
(2)Jetpack6.2 linux kernel+userspace take 15s during the boot process , UEFI takes nearly 15 seconds

How to reduce the time consumption of UEFI r36.4.3

//start boot UEFI start
[2025-09-23 13:57:29.524] [0000.063] I> MB1 (version: 1.4.0.4-t234-54845784-e89ea9bc)

//ubuntu system login
[2025-09-23 13:57:58.716] localhost login:

jetpack6.2_Orin_NX_boot_time_debug_uart_2025-09-23_13_57_12.log (134.3 KB)

agi@localhost:~$systemd-analyze time
Startup finished in 6.911s (kernel) + 8.703s (userspace) = 15.614s
graphical.target reached after 8.684s in userspace

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

Based on the provided context, I will provide a comprehensive answer to the question.

The question is asking how to reduce the time consumption of UEFI during the boot process of a Jetson Orin NX device running JetPack 6.2. The debug UART log provided shows that it takes nearly 30 seconds from UEFI start to Ubuntu system user login, with UEFI taking nearly 15 seconds and the Linux kernel/userspace taking 15 seconds during the boot process.

To reduce the time consumption of UEFI, we can refer to the Boot Time Optimization section in the provided context. It is mentioned that for a Jetson AGX Orin Developer Kit running NVIDIA JetPack 6.0, the average time from a cold power-on to the login prompt is approximately 43 seconds, but can be significantly reduced to approximately 26 seconds by applying optimization techniques.

One of the optimization techniques mentioned is to disable MB1/MB2 logs by modifying the log_level value to 0 in Linux_for_Tegra/bootloader/tegra234-mb1-bct-misc-common.dtsi. This can help reduce the boot time.

However, since the question is specifically asking about reducing the time consumption of UEFI, we need to look at the Boot Architecture section in the provided context. It is mentioned that the Jetson AGX Orin, Orin NX, and Orin Nano Boot Flow includes the following stages: BootROM, PSCROM, MB1, MB2, UEFI, and Cold Boot Sequence.

To reduce the time consumption of UEFI, we can try to optimize the UEFI stage of the boot process. One possible way to do this is to disable unnecessary UEFI features or reduce the verbosity of UEFI logs.

In comparison to the Jetson AGX Orin Developer Kit, the Jetson Orin NX device has a similar boot architecture, but the specific optimization techniques may vary. Therefore, it is recommended to try the optimization techniques mentioned in the Boot Time Optimization section and also explore other possible ways to reduce the time consumption of UEFI specifically.

In summary, to reduce the time consumption of UEFI during the boot process of a Jetson Orin NX device running JetPack 6.2, you can try the following:

  1. Disable MB1/MB2 logs by modifying the log_level value to 0 in Linux_for_Tegra/bootloader/tegra234-mb1-bct-misc-common.dtsi.
  2. Optimize the UEFI stage of the boot process by disabling unnecessary UEFI features or reducing the verbosity of UEFI logs.
  3. Explore other possible ways to reduce the time consumption of UEFI specifically.

Note that the specific optimization techniques may vary depending on the device and software configuration, so it is recommended to try different approaches and measure the results to find the most effective way to reduce the time consumption of UEFI.

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

I guess this is on a custom board?

yes,we found this issue on our customized carrier board, but it can also be replicated on the Orin NX development kit

please follow this to enable UEFI log and check in which part took the time.

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