Jetson Orin UEFI boot error

andres_r8 · September 2, 2022, 10:04pm

Hello,

Trying to boot the Jetson AGX Orin, it passes MB1 and MB2. Then, it fails on UEFI.

▒▒NOTICE:  BL31: v2.6(release):4fa405dbd
NOTICE:  BL31: Built : 20:16:55, Aug 10 2022
I/TC:
I/TC: Non-secure external DT found
I/TC: OP-TEE version: 3.16 (gcc version 9.3.0 (Buildroot 2020.08)) #2 Thu Aug 11 03:23:19 UTC 2022 aarch64
I/TC: WARNING: This OP-TEE configuration might be insecure!
I/TC: WARNING: Please check https://optee.readthedocs.io/en/latest/architecture/porting_guidelines.html
I/TC: Primary CPU initializing
I/TC: WARNING: Test OEM keys are being used!
I/TC: This is only for TZ-SE testing and should NOT be used for a shipping product!
E/TC:00 0 jetson_user_key_pta_init:700 jetson_user_key_pta_init: Failed (f0100006).
E/TC:00 0 call_initcalls:43 Initcall __text_start + 0x000dab50 failed
I/TC: Primary CPU switching to normal world boot
ERROR:   Exception reason=0 syndrome=0xbe000411
ERROR:   **************************************
ERROR:   RAS Uncorrectable Error in IOB, base=0xe010000:
ERROR:          Status = 0xec000612
ERROR:   SERR = Error response from slave: 0x12
ERROR:          IERR = CBB Interface Error: 0x6
ERROR:          Overflow (there may be more errors) - Uncorrectable
ERROR:          MISC0 = 0x44020040
ERROR:          MISC1 = 0x5554860000000000
ERROR:          MISC2 = 0x0
ERROR:          MISC3 = 0x0
ERROR:          ADDR = 0x80000000367fed40
ERROR:   **************************************
ERROR:   sdei_dispatch_event returned -1
Unhandled Exception in EL3.
x30            = 0x0000000050010b84
x0             = 0x0000000000000000
x1             = 0x0000000000000000

My carrier board does not have HDMI port or Display Port. I tried to disable the DP in the dtb node display@13800000{status = “disabled”;} and also following the instructions on nvdisp Readme, but it does not work.

To reverse this process, and skip display init and revert to a boot flow
without boot splash/display init on T194 boards, complete the following steps:

Change the TBCFILE= line in p3668.conf.common and p2972-0000.conf.common to
point to uefi_jetson.bin, for example:
TBCFILE=“bootloader/uefi_jetson.bin”;

Remove the UEFIFILE= line from the above files.

Edit flash.sh, and remove the following lines:
if [ “${CHIPID}” = “0x19” ] and [ ${UEFIFILE} != “” ]; then
echo “NVDISP+UEFI in ${TBCFILE} …”
truncate --size=393216 “${TBCFILE}”
cat “${UEFIFILE}” >> “${TBCFILE}”
fi;

Delete nvdisp-init.bin from your BSP Linux_for_Tegra/bootloader directory.

Reflash your board.
Now only UEFI will be run as the CPU-BL and no boot splash BMP will appear
on HDMI.

Trumany · September 4, 2022, 11:50pm

Adding @WayneWWW

WayneWWW · September 5, 2022, 3:40am

Hi,

You are using Orin but not Xavier. The p3668 and p2972 configs are for Xavier… so they do not matter here.

Have you reflashed your board + module with sdkmanager already?

andres_r8 · September 7, 2022, 10:56pm

I actually just modified the files:

p3701.conf.common → ODMDATA="gbe-uphy-config-0,hsstp-lane-map-3,nvhs-uphy-config-0,hsio-uphy-config-0" and TBCFILE="bootloader/uefi_jetson.bin"
flash.sh → removing the lines:

if [ “${CHIPID}” = “0x19” ] and [ ${UEFIFILE} != “” ]; then
echo “NVDISP+UEFI in ${TBCFILE} …”
truncate --size=393216 “${TBCFILE}”
cat “${UEFIFILE}” >> “${TBCFILE}”
fi;

Deleted nvdisp-init.bin from my BSP Linux_for_Tegra/bootloader directory.
Reflashed my board with both flash script and sdk manager.

TWarren · September 28, 2022, 2:59pm

As Wayne says, the nvdisp-init stuff (P3668.conf.common, p2972-0000.conf.common and any ‘CHIPID = 0x19’ sections in flash.sh) apply ONLY to T194/Xavier boards, not your Orin AGX system. So please don’t modify any files based on the nvdisp-init README for your system - it isn’t used at all. That includes your P3701.conf.common config file - leave it alone.

As to the UEFI RAS error you are seeing, Wayne can work with our UEFI team to diagnose that.

Tom

andres_r8 · October 10, 2022, 3:55pm

Hello

Here is an update: I used the uefi_jetson.bin from edk2-nvidia-r35.1.0.1 the latest release. It looks like the RAS error is not present anymore, however, a new error makes the boot unsuccessful.

Here is the last fragment of the booting process:

