I flashed my device using sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-only --network usb0 --external-device nvme0n1 -c tools/kernel_flash//flash_l4t_t234_nvme.xml jetson-agx-orin-devkit nvme0n1p1
I then used sudo ./tools/kernel_flash/l4t_initrd_flash.sh --initrd jetson-agx-orin-devkit nvme0n1p1 to SSH into the device and cloned the /dev/nvme0n1p1 to /mnt/system.img where I mounted a removable storage device.
I would like to know how may I now use this cloned image to flash the device again?
My use case would be setting up the device with libraries, code and binaries and then flashing devices with my data already on the system.img.
*** Please note that this reply is generated by LLM automatically ***
To flash the Jetson AGX Orin device again using the cloned image, you’ll need to follow these steps:
Prepare the cloned image: Make sure the cloned image is in the correct format and location. You’ve already cloned the image to a removable storage device, which is a good start.
Use the flash.sh script: The flash.sh script is used to flash the device. You’ll need to use this script to flash the device with the cloned image.
To use the flash.sh script, follow these steps:
Connect the removable storage device containing the cloned image to the host machine.
Navigate to the directory where the flash.sh script is located. This is usually in the top-level directory of the BSP (Board Support Package) for the Jetson AGX Orin.
Run the flash.sh script with the following command:
Replace <image_directory> with the path to the directory containing the cloned image on the removable storage device.
The -r option tells the script to use the image from the specified directory instead of the default image.
jetson-agx-orin-devkit is the target board configuration.
mmcblk0p1 is the device where the root file system is located.
Comparison with the original flashing process: The main difference between this process and the original flashing process is the use of the -r option to specify the cloned image directory. This allows you to use a custom image instead of the default image provided with the BSP.
Tips and considerations:
Make sure the cloned image is in the correct format and is compatible with the Jetson AGX Orin device.
Before flashing the device, ensure that the removable storage device is properly connected and recognized by the host machine.
The flashing process will erase all data on the device, so make sure to back up any important data before proceeding.
If you’re using a custom image, ensure that it is properly configured and tested before flashing the device.
By following these steps, you should be able to flash the Jetson AGX Orin device with the cloned image and have your libraries, code, and binaries pre-installed on the system.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
I have attempted to use flash.sh like below: sudo ./flash.sh -r -k APP jetson-agx-orin-devkit nvme0n1p1
and like so sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-only --flash-only --network usb0 --external-device nvme0n1 -c tools/kernel_flash/flash_l4t_t234_nvme.xml jetson-agx-orin-devkit nvme0n1p1
Could you please ellaborate which would be the correct approach to flash the system to boot from nvme? I have read the guide for the version I wish to use
I tried flashing without —flash-only and it did not work.
I then deleted Linux_for_Tegra folder and downloaded it again.
I then ran: sudo tools/l4t_flash_prerequisites.sh sudo ./apply_binaries.sh sudo tools/l4t_create_default_user.sh --username my-username --password my-username --hostname my-hostname --accept-license
I then flashed with sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-only --network usb0 --external-device nvme0n1 -c tools/kernel_flash//flash_l4t_t234_nvme.xml jetson-agx-orin-devkit nvme0n1p1 and it successfully flashed.
I then replaced the Linux_for_Tegra/bootloader/system.img with my sparse image and flashed again with -–flash-only:
However the username and host and the the image flashed appeared to be the clean image with my-hostname and my-username which is different from my sparse image.
