I’m working on XavierNX based custom board.
I want to clone the App partition in NVMeSSD, so I executed the following on the xaviernx board to create a clone image file.
# img2simg /dev/nvme0n1p1 system.img.ext
You can just replace the system.img.ext during the workflow of initrd_flash.
There should be one step that you can see this image inside the folder.
Relying on the above URL description, we replaced system.img by system.img.ext.
# cp system.img.ext tools/kernel_flash/images/external/system.img
and l4t_initrd_flash.sh with --flash-only option.
$ sudo NO_ROOTFS=0 tools/kernel_flash/l4t_initrd_flash.sh --flash-only \ --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml --showlogs p3509-0000+p3668-0000-qspi internal
As a result, the following error occurred.
error: file_write: write: No space left on device Cannot write output file [ 467]: l4t_flash_from_kernel: Error flashing external device [ 467]: l4t_flash_from_kernel: nvsimg2img ...Linux_for_Tegra/tools/kernel_flash/images/external/system.img /dev/sdg1 failed [ 467]: l4t_flash_from_kernel: The device size indicated in the partition layout xml is smaller than the actual size. This utility will try to fix the GPT.
It seems [tools/kernel_flash/images/external/flash.idx] doesn’t match the size after cloning.
12, 9:0:APP, 516857856, 15032385536, , , fixed-<reserved>-1,
Can we really write clone files to NVMeSSD by simply replacing system.img?
Do we also need to update the partition in flash.idx?
If so, could you please tell me how to update the flash.idx to the size after the clone?