Flash NX device tree only


Is there a way to flash NX device tree only?

Such the commad from https://developer.ridgerun.com/wiki/index.php?title=Jetson_Nano/Development/Building_the_Kernel_from_Source

Flash device tree only

sudo ./flash.sh -r -k DTB jetson-nano-emmc mmcblk0p1

Thank you,

1 Like

“-k kernel-dtb”.

For any flash problem on NX, please refer to xavier instead of Nano.

Hi WayneWWW,

Thank you for your prompt support.
it works.


sudo ./flash.sh -r -k kernel-dtb jetson-xavier-nx-devkit-emmc mmcblk0p1

how to put programmattically from terminal NX into the recovery mode ?

@Andrey1984, hi
how to put programmattically from terminal NX into the recovery mode ?

sudo reboot --force forced-recovery

1 Like

How to upgrade DTB without flash.sh on Xavier NX?
Jetson TX2 can use dd command to upgrade the singned dtb flie:
sudo dd if=/boot/tegra186-quill-p3310-1000-c03-00-base_sigheader.dtb.encrypt of=/dev/mmcblk0p28
Could nx use the same way?

Do I understand correctly that this command would only update cboot?

sudo ./flash.sh -r -k cpu-bootloader jetson-xavier-nx-devkit-qspi

(and for the B slot)

sudo ./flash.sh -r -k cpu-bootloader_b jetson-xavier-nx-devkit-qspi

You don’t have to flash anything. Just put the new dtb in /boot/ on the device and add an “FDT” entry to extlinux.conf/

INITRD .....
FDT /boot/tegra194-p3668-all-p3509-0000-user-custom.dtb
APPEND .....

CBoot will pick it up on the next reboot.

HA! I just realized I responded to a 2 month old post. :)

There may be a bug trying to flash only a single partition. I was never able to get a flash of just CBoot to work. It somehow corrupted the flash device, maybe by not doing an erase first. Had to flash everything (except system image) to get it back.

Same for me actually. But I edited the flash XML and removed everything related to sdcard to prevent it being overwritten.

That one omits important kernel cmdline arguments (the one with signature is under /boot/dtb/tegra194-p3668-all-p3509-0000.dtb), which the same as in /boot but with “root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4” as extra arguments.

Yeah, you’re correct. I forgot about that but adding those to the APPEND line in extlinux.conf is a more flexible way to set up the boot process. Now if you’re creating a hardened system it’s a different story.