We are running into a problem using Yocto and the Verdin Imx8m SoM. For our custom carrier board we created a new device tree with a new name. While it compiles and is included in the /boot folder, u-boot still boots the imx8mp-verdin-wifi-dev.dtb device tree.
Looking at the u-boot-initial-env file that is generated, the following line stands out:
preboot=setenv fdtfile imx8mp-verdin-${variant}-${fdt_board}.dtb
If, after flashing and booting, I chance the fdtfile to the correct dtb file using setenv and saveenv, the correct device tree is booted.
What would be the recommended way to chance this setting in u-boot?
It looks like the Mender integration patches may be missing that bit. I do see that for the colibri-imx6ull platform we are modifying the preboot setting but not for any other platforms.
I’ll try to get a patch put together but I’m traveling this week for Embedded Linux Conference so it may take some time. Do you have any specific urgency here?
Thanks for the quick reply. For now we fix it manually after a first boot.
If you have time to make a patch in the coming days, that would be very helpful. A link to the Colibri-imx6ull patch would be helpful, then I can have a look at that already the coming days.
I finally got around to testing this and possibly getting a proper fix into the meta-mender-community repository. I would appreciate any feedback you can provide over on github for this proposed change.