Create a image from "3767-300-0000", but it can't restore back to "3767-301-0000"

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

Hi,

I have a orin nano dev kit with Orin NX 16G (“3767-300-0000”).
I download latest L4T R36.4.4.
I flashed it with “sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -p “-c ./bootloader/generic/cfg/flash_t234_qspi.xml” -c ./tools/kernel_flash/flash_l4t_t234_nvme.xml --showlogs --network usb0 jetson-orin-nano-devkit external“, everything works well.

And I created a image by using “sudo ./tools/backup_restore/l4t_backup_restore.sh -e nvme0n1 -b jetson-orin-nano-devkit“,
I can restore image back to another orin nano dev kit with Orin NX 16G (“3767-300-0000”) by using “sudo ./tools/backup_restore/l4t_backup_restore.sh -e nvme0n1 -r jetson-orin-nano-devkit“.
But, I can’t restore image back to another orin nano dev kit with Orin NX 16G (“3767-301-0000”) by using “sudo ./tools/backup_restore/l4t_backup_restore.sh -e nvme0n1 -r jetson-orin-nano-devkit“.

I got following error, could you please check it for me?

image
image1920×502 75.6 KB

2

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

Based on the provided context, it appears that you are trying to restore an image to a different Jetson Orin Nano Developer Kit with a different board ID (37673010000) using the l4t_backup_restore.sh script.

The error message you provided suggests that the image is not compatible with the target device. This is likely due to the fact that the image was created for a device with a different board ID (37673000000).

The l4t_backup_restore.sh script is designed to work with devices that have the same board ID. When you create an image using this script, it includes information specific to the device it was created on, including the board ID.

To resolve this issue, you have a few options:

  1. Re-create the image: You can re-create the image on the new device (Orin NX 16G 37673010000) using the l4t_backup_restore.sh script. This will ensure that the image is compatible with the new device.
  2. Use a different restore method: You can try using a different restore method, such as flashing the device using the l4t_initrd_flash.sh script, as you did initially. This method does not rely on the board ID and may allow you to restore the image to the new device.
  3. Modify the image: You can try modifying the image to make it compatible with the new device. This would require editing the image files to update the board ID and other device-specific information. However, this approach is not recommended, as it can be complex and may lead to unexpected issues.

In summary, the issue you are experiencing is due to the difference in board IDs between the devices. To resolve this, you can re-create the image on the new device, use a different restore method, or modify the image (although this is not recommended).

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

4

Hi,

Do you mean that I have to re-create backup image after NVIDIA PCN every time? I don’t think it’s a solution. :(

6

Hi, may I know if there is any one can help me on this topic?

7

Hi,

Sorry for the late response.

Backup/Restore not support in different board spec.

Please try below topics instead

Thanks

8

Hi David,

I’m using the same SPEC ( Orin NX 16G ), but the P/N of OrinNX16G before Nvidia PCN is 3767-300-0000, and the P/N of OrinNX16G after Nvidia PCN is 3767-301-0000. It’s the same Orin NX 16G, but different P/N since the Nvidia PCN. And I’m using the latest L4T R36.4.4.

9

Hi,

Yes, using a different PCN will cause the restore to fail.
Therefore, if you need to restore the APP partition, we recommend following the topics mentioned above.

Thanks