Custom Board Boot Failed FvbNorFlashStandaloneMm.c(937): ((BOOLEAN)(0==1))

Robotics & Edge Computing Jetson Systems Jetson AGX Orin
,
1

DRIVE OS Version:
Jetson UEFI firmware (version r36.4.3-85becaf8-dirty built on 2026-01-22T11:52 :44+00:00)

Issue Description:
Our customized motherboard uses UEFI r36.4.3 version, and there are also probability events that may occur,

▒▒I/TC: Reserved shared memory is disabled
I/TC: Dynamic shared memory is enabled
I/TC: Normal World virtualization support is disabled
I/TC: Asynchronous notifications are disabled
I/TC: WARNING: Test UEFI variable auth key is being used !
I/TC: WARNING: UEFI variable protection is not fully enabled !

ASSERT [FvbNorFlashStandaloneMm] /out/nvidia/optee.t234-uefi/StandaloneMmOptee_RELEASE/edk2-nvidia/Silicon/NVIDIA/Drivers/FvbNorFlashDxe/

serial.log (44.3 KB)

image
image1920×1080 213 KB

FvbNorFlashStandaloneMm.c(937): ((BOOLEAN)(0==1))

Once it appears, nothing can be done but disassemble and reinstall the system
problem:

5

Hi,

We dont observe ASSERT in your attachment.
Could your please upload the files again.

Thanks

6

HI DavidDDD
The serial port log is a normal log. The problematic serial port log is shown in the following figure, and no other information can be seen.
The problematic machine has been reprogrammed and has not been reproduced yet.

5709a40d-2363-4b22-adcf-db3d59100e1b
5709a40d-2363-4b22-adcf-db3d59100e1b1920×1440 528 KB

What I mean is that clues can be found in the serial port log of a normal machine? For example, which version of the image is incorrect.

7

Hi,

Please see Assertion3 in

Thanks

8

Thanks

We also found this
From the serial port log and jtop, it can be seen that our baseline is Jetpack 6.2 (R36.4.3), which should already include modifications to Asset 3.

Can we see from the serial port log which parts we haven’t updated? Or is there any way to investigate

11

Hi,

Please try to upgrade to r36.5 and cross check whether the issue exists.

Thanks