Board description The VAR-SOM-MX8M-MINI is a highly scalable, low power System on Module (SoM), offering a mainstream solution to fit a wide range of applications and cost requirements. Based on NXP’s i.MX 8M Mini with up to 1.8GHz Quad-core ARM Cortex-A53™ plus 400MHz Cortex-M4™ real-time processo…

The integrations we have for Variscite boards use the u-boot-variscite recipe and not the u-boot-imx recipe. Something is changing the configuration in your case; I suspect it is the b2qt layers. You can see the existing recipes here and you will probably need to make a u-boot-imx.bbappend modeled…

Hi Drew Thank you for the quick reply. Its really appreciated :slight_smile: I manged to build the image, though I didn’t have to make any changes to u-boot-imx.bbappend nor to u-boot-variscite.bbappend. I just enabled “mender-uboot” feature in the local.conf file (MENDER_FEATURES_ENABLE_append = …

I think the issue with needing to add mender-uboot explicitly is due to a change in the Mender defaults in the newer branches. It’s possible we need to update the templates for Zeus. It looks like the templates for Dunfell already have that. You may also want to review the templates to make sure yo…

Hi Drew Thanks you for clarifying. I really appreciate your support :slight_smile: 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 …

That error message seems to indicate that it is still trying to use Image format for some reason. Can you run the following: bitbake -e core-image-minimal | grep -B25 ‘^KERNEL_IMAGETYPE=’ and also run the following from uboot? env default -a -f saveenv printenv Drew

The command bitbake -e b2qt-embedded-qt5-image | grep -B25 ‘^KERNEL_IMAGETYPE=’ returns nothing. I modified it and used: bitbake -e b2qt-embedded-qt5-image 2>&1 | grep ^KERNEL_IMAGETYPE= which returns: KERNEL_IMAGETYPE=“Image.gz” and this was set in the local.conf file. So it seems it is…

You need to use zImage instead of Image.gz for the KERNEL_IMAGETYPE. Drew

[image] ABTP: mage.gz My mistake. Actually in the local.conf I have set KERNEL_IMAGETYPE=“zImage” but yocto still packages Image.gz instead. I searched all files where this change can be happening and found only one file where it was set to “Image.gz” and that was “variscite.inc”. In this fi…

Oops, of course. Image is the correct type for 64-bit arm. Sorry about the diversion. I think the issue is that you need to decompress the Image.gz file. It’s not handled automatically. As a quick test you can try changing it to “Image” just to see if that gets past the “Bad Magic” issue but I s…

Initially I had it set to “Image”. If you look at the serial boot output in my post on 28.04.2021 you can see it set to Image. But I was seeing the same “Bad Magic” issue even then. Just to clarify, before I attempted to integrate mender the original Boot2Qt was using “Image.gz” kernel type and the…

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

Board Integrations Yocto Project

Topic		Replies	Views
Variscite VAR_DART_IMX8MM Problem General Discussions	12	2718	November 16, 2020
Issue with Variscite VAR-SOM-MX8M-NANO General Discussions	15	3127	February 20, 2022
Bad Linux ARM64 Image magic! General Discussions zeus	7	8959	May 12, 2021
Toradex Verdin iMX8M Mini Yocto Project yocto , nxp , dunfell	11	3138	June 8, 2023
Info on mender integration Yocto Project dunfell , imx8mm	16	3382	February 16, 2023

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

Related topics