Jetson Image Creator

[eduri.lavanya]

I tried to create ajetson disk image using
"jetson-disk-image-creator.sh " script with following command :
sudo ./jetson-disk-image-creator.sh -o sd-blob.img -b jetson-agx-orin-devkit -d SD
But when i executed this i came across the following error:
Chip SKU(00:00:00:D0) ramcode() fuselevel(fuselevel_production) board_FAB()
Error: Unrecognized module SKU
Can anyone help me.
I have also attached the screenshot of the terminal

[linuxdev]

AGX Orin has eMMC memory, and does not use the SD card image. The boot stages don’t have the driver unless you have a third party carrier board (in which case the third party has to provide the driver via its board support package). One would normally flash eMMC for an AGX Orin.

[eduri.lavanya]

i want to create for an eMMC memory only, for that how do i create an image on host pc?
Also i would like to know whether and how can i create a backup of the complete disk and the reflash it again?

[linuxdev]

You just flash, and after flash, you will find these files:

• Linux_for_Tegra/bootloader/system.img (a sparse file)
• Linux_for_Tegra/bootloader/system.img.raw (a raw file)

The above would be true regardless of whether you flash on command line or via JetPack/SDKM. If you want to generate this without actually flashing, then you’d use command line. An example with flash:
sudo ./flash.sh jetson-agx-orin-devkit mmcblk0p1

A variation of this, which does not actually flash:
sudo ./flash.sh --no-flash jetson-agx-orin-devkit mmcblk0p1

Incidentally, sometimes the --no-flash is used to create a signed version of the non-rootfs content. During a flash all partitions, except for rootfs/APP, are signed before being flashed. The default is a NULL key, but the other non-rootfs content is still signed before flashing. Those signed files would normally be deleted after flash, but the --no-flash can be used to keep those files around as well as for creating system.img and system.img.raw.

If you have a Jetson set up the way you like it, then instead of generating an image on the host PC via the sample rootfs, you could instead do one of these:

• Clone the rootfs/APP partition using a recovery mode Jetson and command line. Example:
  sudo ./flash.sh -r -k APP -G my_backup.img jetson-agx-orin-devkit mmcblk0p1
  (produces raw clone my_backup.img.raw and sparse clone my_backup.img)
• Use standard tools such as rsync to do a network backup of the rootfs.

[srivathsan.p]

both the sparse and the raw file where not present after flashing

[linuxdev]

Does the host PC have enough disk space? If this fails during creation, then no file will exist. From the location where the “Linux_for_Tegra/bootloader/” directory exists (cd there), what do you see from:
df -H -T .
(the trailing “.” is important…it means “the current directory”)