Cloning Orin Nano

Autonomous Machines Jetson & Embedded Systems Jetson Orin Nano
,
1

Hello everyone,

I am trying to clone Jetson Orin Nano (p3767-0003) from one device to all others, but experience big problems.

Used custom board from seedstudio

At first made an image with ./tools/backup_restore/l4t_backup_restore.sh -b p3509-a02+p3767-0000 and then restore via ./tools/backup_restore/l4t_backup_restore.sh -r p3509-a02+p3767-0000 with changed all scripts inside backup_restore directory as written here

Essentialy search and replace mmcblk0 → nvme0n1

After success flashing second device it, remove jumper and boot, come this screen with error which takes ~5min and then normal boot

error1
error11024×768 160 KB

error2
error21024×273 33.7 KB

Jetson info

photo_2023-07-10 18.02.50
photo_2023-07-10 18.02.501280×649 83.7 KB

Boot log
boot.log (239.2 KB)

Google says can be problem with boot order, but how to fix it?
Is there better way to clone orin nano one to many?

2

during boot up, uefi will tell you to press escape to enter the uefi boot menu. You can modify the boot order using the menu.

Another way is, once you boot up, you can use efibootmgr utility to modify the boot order.

3

Thank you for quick respond, change boot order resolved the problem, by why it happening? Any chance to fix it automatically after clonning via some commands?

4

I think you can change the boot order on the original device so the clone image would have the correct boot order.

5

Thats original device:

BootCurrent: 0001
Timeout: 5 seconds
BootOrder: 0001,0004,0003,0002,0005,0000,0006,0007
Boot0000* Enter Setup
Boot0001* UEFI FORESEE XP1000F128G MML967Q001463 1
Boot0002* UEFI PXEv4 (MAC:48B02DE9D73D)
Boot0003* UEFI PXEv6 (MAC:48B02DE9D73D)
Boot0004* UEFI HTTPv4 (MAC:48B02DE9D73D)
Boot0005* UEFI HTTPv6 (MAC:48B02DE9D73D)
Boot0006* BootManagerMenuApp
Boot0007* UEFI Shell

After clone become

boot_order
boot_order2048×1152 481 KB

6

I see. After cloning, the SSD ID change so it gets added to the end of the boot order.

If you use Jetpack 5.1.1, You can flash you original device with environment variable set:

OVERLAY_DTB_FILE=“BootOrderNvme.dtbo”

so it will priotize booting from NVMe. However, because you use a custom board, I am not sure if the vendor BSP has that feature enabled. In that case, your only option is changing the boot order manually.

7

So, command will be for make an image

OVERLAY_DTB_FILE=“BootOrderNvme.dtbo” ./tools/backup_restore/l4t_backup_restore.sh -b p3509-a02+p3767-0000

And then restore as before?

./tools/backup_restore/l4t_backup_restore.sh -r p3509-a02+p3767-0000
8

No you have to reflash the original device. There is no way to change the boot order when generating the backup image and restoring

9

Any chance to do it with SDK Manager? flashing via flash.sh are breaking OS for some reason

10

Maybe just remove all other options? boot from http are not required, so can I delete all of them from original device, make image and flash it to other devices?

11

I am not sure if that is possible. But yes you can do that

12

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