# Variscite VAR-SOM-MX8M-MINI : NXP i.MX 8M Mini

**URL:** <https://hub.mender.io/t/variscite-var-som-mx8m-mini-nxp-i-mx-8m-mini/1918>\
**Category:** Yocto Project\
**Created:** [May 14, 2020, 1:51pm UTC](https://hub.mender.io/t/variscite-var-som-mx8m-mini-nxp-i-mx-8m-mini/1918 "2020-05-14T13:51:16Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![ABTP](https://avatars.discourse-cdn.com/v4/letter/a/58f4c7/32.png) [@ABTP](https://hub.mender.io/u/ABTP)\
**Post date:** [April 30, 2021, 2:34pm UTC](https://hub.mender.io/t/variscite-var-som-mx8m-mini-nxp-i-mx-8m-mini/1918/10 "2021-04-30T14:34:41Z")

</div>

Hi Drew

Thanks you for clarifying. I really appreciate your support 🙂

I went ahead and used the exact configs from the templates, and changed the KERNEL\_IMAGETYPE to zImage, but unfortunately I still get the same error ( Bad Linux ARM64 Image magic!) so the kernel is not loaded.

The only thing that kind of worked was to disable mender-uboot and enable mender-grub:

> MENDER\_FEATURES\_ENABLE\_append = " mender-image-sd mender-grub"  
> MENDER\_FEATURES\_DISABLE\_append = " mender-image-uefi mender-uboot"

By doing so, the kernel was loaded successfully and the board booted to Boot2qt, but took around 2 minutes to finish booting (without mender it took less than a minute). Doing it like this means that u-boot loaded grub, then grub loaded the kernel and this is not what I want. I need u-boot to load the kernel.

The guy from this post had the same problem, and said he solved it by changing the dtb file in u-boot-variscite.bbappend. I did the same but no success ☹  
[https://hub.mender.io/t/variscite-var-dart-imx8mm-problem/2811/13](https://hub.mender.io/t/variscite-var-dart-imx8mm-problem/2811/13)

Any other suggestions how to fix the “Bad Linux ARM64 Image magic!” error?

---

_[View the full topic](https://hub.mender.io/t/variscite-var-som-mx8m-mini-nxp-i-mx-8m-mini/1918)._