NVIDIA工程师，您好：
我遇到了一个UEFI需要1分钟才能启动的问题，
跟这个帖子中反馈的情况是相同的。
AGX Orin Boot Delay Issue on Custom Board - Jetson & Embedded Systems / Jetson AGX Orin - NVIDIA Developer Forums
我也使用了MGBE功能。
帖子中相同的问题：
TBCDTB_FILE中指定设备树文件ethernet@6800000，status = “disabled”;会导致kernel里面的eth也无法使用。
如何修改设备树文件，让MGBE在UEFI中也生效呢？让UEFI启动不要一直卡在这里：
.SNP:PHY: PhyDxeInitialization () Failed to reset Phy
EqosDeviceDxe:DeviceThreadMain, driver returned Device Error to start notification
Hi hanyu.du,
Are you using the devkit or custom board for AGX Orin?
What’s the Jetpack version in use?
Have you tried to build custom UEFI and disable Eqos related configs?
custom board
R36.4.3
我下载了UEFI并编译了uefi_Jetson_Desbug.bin正在调试。
怎么在UEFI关闭Eqos功能？
Please don’t disable EQOS in UEFI since it may cause MGBE failed to work.
You can replace <Linux_for_Tegra>/bootloader/uefi_jetson.bin with uefi_Jetson_DEBUG.bin you built w/o any change in UEFI source and share the full log for further check.
I have replaced uefi_Jetson_Debug.bin, and the log is the same as the problem link I shared above.
After using MGBE, UEFI startup gets stuck at the same location.
Turning off MGBE does not cause it to get stuck.
uefi.txt (147.3 KB)
How does your MGBE device tree look like ? Please share how is your configuration and scheamtic.
So it is a ethernet switch case but not a PHY case?
yes
switch
Hi,
Switch case requires to discuss with switch vendor. It looks like the device tree is correct to me but we are uncertain if any missing for a switch case.
I am using Marvell’s MV88Q5152 switch.
Since I see that the network in UEFI is not currently enabled, do you mean that I can enable the UEFI network function by modifying the parameters in the device tree?
UEFI and Kernel dtb are same content by default so if you ever enable it in dtb, it will enable on both.
Because the network in my kernel is already working normally, but there is no network in UEFI.
What modifications does NVIDIA need to make to the MGBE processing in UEFI in order to enable the network as it is in the kernel?
Nothing else is needed from our point of view. Need to check with Switch vendor if anything special is required.
Do you have any suggestions for this 1-minute wait time? Is there a way to avoid this wait time?
I need to resolve this issue first.
You could look into eqos driver first and see what got wait there.
Okay, I’ll start by looking into the Eqos content in the UEFI driver.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
