What is the reason for the different phenomena in different modules without changing UEFI?
I made a change to the newly compiled UEFI with reference to this, but it did not get solved.
Do you mean that some AGX Orin modules would hit the issue but some AGX Orin module would not?
If so, I would like to know if the failed modules would work with AGX Orin devkit.
Yes, but with devkit you don’t have that problem,
After comparing UEFI, the content of the log prompt is the same as the content of my post above.
If the failed module would not hit the issue with the devkit board.
I would suggest reviewing and comparing the difference between your custom board and the devkit.
From the error message, they should not appear after remvoing SnpDxe.inf in network stack. Please also check if you apply the binary correctly.
The network on our board is PCI-to-network. Instead of using devkit solutions.
How do I check that SnpDxe.inf is disabled after compiling UEFI binary files?
Could you try to remove the PCI-to-network adapter on your custom board and check if the issue still exist?
The related debug messages from SnpDxe should be removed in your logs.
Should not have anything to do with this, after the system boot, our system network is able to work normally.
2023-08-21_14_09_16.log (281.4 KB)
This is a newly obtained log, and it looks like a new error is affecting the startup.
SNP:PHY: PhyDxeInitialization () Failed to configure Phy
DeviceDiscoveryBindingStart, driver returned Device Error to start notification
SNP:PHY: PhyDxeInitialization () Failed to reset Phy
DeviceDiscoveryBindingStart, driver returned Device Error to start notification
SNP:PHY: PhyDxeInitialization () Failed to configure Phy
DeviceDiscoveryBindingStart, driver returned Device Error to start notification
uefi_Jetson_DEBUG.bin
I only replaced this one file, may I ask whether other files need to be replaced as well?
It is just suggested to clarify the issue.
You could also try to replace <Linux_for_Tegra>/bootloader/BOOTAA64.efi with BOOTAA64_Jetson_RELEASE.efi.
I used the reconstructed UEFI file here to make the following replacement:
cp uefi_Jetson_DEBUG.bin <Linux_for_Tegra>/bootloader/uefi_jetson.bin
cp BOOTAA64_Jetson_RELEASE.efi <Linux_for_Tegra>/bootloader/BOOTAA64.efi
But it didn’t solve the problem. The log information is the same.
2023-08-23_11_03_06.log (274.6 KB)
According to the link you provided before, I modified the following file.
nvidia-uefi-r35.3.1-updates/edk2-nvidia/Platform/NVIDIA/NVIDIA.fvmain.fdf.inc
NVIDIA.fvmain.fdf.inc.patch (1.6 KB)
Then execute the following command to rebuild the BOOTAA64_Jetson_RELEASE.efi and uefi_Jetson_DEBUG.bin files.
./Platform/NVIDIA/Jetson/build.sh
Is the UEFI environment built using this command.
It seems you also need to remove them from NVIDIA.common.dsc.inc.
Please remove #791 to #813 in
edk2-nvidia/Platform/NVIDIA/NVIDIA.common.dsc.inc at r35.4.1-updates · NVIDIA/edk2-nvidia · GitHub.
That is for clone the UEFI source.
If you are using JP5.1.2(R35.4.1) currently, please use the following command instead.
$ edkrepo clone nvidia-uefi-r35.4.1-updates NVIDIA-Platforms r35.4.1-updates
and use the following command to build uefi binary.
$ . edk2-nvidia/Platform/NVIDIA/Jetson/build.sh
We used L4T35.3.1
Since you said 5.1.2 with the same issue so that I thought you have updated to it…
If you are using JP5.1.1(R35.3.1), please use the following command instead.
$ edkrepo clone nvidia-uefi-r35.3.1-updates NVIDIA-Platforms r35.3.1-updates
According to the previous communication, my operation steps are as follows:
edkrepo clone nvidia-uefi-r35.3.1-updates NVIDIA-Platforms r35.3.1-updates
remove #790 to #814 in
https://github.com/NVIDIA/edk2-nvidia/blob/r35.3.1-updates/Platform/NVIDIA/NVIDIA.common.dsc.inc#L790
remove #160 to #182 in
https://github.com/NVIDIA/edk2-nvidia/blob/r35.3.1-updates/Platform/NVIDIA/NVIDIA.fvmain.fdf.inc#L160
cd nvidia-uefi-r35.3.1-updates
./edk2-nvidia/Platform/NVIDIA/Jetson/build.sh
cp images/uefi_Jetson_DEBUG.bin <Linux_for_Tegra>/bootloader/uefi_jetson.bin
cp images/BOOTAA64_Jetson_RELEASE.efi <Linux_for_Tegra>/bootloader/BOOTAA64.efi
cd <Linux_for_Tegra>
sudo ./flash.sh y-c8-agx-orin-3531 mmcblk0p1
But it doesn’t really do anything.
Below is the latest log file.
2023-08-25_11_46_06.log (274.3 KB)
Is there a better way to deal with this? Or is there any device change in the new batch of modules?
The steps provided from you seems fine but it seem still doing PhyDxeInitialization.
Could you also help to remove #65-#74 in the following file?
https://github.com/NVIDIA/edk2-nvidia/blob/r35.3.1-updates/Platform/NVIDIA/NVIDIA.common.dsc.inc#L65
Hello, after removing these two parts of content at the same time, there is no solution, the log is still the same.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.