Kirkstone branch results in a broken image

HI,

after building all types of images from GitHub - SolidRun/meta-solidrun-arm-imx8 at kirkstone-imx8m

as in:
bitbake core-image-minimal
bitbake imx-image-full
bitbake imx-image-multimedia

the resulted images imx-image-multimedia-imx8mpsolidrun-20230823130818.rootfs.wic.zst
is ~140 MB in size and when booting it we get:

sh: cannot set terminal process group (-1): Inappropriate ioctl for device
sh: no job control in this shell
sh-5.1# [ 2.812843] usb 4-1: new SuperSpeed USB device number 2 using xhci-hcd
[ 2.865594] hub 4-1:1.0: USB hub found
[ 2.869418] hub 4-1:1.0: 4 ports detected

sh-5.1#

in addition the default value for the devicetree is always
imx8mp-hummingboard-mate.dtb
which requires fixing in the boot prompt to imx8mp-hummingboard-pulse.dtb

thanks.

i would appreciate a response,

thanks.

We have been unable to reproduce the issues you are seeing. Have you attempted a clean build, and verified that you have run repo sync to update all the dependency layers?

Your build as you instructed in the GitHub page for kirkstone cannot be performed due to an initial error so I don’t understand how it wasn’t reproduced on ur end.

this was run under ubuntu18 docker and on a clean env.
also, the dockerfile itself is flawed and missing lz4c (liblz4-tool) and needed fixing.

user@94b294f3d87f:~/rev4_imx8mp_yocto_build/imx-yocto/build-xwayland-imx8mp$ bitbake core-image-minimal
Loading cache: 100% | | ETA: --:–:–
Loaded 0 entries from dependency cache.
Parsing recipes: 100% |#################################################################################################################################################################################################################| Time: 0:00:31
Parsing of 3191 .bb files complete (0 cached, 3191 parsed). 4739 targets, 284 skipped, 5 masked, 0 errors.
ERROR: No recipes in default available for:
/home/user/rev4_imx8mp_yocto_build/imx-yocto/sources/meta-solidrun-arm-imx8/recipes-multimedia/libimxvpuapi/libimxvpuapi2_2.2.2.bbappend

Summary: There was 1 ERROR message, returning a non-zero exit code.