Toradex Easy Installer fails to load after flashing board with Qt 5.12 Demo Image

After flashing the Apalis iMX6 evaluation board with the Qt 5.12.2 image (https://docs.toradex.com/105532-b2qt-embedded-qt5-image-apalis-imx6-tezi.tar)
via Toradex Easy Installer, Toradex Easy Installer no longer works for further flash updates. Instead it stalls when “Starting kernel …”.

Toradex Easy Installer becomes usable again once the board is flashed using the
legacy method (Flashing Embedded Linux to iMX6 Modules) and a
Toradex image (https://developer1.toradex.com/files/toradex-dev/uploads/media/Colibri/Linux/Images/Apalis-iMX6_LXDE-Image_2.7-20180104.tar.bz2).

Easy Installer is being started using “run distro_bootcmd” after copying “boot.scr” and “tezi.itb” to an SD card as described
here (Linux - Distro Boot).

These are the last lines of output from the console when Easy Installer stalls (Qt 5.12.2):

## Loading fdt from FIT Image at 12100000 ...
Using 'config@1' configuration
Trying 'fdt@1' fdt subimage
    Description:  Apalis iMX6 Device Tree
    Type:         Flat Device Tree
    Compression:  uncompressed
    Data Start:   0x1350acfc
    Data Size:    50361 Bytes = 49.2 KiB
    Architecture: ARM
    Hash algo:    md5
    Hash value:   67b35a20ece1bd6c1c0639fed8dc7b47
Verifying Hash Integrity ... md5+ OK
Booting using the fdt blob at 0x1350acfc
Loading Kernel Image ... OK
Loading Device Tree to 2fff0000, end 2ffff4b8 ... OK

Starting kernel ...

[    1.303423] snvs-secvio 20cc000.caam-snvs: can't get snvs clock

These are the last lines of output from the console when Easy Installer works (Toradex LXDE - 2.7):

## Loading fdt from FIT Image at 12100000 ...
Using 'config@1' configuration
Trying 'fdt@1' fdt subimage
    Description:  Apalis iMX6 Device Tree
    Type:         Flat Device Tree
    Compression:  uncompressed
    Data Start:   0x1350acfc
    Data Size:    50361 Bytes = 49.2 KiB
    Architecture: ARM
    Hash algo:    md5
    Hash value:   67b35a20ece1bd6c1c0639fed8dc7b47
Verifying Hash Integrity ... md5+ OK
Booting using the fdt blob at 0x1350acfc
Loading Kernel Image ... OK
Loading Device Tree to 2fff0000, end 2ffff4b8 ... OK

Starting kernel ...

[    1.283105] snvs-secvio 20cc000.caam-snvs: can't get snvs clock
Running /etc/rc.local...
Apalis-iMX6_ToradexEasyInstaller_1.8-20181019

Welcome to Toradex Easy Installer

This is a Linux based installer for Toradex modules. Currently the
installer does not have a serial console interface. You can use the
Toradex Easy Installer through any of the available display interfaces
using USB mouse/keyboard or via network using VNC. Use:
# ip addr show eth0
to display the Ethernet IP address or use USB RNDIS at IP 192.168.11.1.

/ # 

Does anyone have any insight as to what could be causing this issue?

Greetings @Jimmy,

Unfortunately I was unable to reproduce your issue on my end. Going to need to gather some more info here.

Best Regards,
Jeremias

Thank you for getting back to me so quickly.

I have narrowed down the issue to the U-boot environment variable fdt_file. It is set to imx6q-apalis-ixora-v1.1.dtb in the Qt demo image instead of imx6q-apalis-eval.dtb to match the board.

Once I set it to imx6q-apalis-eval.dtb I am eventually able to start Easy Installer, but I would like to know if there is a recommended way to set U-boot environment variables as part of a Yocto image build.

Thank you. Creating a patch fixed my issue with custom-built images. How should I mark my issue as resolved?

The most straightforward way in Yocto would be to clone our u-boot source and create a patch, then add that patch to the respective u-boot recipe in Yocto.

The file where the default environment variables are defined in u-boot: http://git.toradex.com/cgit/u-boot-toradex.git/tree/include/configs/apalis_imx6.h?h=2016.11-toradex.