The difference between ./ and ./

when i use xxx/Linux_for_tegra/tools/kernel_flash/,it will show using ./,for example,
sudo ./tools/kernel_flash/ --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 ./ --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 ./ instead
./tools/kernel_flash/ cannot flash anything to your nvme. If you plug an empty nvme to jetson, run only, then in the end your nvme will still be empty. can only flash mmcblk0p1.

But initrd flash will use to boot into initrd, and then flash the nvme from initrd. Thus, nvme drive will have file in the end.


ok,thank your reply,i know it.
so if i will repalce files in a not empty nvme ,i should still use initrd flash.

If you want to flash file system to an empty nvme, then use initrd flash.

If you just want to boot from nvme and nvme already had a filesystem on it, then you can also use

1 Like

Now i will repalce dtb file of nvme driver(nvme driver has filesystem already), i used ./ sricpt

sudo BOOTDEV=nvme0n1p1 ./ -r --no-systemimg -k kernel-dtb jetson-xavier-nx-devkit-emmc nvme0n1p1


sudo BOOTDEV=nvme0n1p1 ./ -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?

thanks you !

As I said in previous comment, has no ability to flash anything to the nvme drive.

1 Like

ok, appreciate.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.