AGX ORIN starts slowly in version L4T36.2

Robotics & Edge Computing Jetson Systems Jetson AGX Orin
1

By examining the UEFI serial console output, it was found that after the prompt Failed to get BMC Boot Options Parameter 4 (IPMI CompCode = 0x0), the system booted for about 30 seconds.

The following is related log information.

[2023/12/19 16:59:44] add-symbol-file /home/plink/UEFI-source/nvidia-uefi-r36.2-updates/Build/Jetson/DEBUG_GCC5/AARCH64/Silicon/NVIDIA/Drivers/SmbiosBmcTransfer/SmbiosBmcTransfer/DEBUG/SmbiosBmcTransfer.dll 0x10253C1000
[2023/12/19 16:59:44] Loading driver at 0x010253C0000 EntryPoint=0x010253C4BC8 SmbiosBmcTransfer.efi
[2023/12/19 16:59:44] 
[2023/12/19 16:59:44] add-symbol-file /home/plink/UEFI-source/nvidia-uefi-r36.2-updates/Build/Jetson/DEBUG_GCC5/AARCH64/Silicon/NVIDIA/Drivers/SmbiosOemDxe/SmbiosMiscOemDxe/SmbiosMiscOemDxe/DEBUG/SmbiosMiscOemDxe.dll 0x10253B7000
[2023/12/19 16:59:44] Loading driver at 0x010253B6000 EntryPoint=0x010253BAF28 SmbiosMiscOemDxe.efi
[2023/12/19 16:59:44] 
[2023/12/19 16:59:44] Driver CBD2E4D5-7068-4FF5-B462-9822B4AD8D60 was discovered but not loaded!!
[2023/12/19 16:59:44] Driver 9622E42C-8E38-4A08-9E8F-54F784652F6B was discovered but not loaded!!
[2023/12/19 16:59:44] Driver 32DC7535-51EF-445E-BF29-3F6E894D6EB6 was discovered but not loaded!!
[2023/12/19 16:59:44] Driver 30DF5A51-535C-4FF7-ACF2-EF914016699B was discovered but not loaded!!
[2023/12/19 16:59:44] Driver FE5CEA76-4F72-49E8-986F-2CD899DFFE5D was discovered but not loaded!!
[2023/12/19 16:59:44] Driver E44CDDE6-EF19-4A7A-8C90-395747C35F7C was discovered but not loaded!!
[2023/12/19 16:59:44] Driver 4D9CBEF0-15A0-4D0C-83DB-5213E710C23F was discovered but not loaded!!
[2023/12/19 16:59:44] Failed to get BMC Boot Options Parameter 4 (IPMI CompCode = 0x0)
[2023/12/19 16:59:44] Waiting for driver 2 of 3 to complete
[2023/12/19 17:00:24] .SNP:PHY: PhyDxeInitialization () Failed to reset Phy
[2023/12/19 17:00:24] DeviceThreadMain, driver returned Device Error to start notification
[2023/12/19 17:00:24] UpdateFdt: Applying overlays from firmware media.
[2023/12/19 17:00:24] Processing "L4T Configuration Settings" DTB overlay
[2023/12/19 17:00:24] Processing "Tegra234 p3737-0000+p3701-xxxx Dynamic Overlay" DTB overlay
[2023/12/19 17:00:24] Processing "OP-TEE overlay" DTB overlay
[2023/12/19 17:00:24] Processing "Jetson Camera Dual-IMX274" DTB overlay
[2023/12/19 17:00:24] Processing "Jetson Camera E3331 module" DTB overlay
[2023/12/19 17:00:24] Processing "Jetson Camera E3333 module" DTB overlay
[2023/12/19 17:00:24] Processing "Jetson Camera IMX185" DTB overlay
[2023/12/19 17:00:24] UpdateRamOopsMemory: RamOopsBase: 0x102CDF0000, RamOopsSize: 0x200000
[2023/12/19 17:00:24] UpdatePvaFwMemory: PvaFwBase: 0x102D980000, PvaFwSize: 0x280000
[2023/12/19 17:00:24] FtpmProtocol Not Found - Not Found
[2023/12/19 17:00:24] AppendKeys Failed to get dbxSigned_0 Not Found
[2023/12/19 17:00:24] AppendKeys Failed to get dbSigned_0 Not Found
[2023/12/19 17:00:24] AppendKeys Failed to get kekSigned_0 Not Found
[2023/12/19 17:00:24] ListPciDevices: Segment: FF	 Bus: 0x00	 Device: 0x00	 Function: 0x00	Vendor ID: 0xFFFF	Device ID:0x0000
[2023/12/19 17:00:24] ListPciDevices: Segment: FF	 Bus: 0x00	 Device: 0x01	 Function: 0x00	Vendor ID: 0xFFFF	Device ID:0x0000
[2023/12/19 17:00:24] ListPciDevices: Segment: 01	 Bus: 0x00	 Device: 0x00	 Function: 0x00	Vendor ID: 0x10DE	Device ID:0x229E
[2023/12/19 17:00:24] ListPciDevices: Segment: 04	 Bus: 0x00	 Device: 0x00	 Function: 0x00	Vendor ID: 0x10DE	Device ID:0x229C
[2023/12/19 17:00:24] ListPciDevices: Segment: 00	 Bus: 0x00	 Device: 0x00	 Function: 0x00	Vendor ID: 0x10DE	Device ID:0x229C
[2023/12/19 17:00:24] ListPciDevices: Segment: 05	 Bus: 0x00	 Device: 0x00	 Function: 0x00	Vendor ID: 0x10DE	Device ID:0x229A
[2023/12/19 17:00:24] ListPciDevices: Segment: 07	 Bus: 0x00	 Device: 0x00	 Function: 0x00	Vendor ID: 0x10DE	Device ID:0x229A

Attached is the complete serial console output.
boot-slowly.txt (192.4 KB)
Do you have any suggestions?

3

Hi chen.xi,

Are you using the devkit or custom board for AGX Orin?

[2023/12/19 17:00:24] .SNP:PHY: PhyDxeInitialization () Failed to reset Phy

Could you check if there’s still the delay if you don’t connect ethernet cable?

4

Custom carrier board, test the startup speed of this carrier board has no network chip, so it should have nothing to do with the network connection.

At the same time, if the EQOS service is disabled in the UEFI stage according to the previous operation, the network cannot be used after entering the system. In the general version of L4T35.4.1 and L4T35.3.1, the EQOS service in the UEFI stage is disabled. This does not occur, and can effectively solve the problem of slow startup.

5

If you don’t have the requirement of network, you could remove all related features in UEFI.

Please use the following command to clone and build UEFI binary for R36.2

edkrepo clone nvidia-uefi-r36.2 NVIDIA-Platforms r36.2

and share the full serial console log with timestamp enabled after you disable them.

6

Our actual application requires the network chip, just to verify whether the network chip is affected, so the network chip will be removed.

If EQOS services are directly disabled, the network becomes unavailable after the system is logged in. The above log is the serial console log obtained after building UEFI binary for r36.2.

7

Then, you should not disable the network features (including EQOS) in your use case.

Please connect your network chip and check the log to debug why PhyDxeInitialization failed to reset your Phy.