when i use xxx/Linux_for_tegra/tools/kernel_flash/l4t_initrd_flash.sh,it will show using ./flash.sh,for example, sudo ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash --external-device nvme0n1 -S 100GiB --external-only -c ./xxx/flash_l4t_nvme.xml jetson-xavier-nx-devkit-emmc nvme0n1p1
it will instead of flowing BOOTDEV=nvme0n1 ./flash.sh --no-flash --signed --external-device -S 100GiB -c ./xxx/flash_l4t_nvme.xml jetson-xavier-nx-devkit-emmc nvme0n1p1
so it means i could use ./flash.sh instead
./tools/kernel_flash/l4t_initrd_flash.sh?
flash.sh cannot flash anything to your nvme. If you plug an empty nvme to jetson, run flash.sh only, then in the end your nvme will still be empty. Flash.sh can only flash mmcblk0p1.
But initrd flash will use flash.sh to boot into initrd, and then flash the nvme from initrd. Thus, nvme drive will have file in the end.
sudo BOOTDEV=nvme0n1p1 ./flash.sh -r --no-systemimg -k kernel-dtb -c ./tools/kernel_flash/flash_l4t_nvme_256GB.xml jetson-xavier-nx-devkit-emmc nvme0n1p1
./flash_l4t_nvme_256GB.xml is partition specific for my 256GB ssd,
but the dtb of nvme ssd can’t changed , so what i should do?