L32R 4.3
There are two ways to flash the SD card,
1、sudo ./flash.sh
2、USE Etcher and SD.img file
If I use the /flash.sh method, but the root partition is too small after flashing, and I can’t find a suitable method to modify the partition.
It is said on the Internet that flashing through Etcher and SD.img file is the perfect solution, so I download jetson-nx-developer-kit-sd-card-image.zip tried it and it did solve the previous problem, but I found that after flashing SD in this way, the Image file can be upgraded by changing the /boot/Image file, but DTB cannot use ./flash.sh -r -k kernel-dtb jetson-xavier-nx-devkit mmcblk0p1 to upgrade
please review the file, /boot/extlinux/extlinux.conf,
device tree blob will load from file system instead of kernel partition if you’re having FDT entry in the configure file,
Thank you, but I found that using /flash.sh -r -k kernel-dtb jetson-xavier-nx-devkit mmcblk0p1 did not change /boot/tegra194-p3668-all-p3509-0000.dtb or /boot/dtb/tegra194- p3668-all-p3509-0000.dtb
because those were files on your file system.
the commands, /flash.sh -k kernel-dtb, it update the kernel-dtb partition.
check this, $ ls -al /dev/disk/by-partlabel/ for more details.
thanks
I am even more confused in this way,
1、kernel-dtb → …/…/mmcblk0p4,
Then we update the DTB should be./flash.sh -r -k kernel-dtb jetson-xavier-nx-devkit mmcblk0p4, but all the online tutorials are mmcblk0p1
2、If I set the FDT entry in the configure file, do I need to manually overwrite the FDT object file in Linux?
the command-line, -k kernel-dtb has already point to the correct partitions.
the mmcblk0p1 is actually for the rootdev recognition, it skips flashing rootfs since -k options has included,
so,
below shows the correct command to perform device tree blob partition update.
i.e. $ sudo ./flash.sh -r -k kernel-dtb jetson-xavier-nx-devkit mmcblk0p1
as I said.
device tree blob will load from file system instead of kernel partition if you’re having FDT entry in the configure file,
it’s CBoot functionality includes a default booting scan sequence, please check CBoot session for more details.
thanks