Remove boot messages from screen, xavier nx jetpack 5.1.1

Robotics & Edge Computing Jetson Systems Jetson Xavier NX
,
1

Hi,

I am using xavier nx jetpack 5.1.1. on a custom carrier board.

I am trying to remove the message " L4Tlauncher: attempting direct boot" and " warning test key is used" from the boot log on the screen.
I could remove the message " wearnign … " by commenting line 941 of the file BdsEntry.c located at ~/nvidia-uefi/edk2/MdeModulePkg/Universal/BdsDxe/BdsEntry.c

For the message “L4tlauncher …” I commented line 2388 at the file ~/nvidia-uefi/edk2-nvidia/Silicon/NVIDIA/Application/L4TLauncher/L4TLauncher.c
//ErrorPrint (L"%a: Attempting Direct Boot\r\n", FUNCTION);

the message “L4tlauncher…” is not eliminated. I tried to build and flash multiple times.
How to I remove this message from being printed on the screen?

Any help is appreciated.
Farough

3

You mean all of L4TLauncher: Attempting Direct Boot is still present in the log?
How did you flash the device?

4

Hi Dave,

Yes I mean the entire message: L4TLauncher: Attempting Direct Boot is still in the log.
I flashed the device using the following command:

sudo ./flash.sh -r -k cpu-bootloader jetson-xavier-nx-devkit mmcblk0p1

Regards,
Farough

5

Hi,

L4TLauncher is packed in a file different from the main UEFI binary.
You also have to replace BOOTAA64.efi.

6

Before flashing I replaced that file using he following command:
sudo cp ~/nvidia-uefi/images/BOOTAA64_Jetson_RELEASE.efi ~/nvidia/nvidia_sdk/JetPack_5.1.1_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/bootloader/BOOTAA64.efi

Then flashed using the following command:
sudo ./flash.sh -r -k cpu-bootloader jetson-xavier-nx-devkit mmcblk0p1

Is there anything missing? How do I replace BOOTAA64.efi?

Regards,
Farough

7

BOOTAA64.efi is flashed into the esp partition, not cpu-bootloader.

        <partition name="esp" type="data">
            <allocation_policy> sequential </allocation_policy>
            <filesystem_type> basic </filesystem_type>
            <size> 67108864 </size>
            <file_system_attribute> 0 </file_system_attribute>
            <allocation_attribute> 0x8 </allocation_attribute>
            <percent_reserved> 0 </percent_reserved>
            <filename> ESP_FILE </filename>
            <partition_type_guid> C12A7328-F81F-11D2-BA4B-00A0C93EC93B </partition_type_guid>
            <description> **Required.** EFI system partition with L4T Launcher. </description>
        </partition>
8

Thanks for pointing out the problem. How do I change the flash command to update the BOOTAA64.efi too?

9

sudo ./flash.sh -r -k esp jetson-xavier-nx-devkit mmcblk0p1

10

Is it possible to update the esp and the bootloader at once ? This command only updates the esp.

11

You either flash them one-by-one, or do a whole re-flash without specifying any partitons.

12

Thank you Dave. I will try it. Your instructions were very helpful.

13

I tried the flashing command:

sudo ./flash.sh -r -k esp jetson-xavier-nx-devkit mmcblk0p1

Still the message L4TLauncher: Attempting Direct Boot appears on the boot screen. There is something missing in the flashing procedure.

14

Then please do a whole re-flash.

15

I tried the command sudo ./flash.sh jetson-xavier-nx-devkit mmcblk0p1 to do a whole reflash, still the message L4TLauncher: Attempting Direct Boot appears on the boot screen.

16

You must have missed something compiling the UEFI code. Please check it yourself.
I tried the same setup and I’m sure it’s working this way.

17

This is the command I run to compile all the changes:

sudo bash ~/nvidia-uefi/edk2-nvidia/Platform/NVIDIA/Jetson/build.sh

Does it need a flag or some thing else?

Thanks.

18

Maybe delete everything and start from scratch.

19

Hi,
Thanks for being helpful so far.
Since we have some build products, I can not re-flash the entire OS to remove the boot message : “L4Tlauncher: attempting direct boot”.

I tried the following commands to remove it, but it still exists. What other partition other than cpu-bootloader and esp I should try to flash?
sudo ./flash.sh -r -k cpu-bootloader jetson-xavier-nx-devkit mmcblk0p1
sudo ./flash.sh -r -k esp jetson-xavier-nx-devkit mmcblk0p1

Thanks,
Farough

20

This is all I can suggest.

21

The following flash commands worked. I have NVME on the Jetson and I had to use the NVME as the but I was using the emmc before.

sudo ./flash.sh -k cpu-bootloader jetson-xavier-nx-devkit nvme0n1p1
sudo ./flash.sh -k esp jetson-xavier-nx-devkit nvme0n1p1