The current burning method is as follows:
only burn qspi ：
sudo ./flash.sh -c bootloader/t186ref/cfg/flash_t234_qspi.xml jetson-orin-nano-devkit nvme0n1p1
all burn：
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -p “-c ./bootloader/t186ref/cfg/flash_t234_qspi.xml” -c ./tools/kernel_flash/flash_l4t_t234_nvme.xml --showlogs --network usb0 jetson-orin-nano-devkit nvme0n1p1
Because somethings installed in the file system will be lost after being updated. I am currently debugging the driver, so I do not want to update the file system. How to modify the burning method
Hi 550399056
To burn Qspi without rfs, you can use your mentioned command:
sudo ./flash.sh -c bootloader/t186ref/cfg/flash_t234_qspi.xml jetson-orin-nano-devkit nvme0n1p1
To flash a specific partition, please refer to the Workflow 9 section in the Linux_for_Tegra/tools/kernel_flash/README_initrd_flash.txt:
Workflow 9: Flash inidividual partition
Initrd flash has an option to flash individual partitions based on the index file.
When running initrd flash, index files are generated under tools/kernel_flash/images
based on the partition configuration layout xml (images/internal/flash.idx for internal storage,
images/external/flash.idx for external storage). Using "-k" option, initrd flash can flash one
partition based on the partition label specified in the index file.
Examples:
For flashing eks partition on internal device:
$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh -k eks jetson-xavier mmcblk0p1
For flashing kernel-dtb partition on external device:
$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh \
--external-device nvme0n1p1 \
-c ./tools/kernel_flash/flash_l4t_external.xml \
-k kernel-dtb --external-only jetson-xavier mmcblk0p1
To flash only the kernel image, you can replace it at /boot/Image with the new kernel image you build in the Orin Nano.
Before proceeding with any flashing operation, it’s highly recommended that you perform a backup of your device.