PROGRESS CODE: V02020000 I0
PROGRESS CODE: V02020004 I0
PROGRESS CODE: V02020003 I0
XhcCheckUrbResult: STALL_ERROR! Completecode = 6
XhcControlTransfer: error - Device Error, transfer - 2
XHCI: Don't support multi-TT feature for Hub now. (force to disable MTT)
PROGRESS CODE: V02020006 I0
DeviceDiscoveryBindingStart, failed to reset moduleDevice Error
TegraI2cStartRequest: No ACK received
Failed to read eeprom (No Response)
TegraI2cStartRequest: No ACK received
Failed to read eeprom (No Response)
TegraI2cStartRequest: No ACK received
Failed to read eeprom (No Response)
TegraI2cStartRequest: No ACK received
Failed to read eeprom (No Response)
TegraI2cStartRequest: No ACK received
Failed to read eeprom (No Response)
TegraI2cStartRequest: No ACK received
Failed to read eeprom (No Response)
TegraI2cStartRequest: No ACK received
Failed to read eeprom (No Response)
TegraI2cStartRequest: No ACK received
Failed to read eeprom (No Response)
TegraI2cStartRequest: No ACK received
Failed to read eeprom (No Response)
TegraI2cStartRequest: No ACK received
Failed to read eeprom (No Response)
PROGRESS CODE: V02020000 I0
SNP:PHY: PhyDxeInitialization () Failed to reset Phy
DeviceDiscoveryBindingStart, driver returned Device Error to start notification
PROGRESS CODE: V02010000 I0
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02010000 I0
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02010000 I0
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02010004 I0
PROGRESS CODE: V02010004 I0
DeviceDiscoveryBindingStart, driver returned Unsupported to start notification
DeviceDiscoveryBindingStart, driver returned Unsupported to start notification
PROGRESS CODE: V02020000 I0
PROGRESS CODE: V02020000 I0
Jetson UEFI firmware (version 202209.0-a87aded built on 2022-10-07T21:37:20+00:0
0)
Press ESCAPE for boot options **********************************
**  WARNING: Test Key is used.  **
**********************************
**  WARNING: Test Key is used.  **
......PROGRESS CODE: V03051007 I0
InstallFdt: Installing Kernel DTB
Processing "L4T Configuration Settings" DTB overlay
Deleting fragment fragment@0
Processing "Add PCIe C5 dual mode support" DTB overlay
Deleting fragment fragment@1
Deleting fragment fragment@2
Processing "Jetson Concord (40Pin RT5658)" DTB overlay
Deleting fragment fragment@0
Deleting fragment fragment@1
Deleting fragment fragment@2
Deleting fragment fragment@3
Deleting fragment fragment@4
Deleting fragment fragment@5
Deleting fragment fragment@6
Deleting fragment fragment@7
Deleting fragment fragment@8
Deleting fragment fragment@9
Deleting fragment fragment@12
Deleting fragment fragment@13
Deleting fragment fragment@14
Deleting fragment fragment@15
Processing "Add P3737 A03 Overlay Support" DTB overlay
Deleting fragment fragment@0
Processing "Add P3737 A04 Overlay Support" DTB overlay
Deleting fragment fragment@0
Processing "L4T Rootfs Information" DTB overlay
Deleting fragment fragment@0
UpdateRamOopsMemory: RamOopsBase: 0x82C200000, RamOopsSize: 0x200000
PROGRESS CODE: V03051001 I0
[Bds]Booting UEFI eMMC Device
PROGRESS CODE: V03058000 I0
add-symbol-file /dvs/git/dirty/git-master_linux/out/nvidia/bootloader/uefi/Jetson_RELEASE/Build/Jetson/RELEASE_GCC5/AARCH64/Silicon/NVIDIA/Application/L4TLauncher/L4TLaunch0
Loading driver at 0x00822B3E000 EntryPoint=0x00822B487CC L4TLauncher.efi
PROGRESS CODE: V03058001 I0

L4TLauncher: Attempting GRUB Boot
L4TLauncher: Attempting Direct Boot
Processing "L4T Configuration Settings" DTB overlay
Deleting fragment fragment@0
Processing "Add PCIe C5 dual mode support" DTB overlay
Deleting fragment fragment@1
Deleting fragment fragment@2
Processing "Jetson Concord (40Pin RT5658)" DTB overlay
Deleting fragment fragment@0
Deleting fragment fragment@1
Deleting fragment fragment@2
Deleting fragment fragment@3
Deleting fragment fragment@4
Deleting fragment fragment@5
Deleting fragment fragment@6
Deleting fragment fragment@7
Deleting fragment fragment@8
Deleting fragment fragment@9
Deleting fragment fragment@12
Deleting fragment fragment@13
Deleting fragment fragment@14
Deleting fragment fragment@15
Processing "Add P3737 A03 Overlay Support" DTB overlay
Deleting fragment fragment@0
Processing "Add P3737 A04 Overlay Support" DTB overlay
Deleting fragment fragment@0
Processing "L4T Rootfs Information" DTB overlay
Deleting fragment fragment@0
ASSERT [DtPlatformDxe] /home/runner/work/edk2-nvidia/edk2-nvidia/workspace/edk2-nvidia/Silicon/NVIDIA/Library/MceAriLib/MceAriLib.c(385): Cluster < (LibPcdGet32(66U))

Resetting the system in 5 seconds.

I’m attaching the complete boot log OrinBoot.log (93.5 KB)

@WayneWWW can you help me to diagnose the UEFI error?
Thanks

WayneWWW · October 11, 2022, 4:04am

Hi,

Is this a custom carrier board you made? If so, please refer to the adaptation guide and disable the eeprom read in mb2…

https://docs.nvidia.com/jetson/archives/r35.1/DeveloperGuide/text/HR/JetsonModuleAdaptationAndBringUp/JetsonAgxOrinSeries.html

andres_r8 · October 15, 2022, 12:03am

Solved using uefi_jetson.bin from release >35 and flashing using jetson-agx-orin-devkit instead of jetson-agx-orin-devkit-as-jao-32gb

system · November 9, 2022, 2:51am

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