Replace UEFI boot splash screen/logo (Jetpack 5.1 / R35.2.1)

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

Hi NVIDIA,
I would like to change the UEFI boot splash screen logo on my Orin NX production module. I tried to replace nvidiagray480.bmp , nvidiagray720.bmp and nvidiagray1080.bmp with our customized bmp files, then did a full flash, but the result is as follows:

  • An initial delay with a black screen
  • A short flicker of a completely white screen (I tried to use HDMI monitor OSD to check the output resolution from Orin NX is 1280x1024)
    We don’t know why the resolution of 1280x1024 is output from Orin NX and show the white screen.
    Please kindly advise.
    Thanks all.
3

Hi maxs.yeh,

What’s your carrier board for Orin NX?

Do you replace the logo successfully? (i.e. Could you see your logo at boot up?)

Do these two behaviors occur only after you replace the logo image?

4
  1. AVerMedia’s D115OXB
    D115OXB/D115ONB | AVerMedia
  2. Yes, we can see the logo after short flicker, but the short flicker is not normal and result in our LCM is abnormal.
    Our LCM only support 1280x800 but the short flicker is 1280x1024 that we found it by PC monitor OSD.
    Firstly, when we connect the HDMI from AI-Box to our LCM supported 1280x800 then boot the AI-Box, we find it has short flicker for around 5 seconds then see the logo.
    Secondly, we want to double check so connect the HDMI from AI-Box to PC monitor support 1920x1080. Then boot the AI-Box, we find it shows 1280x1024 logo, but we don’t put this 1280x1024 logo into UEFI.
    We have no idea how to debug and solve this problem of short flicker of a completely white screen when connecting HDMI from AI-Box to our 1280x800 LCM.
  3. Yes.
5

May I know what is “LCM” meaning here?

You might need to replace 3 bmp files with different resolution as the original logo files as instruction mentioned.

Is there any abnormal messages during boot up?

Which UEFI branch you are using to build custom uefi_jetson.bin?

6
  1. We connect AI-Box to 10" touch panel with LCM (i.e. LCM display device).
  2. I replaced 3 bmp files with different resolution as your post link of instruction.
  3. I didn’t record log from debug UART port.
  4. The branch of nvidia-uefi-35.2.1
    Thanks.
7

Could you move to latest R35.3.1 to verify and use r35.3.1-updates branch instead?

edkrepo clone nvidia-uefi-r35.3.1-updates NVIDIA-Platforms r35.3.1-updates
8

Would you please tell me if R35.3.1 is included the JP5.1.1 ?
If we use R35.3.1 then we need to upgrade the BSP codebase to JP5.1.1 ?
Currently, our BSP codebase is JP5.1 version.

9

Yes, R35.3.1 is part of Jetpack 5.1.1.

Or do you have the devkit could reproduce the same behavior?

10

No, I don’t have devkit and only buy AVerMedia’s D115OXB.
Is it possible that we can base on nvidia-uefi-35.2.1 (JP5.1) to modify some code to let UEFI boot doesn’t show 1280x1024 logo and maybe let it to show 1280x720 logo?
If it’s possible, please kindly provide the solution or method to me.
Thank you very much ^_^

11

We don’t have a 1280x1024 logo. Our UEFI boot logo support is restricted to the following resolutions mentioned during boot:

Found 640x480
Found 1280x720
Found 1920x1080

Have you tried with another display which supports 1280x720 resolution?

12

We double check it and connect the HDMI from AI-Box to PC monitor supported 1920x1080. Then boot the AI-Box, we find it shows 1280x1024 logo.
We don’t have another display supported 1280x720 resolution.

13

Then it should show 1920x1080 image.

This is just to debug the issue.
Could you also share the block diagram of your connections?
I’m not clear about your usage with “AI-Box” and LCM display.

Or could you also share the serial console log with UEFI bug message enabled for further check?

14

The connections is very simple and only connect HDMI cable to LCM display.
AI-Box —> HDMI cable —> 10" LCM display device wity touch panel

Please check attached boot log file.
2023.07.17_BootLogo_FirstBlankLogo.log (107.1 KB)

15

It seems your current serial console log still no debug message enabled for UEFI.
Please re-build the UEFI and replace your Linux_for_Tegra/booloader/uefi_jetson.bin with uefi_Jetson_DEBUG.bin built by you.

16

Could you kindly tell me how to build out the uefi_Jetson_DEBUG.bin ?
If I need to turn on some flag to build UEFI with DEBUG ?
Thanks.

17

You could refer to the following instruction to setup the build environment for UEFI binary.
Build without docker · NVIDIA/edk2-nvidia Wiki · GitHub

It will generate both uefi_Jetson_RELEASE.bin and uefi_Jetson_DEBUG.bin. Please just build it w/o any change and remember to use the r35.3.1-updates as latest branch.

edkrepo clone nvidia-uefi-r35.3.1-updates NVIDIA-Platforms r35.3.1-updates
19

Our vendor-AVerMedia will provide the log to you.

20

Thanks, we’ve got the bug tracking on this issue.

22

Hi Kevin,
Do you have any progress update?
Thanks.

23

Sorry that I’ve not received the debug logs from partner, let me check the status and will update to you once there’s any progress.