When using updated dtb defined in the exlinux.conf to boot , kernel will stuck, but if I using flash cmd ./flash -k kernel-dtb ... to burn into emmc,

when using updated dtb defined in the exlinux.conf to boot , kernel will stuck, but if I using flash cmd ./flash -k kernel-dtb … to burn into emmc, the kenel will not stuck when boot.
here is the log:
post20231106.txt (20.2 KB)

similar to to the below link:
https://forums.developer.nvidia.com/t/l4t-32-6-1-tx2-nx-loading-default-dtb-trough-extlinux-fdt-causes-kernel-to-hang

Hi,

What JetPack/L4T version are you using?
Any booting log to provide?

That’s because bootloader by default reads kernel-dtb from rootfs as specified in extlinux.conf, and the kernel-dtb partition is not used unless there is no FDT entry specified in extlinux.conf.

I using Tx2_nx dev kit board
the version is 32.5.1

the log was updated on the post as a txt file attachment

Yes , but the dtb is the same for both in the rootfs and in the emmc

Are you using the latest release?

Maybe not, I down load it several month ago. Using Jetpack 32.5.1 all the way

Then please upgrade to the latest L4T 32.7.4.

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