Change the boot logo of jetson orin nano

Robotics & Edge Computing Jetson Systems Jetson Orin Nano
1

How to change the boot image in jetson orin nano? Can anyone provide the working steps?

3

*** Please note that this reply is generated by LLM automatically ***

Changing the boot image on a Jetson Orin Nano involves several steps, including preparing an SD card with the desired JetPack image, booting the device, and updating the bootloader. Here’s a step-by-step guide on how to change the boot image on a Jetson Orin Nano:

Method 1: Using an SD Card

  1. Prepare an SD card with the desired JetPack image: Download the JetPack 5.1.1 or JetPack 5.1.4 SD card image from the JetPack SDK 5.1.1 or JetPack SDK 5.1.4, respectively. Refer to “Flashing the Image to an SD Card with Etcher” for more information on preparing the SD card image.
  2. Boot the Jetson Orin Nano Devkit with the SD card inserted: Insert the prepared SD card into the Jetson Orin Nano Devkit and boot the device.
  3. Navigate to the Boot Manager: When prompted to “Press ESCAPE for boot options” from the landing page of the UEFI menu, navigate to the “Boot Manager” to check the boot order. Make sure the “UEFI SD Device” is on top of the list. If it’s not, refer to “Customizing the Default Boot Order in the UEFI Menu” for more information on changing the boot order.
  4. Complete the oem-config if needed: Complete the oem-config if prompted.
  5. Update the bootloader (optional): If you want to update the bootloader, refer to the “Update Bootloader” section.

Method 2: Using a BUP Image

  1. Create a BUP image: Create a BUP image for the Jetson Orin Nano Devkit using the build_l4t_bup.sh script. Refer to the “Generating the Bootloader Update Payload (BUP)” section for more information.
  2. Place the target board into Force Recovery Mode: Place the Jetson Orin Nano Devkit into Force Recovery Mode.
  3. Run the build_l4t_bup.sh script: Run the build_l4t_bup.sh script with the required options to create a BUP image for the Jetson Orin Nano Devkit.
  4. Update the bootloader: Update the bootloader using the created BUP image.

Comparison of Methods

Both methods can be used to change the boot image on a Jetson Orin Nano. However, Method 1 is simpler and more straightforward, as it only requires preparing an SD card with the desired JetPack image and booting the device. Method 2, on the other hand, requires creating a BUP image and updating the bootloader, which can be more complex.

Additional Information

  • Make sure to check the current slot bootloader version in the QSPI using the sudo nvbootctrl dump-slots-info command before updating the bootloader. The output “Current version” should be less than “35.6.0”.
  • Refer to the “Updating Jetson Linux with Image-Based Over-the-Air Update” section for more information on updating the BSP on a Jetson device using image-based OTA updates.
  • Note that image-based OTA updates support updates between versions with different partition layouts that require layout changes during the update.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

4

Could you please provide me procedure to boot image using SSD?

6

Hi,

I’d like to clarify the situation.
Do you currently have two storage devices — an SD card and an SSD — both flashed with complete systems, and you want to boot from the SSD?
Or are you planning to flash the system onto the SSD?

Thanks

7

Hello David,

I flashed Jetson Nano using SSD and installed so much stuffs on it. Now I am looking for the procedure to change the boot logo (NVIDIA logo appears during reboot) on flashed Jetson Nano without losing any installed stuffs.

Thanks

8

For this, I followed steps:

  1. Create the NVIDIA UEFI Workspace: edkrepo clone nvidia-uefi-r36 NVIDIA-Platforms r36.4.0-updates
  2. Placed custom logo files and updated the NVIDIA.fvmain.fdf.inc file.
  3. Replaced the files to JetPack directory: uefi_jetson.bin and BOOTAA64.efi
  4. Build the UEFI binary: edk2-nvidia/Platform/NVIDIA/Jetson/build.sh

While flashing, get stuck at:

[ 3.0661 ] The number of images in blob is 17
[ 3.0663 ] blobsize is 22406544
[ 3.0664 ] Added binary blob_uefi_jetson_minimal_with_dtb_sigheader.bin.encrypt of size 2043968
[ 3.0728 ] Added binary blob_pscfw_t234_prod_sigheader.bin.encrypt of size 310768
[ 3.0730 ] Added binary blob_mce_flash_o10_cr_prod_sigheader.bin.encrypt of size 187120
[ 3.0731 ] Added binary blob_tsec_t234_sigheader.bin.encrypt of size 176128
[ 3.0732 ] Added binary blob_applet_t234_sigheader.bin.encrypt of size 279808
[ 3.0733 ] Not supported type: mb2_applet
[ 3.0734 ] Added binary blob_mb2_t234_with_mb2_bct_MB2_sigheader.bin.encrypt of size 440944
[ 3.0735 ] Added binary blob_xusb_t234_prod_sigheader.bin.encrypt of size 164864
[ 3.0736 ] Added binary blob_nvpva_020_sigheader.fw.encrypt of size 2164640
[ 3.0740 ] Added binary blob_display-t234-dce_with_kernel_tegra234-p3768-0000+p3767-0005-nv_sigheader.bin.encrypt of size 12070560
[ 3.0785 ] Added binary blob_nvdec_t234_prod_sigheader.fw.encrypt of size 294912
[ 3.0796 ] Added binary blob_bpmp_t234-TE950M-A1_prod_sigheader.bin.encrypt of size 1027008
[ 3.0799 ] Added binary blob_tegra234-bpmp-3767-0003-3509-a02_with_odm_sigheader.dtb.encrypt of size 204736
[ 3.0801 ] Added binary blob_camera-rtcpu-t234-rce_sigheader.img.encrypt of size 458096
[ 3.0802 ] Added binary blob_adsp-fw_sigheader.bin.encrypt of size 415008
[ 3.0803 ] Added binary blob_spe_t234_sigheader.bin.encrypt of size 270336
[ 3.0804 ] Added binary blob_tos-optee_t234_sigheader.img.encrypt of size 1887312
[ 3.0810 ] Added binary blob_eks_t234_sigheader.img.encrypt of size 9232
[ 3.0887 ] Sending membct and RCM blob
[ 3.0890 ] tegrarcm_v2 --chip 0x23 0 --pollbl --download bct_mem mem_rcm_sigheader.bct.encrypt --download blob blob.bin
[ 3.0891 ] BL: version 1.4.0.4-t234-54845784-e89ea9bc last_boot_error: 0
[ 3.1113 ] Sending bct_mem
[ 3.1402 ] Sending blob
[ 4.4948 ] completed
[ 4.4948 ] Retrieving storage infomation
[ 4.4953 ] tegrarcm_v2 --chip 0x23 0 --oem platformdetails storage storage_info.bin

How I can fix this?

9

Hi,

What is your flashing commands?

Also please make sure device in recovery mode before flashing.

Thanks

10

Hi,

Yes, Jetson Nano was in recovery mode.
Into the JetPack (6.2.1) directory:
Flashing command: sudo ./flash.sh jetson-orin-nano-devkit nvme0n1p1

Also, my uefi_jetson file size is 4.2 MB. Will it create any conflict while flashing?

And after getting flashed, Will my installed things persist?

Thanks

11

Hi,

Please try using the following command to flash only the QSPI on Jetson Orin series, as described in the NVIDIA Jetson Linux Developer Guide:

$ sudo ./flash.sh --no-systemimg -c bootloader/generic/cfg/flash_t234_qspi.xml <board> <rootdev>

Thanks