Orin NX fails to boot on custom board

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin NX
, ,
1

Hi

We have a custom carrier board designed for Orin NX. I am flashing it with JP5.1.2 and the flash is successful but the board does not boot. It stops at the below. I was able to flash another carrier board of the same type with the same environment and it boots successfully.
I want to know what this error means and why does it specifically stop booting at this point.

ASSERT [HiiDatabase] /home/nvidia-uefi-r35.4.1/edk2/MdeModulePkg/Universal/HiiDatabaseDxe/Font.c(303): GlyphBuffer != ((void *) 0) && Origin != ((void *) 0) && *Origin != ((void *) 0)

Resetting the system in 5 seconds.

Attaching the serial log:

serial_log.txt (3.9 KB)

Flash log:

flash_log.txt (40.5 KB)

3

Hi san1998,

This assertion is caused from the following line in Font.c.
Something is NULL in your case.

ASSERT (GlyphBuffer != NULL && Origin != NULL && *Origin != NULL);

Is the custom board designed by you?
Did you build custom UEFI binary?

Could you reproduce the issue on the devkit?

Does reflashing the board help for this issue?

4

@KevinFFF

I do not face issues on development board. I reverted the UEFI back to original which is not altered and it works.

Sometime i also got this error on the carrier boards:


Synchronous Exception at 0x00000004579E17B4


Synchronous Exception at 0x00000004579E17B4
ASSERT [ArmCpuDxe] /home/nvidia-uefi-r35.4.1/edk2/ArmPkg/Library/DefaultExceptionHandlerLib/AArch64/DefaultExceptionHandler.c(333): ((BOOLEAN)(0==1))

Resetting the system in 5 seconds.

May i know what might be causing this issue as i change the UEFI only to save some boot time. The above errors i have mentioned show DefaultExceptionHandler.c and Font.c although i never disturbed these source files.
I have just disabled network related drivers in uefi.

5

It seems the issue is caused from your customization in UEFI.
Please revert them back one-by-one to clarify which line may cause this issue.

6

@KevinFFF

I have followed the UEFI changes that is documented on the NVIDIA forums. Nothing extra customized other than that. I do not face any issues on the development board but very rarely on the custom carrier boards. And the errors are get are very random like Font.c or ExceptionHandler.c etc. I will still check UEFI customization on my end.

7

Do you mean the issue specific to the custom carrier board?
and it is also hard to reproduce on your board?
Does the reboot help for this state?

You can try to add more debug messages when you hit the issue since we don’t receive related errors before.

9

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