Compulab IOT-GATE-IMX8 does not generate uboot.env file anymore

Dominik-Hstein
Mon, 26 Jun 2023 13:45:20 +0000
General Discussions

Hello,

my goal is to update an NXP imx8mm based Compulab iot-gate-imx8 from Yocto Zeus to Kirkstone.

We have made some modifications two years ago:
We are using u-boot without grub because we wanted to have a read-only boot partition and that was apparently not possible with grub (Making boot filesystem read-only - #8 by rbarlow_bel).
U-Boot then had to be patched to provide a custom environment, which worked as expected in Zeus.

Now I am upgrading to Kirkstone. I have not touched the configs except for updating to Bitbake 2 syntax and I had to include mender-artifact-info because the artifact_info was not generated anymore.

Now at the very end of the compilation it throws an error that uboot.env is missing in tmp/deploy/...

With Kirkstone, u-boot-compulab has been updated from 2020.04 to 2021.04.
I have checked the patch for a custom env manually with

bitbake -c unpack u-boot-compulab
bitbake -c configure u-boot-compulab
bitbake -c compile u-boot-compulab

and it is still applied.
The patch changes the include/configs/iot-gate-imx8.h file, which is only generated after the configure step.

As soon as I remove mender-uboot from the distro features, everything works as expected.

After extensive research, I could not find out why the uboot.env could fail.
Can someone help me what else I should do or what I should try out?

I appreciate any help or reference to resources.
Thank you,
Dominik

19 posts - 3 participants