I follow README_backup_restore.txt
Workflow 1: To create a backup image to host storage
Workflow 2: To restore a Jetson using a backup image
It seems to be possible, but they all need some scripts and configuration files under the Linux_for_Tegra directory, and cannot be used on other machines (without SDK) as burning machines
How to generate an independent image that can be backed up and burned
Hi channinglan,
What’s your requirement here?
You could just tar the Linux_for_Tegra directory.
Do you want to backup/restore the internal eMMC or external NVMe drive?
1.internal eMMC
2.
The previous version had nvmassflashgen.sh that can package the compiled image for later use, but now this script has disappeared…
Is there a way to package the image and burn ORIN on a linux host without SDK??
BSP package (Linux_for_Tegra) is necessary for many usages (flash, backup, restore…etc).
Have you tried the following command to clone the AGX Orin?
sudo ./flash.sh -r -k APP -G clone.img jetson-agx-orin-devkit mmcblk0p1
Still need the scripts and configuration files in the Linux_for_Tegra directory
Why is the script nvmassflashgen.sh removed in the new board SDK??
After JP5, massflash is included in l4t_initrd_flash.sh.
You could refer to Linux_for_Tegra/tools/kernel_flash/README_initrd_flash.txt for detailed usage.
It seems that you want to generate the package first.
Maybe you could refer to Workflow 2: How to generate images first and flash the target later. in README_initrd_flash.txt.
So, what’s your requirement and use case?
After reference Linux_for_Tegra/tools/kernel_flash/README_initrd_flash.txt workflow 2:
backup: success
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash jetson-agx-orin-devkit mmcblk0p1
restore: failed, device in recovery mode, show ssh connect failed as follow picture.
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only jetson-agx-orin-devkit mmcblk0p1
So， how to restore AGX Orin ?
sudo ./flash.sh -r -k APP -G system.img jetson-agx-orin-devkit mmcblk0p1, generate system.img, move it to Linux_for_Tegra/bootloader/, run “sudo ./flash.sh -r jetson-agx-orin-devkit mmcblk0p1” command. So, this way can not backup and restore AGX Orin in JetPack5.1_R35.2.1?Please check the serial console log at this moment.
It seems caused from boot up issue.
What do you mean that “it can not backup/restore” with these steps?
Is that not work?
I means: sudo ./flash.sh -r jetson-agx-orin-devkit mmcblk0p1, this way can work in AGX XAVIER before, but now can not work. So does this way can work for AGX Orin with Jetpack5.1_R3652.1.
debug console log show as follow picture. I will search follow question in forum or internet at first.
I have search in forum,
ODMDATA="gbe-uphy-config-0,hsstp-lane-map-3,nvhs-uphy-config-0,hsio-uphy-config-16";
cvb_eeprom_read_size = <0x0>; In README_initrd_flash.txt
Workflow 7: Initrd Massflash
Seems to be similar to the nvmassflashgen.sh script
This script can generate mfi_jetson-agx-orin-devkit.tar.gz and perform burning directly on other computers after decompression
It seems boot up stuck in UEFI causing host can’t detect the board during flash.
Yes, it should work for AGX Orin with Jetpack5.1(R35.2.1).
Does this workflow work and meet your requirement?
I hope that only scripts such as clone.img and flash.sh can be used as release versions,
There are too many complicated files in mfi_jetson-agx-orin-devkit.tar.gz, there is a risk of being modified…
For your use case, it seems this approach would be better for packaging all data into clone.img, but this is only available for internal eMMC.
It need the scripts and configuration files in the Linux_for_Tegra directory,
Yes, the scripts and configurations are necessary for flash because it needs to know how to do the flash process for the board…
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.