How to set SSD startup in backup images?

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

Hi:
My Hardware Device: orin nano 4G/orin nx 8G
software version:JetPack 5.1.4
My Orin Nano device was started by SSD, and I used a command to perform a Images backup：

./tools/backup_restore/l4t_backup_restore.sh -e nvme0n1 -b jetson-orin-nano-devkit

Then burn to other orin nano devices:

./tools/backup_restore/l4t_backup_restore.sh -e nvme0n1 -r jetson-orin-nano-devkit

The device that burns backup images is found to have a particularly long startup time during startup;
I connecting to HDMI, found that SSD is relatively late in the boot sequence, and Orin Nano will only boot from SSD after failing to boot in other ways. However, the device I copied the image to directly boot from SSD does not have this problem. How should I modify it?

nano_boot1
nano_boot11920×1440 300 KB

nano_boot2
nano_boot22560×1920 346 KB

2

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

Based on the provided context, I’ll try to address the issue you’re facing with your Jetson Orin Nano device.

Problem Statement:
You have a Jetson Orin Nano device with 4GB of RAM, running JetPack 5.1.4. You created a backup image of the device using a command and then flashed it to another Orin Nano device. However, the device that received the backup image takes a long time to start up, and you noticed that the SSD is relatively late in the boot sequence. The device will only boot from SSD after failing to boot from other sources. In contrast, the original device that was used to create the backup image boots directly from SSD without any issues.

Analysis:
The issue you’re facing seems to be related to the boot process of the Jetson Orin Nano device. The device that received the backup image is taking a long time to start up, and the SSD is being initialized late in the boot sequence. This suggests that there might be an issue with the boot configuration or the device tree.

Possible Solutions:

  1. Check the device tree: Verify that the device tree on the device that received the backup image is correct and matches the original device. You can use the dtc command to compile and decompile the device tree.
  2. Modify the boot configuration: You can try modifying the boot configuration to prioritize the SSD as the boot device. You can use the flash.sh command to update the boot configuration.
  3. Update the nanoboot: You can try updating the nanoboot on the device that received the backup image. The nanoboot is responsible for initializing the device and loading the operating system. You can use the flash.sh command to update the nanoboot.
  4. Check the SSD configuration: Verify that the SSD is properly configured on the device that received the backup image. Check the SSD’s firmware version and ensure that it is compatible with the Jetson Orin Nano device.

Comparison with Other Devices:
In your question, you mentioned that the original device that was used to create the backup image boots directly from SSD without any issues. This suggests that the issue is specific to the device that received the backup image. You can try comparing the boot configurations and device trees of the two devices to identify any differences.

Commands to Try:

  • flash.sh -r <image> <device>: Update the boot configuration and flash the image to the device.
  • dtc -I dtb -O dts <device_tree>: Compile and decompile the device tree.
  • nanoboot --update <nanoboot_image>: Update the nanoboot on the device.

Conclusion:
The issue you’re facing with your Jetson Orin Nano device seems to be related to the boot process and configuration. By trying the above solutions and comparing the configurations of the two devices, you should be able to identify and resolve the issue.

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

3

Boot into BIOS by pressing Escand change the SSD to be first option.

Look under:

Boot Maintenance Manger
Boot Options
Change Boot order

5

Hi,

Please try to use efibootmgr to change the boot order.

# Check original boot order
$ sudo efibootmgr
#BootCurrent: 0008
#Timeout: 5 seconds
#BootOrder: 0008,0004,0003,0002,0005,0000,0006,0007
#Boot0000* Enter Setup
#Boot0002* UEFI PXEv4 (MAC:48B02DEC103D)
#Boot0003* UEFI PXEv6 (MAC:48B02DEC103D)
#Boot0004* UEFI HTTPv4 (MAC:48B02DEC103D)
#Boot0005* UEFI HTTPv6 (MAC:48B02DEC103D)
#Boot0006* BootManagerMenuApp
#Boot0007* UEFI Shell
#Boot0008* UEFI SD Device


# Change to boot HTTPv4 first
$ sudo efibootmgr -o 0004,0008,0003,0002,0005,0000,0006,0007

Thanks

6

Hi, DavidDDD:
The mass-produced images of my device are burned using backup images. I need to solve the problem of the default boot order of the device after burning the backup images, which requires starting from SSD by default.

7

There is a setting in the firmware to add new devices as first boot option, i.e. SSD:

Device Manager
  NVIDIA Configuration
    Boot Configuration
      Add new devices to top or bottom of the boot order

one of the options is Top and that will cause the newly burned SSD image to be the first boot device.

Looking at your screenshots the SSD is at the bottom. However it is still a UEFI setting so you might have to customize your firmware.

8

Hi,elsaco:

Thanks for your reply.

The first priority for devices used to create backup images during startup is SSD. After burning the created image onto another Orin Nano, I encountered the problem of SSD booting later. In my understanding, devices that burn backup images should also start from SSD first.

10

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