# Issue with Variscite VAR-SOM-MX8M-NANO

**URL:** <https://hub.mender.io/t/issue-with-variscite-var-som-mx8m-nano/2840>\
**Category:** General Discussions\
**Created:** [November 5, 2020, 4:42pm UTC](https://hub.mender.io/t/issue-with-variscite-var-som-mx8m-nano/2840 "2020-11-05T16:42:26Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![gphillips-a2e](https://avatars.discourse-cdn.com/v4/letter/g/7bcc69/32.png) [@gphillips-a2e](https://hub.mender.io/u/gphillips-a2e)\
**Post date:** [November 19, 2020, 2:52pm UTC](https://hub.mender.io/t/issue-with-variscite-var-som-mx8m-nano/2840/7 "2020-11-19T14:52:15Z")

</div>

@drewmoseley  
I tried the suggested `local.conf` changes. I had an error building:

```auto
/home/yocto/nano/var-fsl-yocto/build_xwayland/tmp/work/imx8mn_var_som-poky-linux/fsl-image-qt5/1.0-r0/bootfs.image_sdimg/*: No such file or directory      

```

Based on [https://hub.mender.io/t/yocto-warrior-build-failing-on-do-image-sdimg-for-beaglebone/1706](https://hub.mender.io/t/yocto-warrior-build-failing-on-do-image-sdimg-for-beaglebone/1706), I tried adding this to the end of `local.conf`:

```
IMAGE_BOOT_FILES = "u-boot.bin"                                                                                              

```

This solved the build problem, but when I booted the image I got “Bad Linux ARM64 Image Magic!”.

---

_[View the full topic](https://hub.mender.io/t/issue-with-variscite-var-som-mx8m-nano/2840)._