/boot/extlinux/extlinux.conf configuration FDT does not work.

[leadercxn]

Hi OE4T developer,

I add

UBOOT_EXTLINUX_FDTDIR = "/boot"
UBOOT_EXTLINUX_FDT = "/boot/${DTBFILE}"

cboot-extlinux 

in my yocto local.conf and I can see /boot/extlinux/extlinux.conf in my system.

Now ,I generate a .dtbo and use fdtoverlay to merge .dtb and .dtbo, and then use fdtdump to check the .dtb files are merged successfully, replace the original dtb file with the merged dtb file in /boot. After the reboot, use dtc -I fs /proc/device-tree > dts.txt to find that the merged dtb was not working. Is there something wrong with my operation? Or am I missing something?

[madisongh]

Take a look at the messages generated by cboot on the serial console. Do you see logs from it about processing the extlinux.conf file, loading the kernel DTB, etc.? Are there any error messages in that sequence?

[leadercxn]

I think yocto project may still have some problems with its cboot, I used the cboot_t194.bin file released by NVIDIA r32.7.1 to replace the one generated by yocto, it works.

The attachment is the startup log output from the serial port

xavier-nx-yocto.log
BTW, I use branch kirkstone-l4t-r32.7.x

[madisongh]

Yeah, it sounds like the patches we have to fix other issues in NVIDIA's cboot ext4 filesystem support need to be looked at again.

You can, in the meantime, configure PREFERRED_PROVIDER_virtual/bootloader and PREFERRED_PROVIDER_cboot to be "cboot-prebuilt" to use the pre-built binary instead of building from sources.

[madisongh]

Also, can you try this with the latest on the branch? The error message mentioned in the screen cap of the failure case above isn't in our patches any longer, when we updated from L4T R32.7.2 to L4T R32.7.3.

[leadercxn]

Also, can you try this with the latest on the branch? The error message mentioned in the screen cap of the failure case above isn't in our patches any longer, when we updated from L4T R32.7.2 to L4T R32.7.3.

Okay, I compiled my project using this branch kirkstone-l4t-r32.7.x of that repository tegra-demo-distro, and the resulting that
meta-tegra commit is too old.

[leadercxn]

Also, can you try this with the latest on the branch? The error message mentioned in the screen cap of the failure case above isn't in our patches any longer, when we updated from L4T R32.7.2 to L4T R32.7.3.

Greate, that works~ thanks