# Apalis i.mx8 builds but no working OS

**URL:** <https://hub.mender.io/t/apalis-i-mx8-builds-but-no-working-os/7730>\
**Category:** Yocto Project\
**Tags:** yocto, nxp, toradex, kirkstone, apalis\
**Created:** [April 16, 2025, 12:44pm UTC](https://hub.mender.io/t/apalis-i-mx8-builds-but-no-working-os/7730 "2025-04-16T12:44:10Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Muken](https://avatars.discourse-cdn.com/v4/letter/m/3ec8ea/32.png) [@Muken](https://hub.mender.io/u/Muken)\
**Post date:** [April 16, 2025, 12:44pm UTC](https://hub.mender.io/t/apalis-i-mx8-builds-but-no-working-os/7730/1 "2025-04-16T12:44:10Z")

</div>

Issues with meta-mender Integration on Yocto (Toradex Apalis-i.mx8)  
Hello,

I’m trying to add meta-mender to my Yocto project using the Toradex Apalis-i.mx8. Initially, I encountered many issues related to patches failing during the build process. To work around these, I downgraded to BSP 6.2.0—which aligns with the latest branch for meta-mender-toradex-nxp.

Problem Description  
After building the image and flashing it, I consistently get a black screen. There was one instance where the board booted successfully, but it has failed every time since. I suspect it might be stuck in a permanent reboot cycle, but I’m not certain what I’m doing wrong.

The one or two times were it worked i found that all the mender settings were fine.

Configuration Details  
Below is the relevant section from my local.conf:

TORADEX\_BSP\_VERSION = “toradex-bsp-6.2.0”  
MENDER\_ARTIFACT\_NAME = “release-1”  
INHERIT += “mender-full”  
DISTRO\_FEATURES:append = " systemd"  
VIRTUAL-RUNTIME\_init\_manager = “systemd”  
DISTRO\_FEATURES\_BACKFILL\_CONSIDERED = “sysvinit”  
VIRTUAL-RUNTIME\_initscripts = “”

INHERIT += “mender-toradex”

MENDER\_FEATURES\_ENABLE:append = " mender-uboot mender-image-sd"  
MENDER\_FEATURES\_DISABLE:append = " mender-grub mender-image-uefi"

IMAGE\_CLASSES += “image\_type\_mender\_tezi”  
IMAGE\_FSTYPES:append = " mender\_tezi"  
IMAGE\_FSTYPES:remove = " teziimg"  
KERNEL\_IMAGETYPE:aarch64:mender-grub = “Image”  
IMAGE\_BOOT\_FILES:remove:mender-grub = “boot.scr-verdin-imx8mm;boot.scr”  
IMAGE\_BOOT\_FILES:remove:mender-uboot = “zImage ${KERNEL\_DEVICETREE} overlays.txt overlays/\*;overlays/”

# Settings for apalis-imx8

MENDER\_IMAGE\_BOOTLOADER\_BOOTSECTOR\_OFFSET:apalis-imx8 = “0”  
MENDER\_BOOT\_PART\_SIZE\_MB:apalis-imx8 = “32”  
OFFSET\_SPL\_PAYLOAD:apalis-imx8 = “”  
MENDER\_STORAGE\_DEVICE:apalis-imx8 = “/dev/mmcblk0”  
MENDER\_STORAGE\_TOTAL\_SIZE\_MB:apalis-imx8 = “4096”  
#KERNEL\_DEVICETREE:apalis-imx8 = “freescale/imx8qm-apalis-v1.1-ixora-v1.2.dtb”

MENDER\_UBOOT\_POST\_SETUP\_COMMANDS:append = " ; setenv tdxargs ${tdxargs} ${bootargs}; "  
MENDER\_UBOOT\_POST\_SETUP\_COMMANDS:append = " ; setenv overlays\_file /boot/overlays.txt ; setenv overlays\_prefix boot/overlays/ "

#IMAGE\_INSTALL:append = " mender-client"

I also have some configuration in my .bb that I’m bitbaking, but I don’t believe it is affecting the Mender behavior.

Any help or guidance would be greatly appreciated.

Thank you!