Torizon boot error when using multilib option in yocto

[jammingyu9]

Spec:

Model: Apalis iMX8QM 4GB WB IT V1.1 E
Carrier board: Ixora V1.2A
OS: Linux 5.6.0

Hi,
I’m trying to build a 64bit torizon-core-docker image with 32bit compat libraries.
I tried to build an image with yocto using multilib option added like below in local.conf file.

require conf/multilib.conf
MULTILIBS = "multilib:lib32"
DEFAULTTUNE_virtclass-multilib-lib32 = "armv7athf-neon"
IMAGE_INSTALL_append = "lib32-bash lib32-glibc lib32-libgcc lib32-libstdc++"

when booting, u-boot prompts the following error

## Error: "bootcmd_run" not defined

If I remove the multilib options, it boots fine.
I’m not very sure but it may seem to be related with this issue?

M4 code incorporated into imx-boot halts after a second

Hi Kevin, I haven’t modified the boot.scr from the reference image, it is still: # # Copyright 2020 Toradex # # TorizonCore boot script. if test -z "${altbootcmd}" then env set altbootcmd 'env set rollback 1; run bootcmd' env save fi if test "${rollback}" = "1" && test "${upgrade_available}" = "1" then # Make sure to reset upgrade_available to avoid unnecessary wear # Note this also makes rollback permanent. aktualizr will reset rollback # when a new (hopefully better) up…

I would appreciate any hints or suggestions.
Thank you.

[jeremias.tx]

Greetings @jammingyu9,

May I ask why you are trying to re-build TorizonCore with 32bit compat libraries? Are you running some kind of legacy arm32 program? Also are you trying to run this on the base OS or inside a container?

As for your issue itself it’s strange. In our meta-layer we define bootcmd_run in this file that gets imported during boot time: meta-toradex-torizon/uEnv.txt.in at kirkstone-6.x.y · toradex/meta-toradex-torizon · GitHub

How your changes managed to “undefine” this, is not obvious. In the custom image you created can you locate this uEnv.txt file? Perhaps somehow it got altered or affected.

Best Regards,
Jeremias