Cannot create a clone of the jetson agx orin 64GB developer kit

[oemer.aydin]

Hi, all.

I want to clone the image of my nvidia jetson agx orin 64GB developer kit that has the Jetpack version 6.2.1 (rev. 1). Afterwards I want to flash it onto another jetson agx orin 64GB developer kit in factory condition. Therefore I have downloaded the Driver Package (BSP) under DRIVERS Jetson Linux Release 36.4.4 | NVIDIA Developer . After unpacking I have also downloaded the Sample Root Filesystem unpacked it with sudo rights inside of Linux_for_Tegra/rootfs. Afterwards I have executed sudo ./apply_binaries.sh inside Linux_for_Tegra. Now when I execute sudo ./flash.sh -r -k APP -G jp_6_2_clone.img jetson-agx-orin-devkit mmcblk0p1 it does not successfully create the clone. Here you can see the output log file:

clone-log.txt (25.7 KB)

Could you please help me?

Thanks in advance.

[carolyuu]

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

I’d be happy to help you with cloning the image of your NVIDIA Jetson AGX Orin 64GB Developer Kit and flashing it onto another kit in factory condition.

First, let’s break down the steps you’ve taken so far:

1. You’ve downloaded the Driver Package (BSP) for Jetson Linux Release 3644 from the NVIDIA Developer website.
2. You’ve unpacked the Driver Package and downloaded the Sample Root Filesystem.
3. You’ve unpacked the Sample Root Filesystem with sudo rights inside the Linux_for_Tegra/rootfs directory.
4. You’ve executed sudo ./apply_binaries.sh inside the Linux_for_Tegra directory.
5. You’re trying to create a clone of the image using sudo ./flash.sh -r -k APP -G jp62-clone.img jetson-agx-orin-devkit mmcblk0p1, but it’s not successful.

Based on the output log file (clonelog.txt) you’ve shared, it seems like there are some issues with the cloning process. However, without more details about the error messages, it’s difficult to pinpoint the exact cause.

That being said, here are some potential issues and suggestions to help you troubleshoot:

1. Make sure you’re using the correct flash.sh command: Double-check that you’re using the correct flash.sh command with the correct options. The command you’re using seems correct, but it’s always a good idea to verify.
2. Verify the jp62-clone.img file: Ensure that the jp62-clone.img file is in the correct location and has the correct permissions. You can try running ls -l jp62-clone.img to verify the file’s existence and permissions.
3. Check the mmcblk0p1 device: Make sure that the mmcblk0p1 device is the correct device for your Jetson AGX Orin 64GB Developer Kit. You can use lsblk or fdisk to verify the device name.
4. Try using a different cloning method: Instead of using flash.sh, you can try using dd command to create a clone of the image. For example: sudo dd if=/dev/mmcblk0p1 of=jp62-clone.img bs=1M
5. Re-run apply_binaries.sh: Try re-running sudo ./apply_binaries.sh inside the Linux_for_Tegra directory to ensure that all the necessary binaries are applied correctly.

If none of these suggestions help, please provide more details about the error messages in the clonelog.txt file, and I’ll do my best to assist you further.

Additionally, since you’re trying to clone the image of your Jetson AGX Orin 64GB Developer Kit, which has Jetpack version 6.2.1 rev 1, you might want to verify that the Sample Root Filesystem you downloaded is compatible with this version. You can check the compatibility by looking at the README file or the release_notes file inside the Sample Root Filesystem directory.

I hope this helps! Let me know if you have any further questions or concerns.

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

[oemer.aydin]

Thanks already. I forgot to install the flash tools with sudo tools/l4t_flash_prerequisites.sh. After rebooting while keeping the usb cable to the jetson and executing the flash command I could create a copy image. After flashing the copy to another factory condition jetson with sudo ./flash.sh -r -k APP jetson-agx-orin-devkit mmcblk0p1 I get an error on bootup after the flash of the jetson that says mount: /mnt: can’t find PARTUID=e717a516-f809-440e-90fd-354d288b33cc. e717a516-f809-440e-90fd-354d288b33cc is the partuuid of mmcblk0p1. I have checked that on the cloned image jetson mmcblk0p1 has the type ext4 and mmcblk0p10 has the mountpoint /boot/efi and type vfat. I have therefore changed on my host pc the file fstab inside of Linux_for_Tegra/rootfs/etc to include:

/dev/root / ext4 defaults 0 1
/dev/mmcblk0p10 /boot/efi vfat defaults 0 1

After reflashing the error persists. I have not executed the apply_binaries.sh script after making the change in fstab.

[oemer.aydin]

What I have done now is mounting the img.raw file and changed the PARTUUID that was set inside of boot/extlinux.conf. This was changed from

LABEL primary
MENU LABEL real-time kernel
LINUX /boot/Image.real-time
INITRD /boot/initrd
APPEND ${cbootargs} root=PARTUUID=e717a516-f809-440e-90fd-354d288b33cc rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 console=ttyAMA0,115200 firmware_class.path=/etc/firmware fbcon=map:0 video=efifb:off console=tty0 nv-auto-config

to

LABEL primary
MENU LABEL real-time kernel
LINUX /boot/Image.real-time
INITRD /boot/initrd
APPEND ${cbootargs} root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 console=ttyAMA0,115200 firmware_class.path=/etc/firmware fbcon=map:0 video=efifb:off console=tty0 nv-auto-config

After creating the image then with img2simg the error that now can be seen is:

Switching from initrd to actual rootfs
/sbin/init: error while loading shared libraries: /lib/aarch64-linux-gnu/libseccomp.so.2: invalid ELF header
Kernel panic - not syncing

[DavidDDD]

Hi,

Please refer to the official documentation below:
Flashing Support — NVIDIA Jetson Linux Developer Guide

Follow Workflow 3: To mass flash the backup image in the guide. This procedure allows you to mass flash the cloned image to other devices.

Thanks.