I’m having some issues flashing a jetson orin nano devkit with a cloned system.img
Running the command
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p "-c bootloader/t186ref/cfg/flash_t234_qspi.xml" --showlogs --network usb0 jetson-orin-nano-devkit nvme0n1p1
Results in an file_write error: No space left on the device
Prior to this the system.img file is copied to /tools/kernel_flash/images/external/system.img after running
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p "-c bootloader/t186ref/cfg/flash_t234_qspi.xml" --showlogs --network usb0 jetson-orin-nano-devkit nvme0n1p1
to generate the initial binaries.
I’m unsure where the space issue occurs as the raw image size is 220GiB, the host PC has 500 GB of available storage, and the external NVME is a 256 GB drive.
I’ve attached a zip file containing my error log, flash_l4t_external.xml , and flash_t234_qspi.xml files.
flash_error_logs.zip (9.0 KB)
Why are you doing such operations?
Why are you copying the system image after running --no-flash
?
Why are you doing such operations?
I was having issues using ./flash.sh with a nvme drive on a jetson-orin-nano-devkit
Why are you copying the system image after running --no-flash
?
This was done to generate the binaries within /kernal_flash/images/external such as
I was able to successfully flash the device using the procedure below.
-
Boot the device into inititrd and clone the device following the procedure. Make sure the dev kit boots into recovery mode.
Run ‘sudo ./tools/kernel_flash/l4t_initrd_flash.sh --initrd jetson-orin-nano-devkit nvme0n1p1’
Ssh into the device its usually ‘ssh root@fe80::1%usb0’
Mount your external storage device. This device should be larger than the nvme storage on the devkit.
mount /dev/sda1 /mnt
Begin cloning the nvme drive, this takes a while and has no progress bar so be patient
‘dd if=/dev/nvme0n1p1 of=/mnt/system.img.raw’
Unmount the drive
‘sync’
‘umount /mnt’ -
Copy the system.img.raw file onto your host PC then mount it
‘sudo mount -o loop system.img.raw /mnt/rootfs’ -
Compress the rootfs dir into a tarball for later.
‘sudo tar -C /mnt/rootfs -czvf cloned_filesystem.tar.gz . ‘ -
Unpack the tar file into Linux_for_Tegra/rootfs. Make a backup if already have a rootfs in this directory
‘sudo mv rootfs/ rootfs_backup/’
‘sudo tar xpf cloned_filesystem.tar.gz -C Linux_for_Tegra/rootfs/’ -
Now you can flash your Jetson devkit. This will regenerate all .img files needed with your rootfs system from your cloned device.
‘ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml \ -p “-c bootloader/t186ref/cfg/flash_t234_qspi.xml” --showlogs --network usb0 jetson-orin-nano-devkit nvme0n1p1 ’
OK, it’s great to see you get it to work.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.