# Mender on iMX8 Plus U-Boot Setup Errors

**URL:** <https://hub.mender.io/t/mender-on-imx8-plus-u-boot-setup-errors/4686>\
**Category:** Yocto Project\
**Created:** [February 24, 2022, 8:55pm UTC](https://hub.mender.io/t/mender-on-imx8-plus-u-boot-setup-errors/4686 "2022-02-24T20:55:49Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![whsplk](https://avatars.discourse-cdn.com/v4/letter/w/fbc32d/32.png) [@whsplk](https://hub.mender.io/u/whsplk)\
**Post date:** [March 2, 2022, 3:29pm UTC](https://hub.mender.io/t/mender-on-imx8-plus-u-boot-setup-errors/4686/6 "2022-03-02T15:29:17Z")

</div>

yea probably, Im not an uboot expert but for my board (from toradex), their recipes have a patch to the boot script ([meta-mender-community/0001-Adapt-boot.cmd.in-to-Mender.patch at dunfell · mendersoftware/meta-mender-community · GitHub](https://github.com/mendersoftware/meta-mender-community/blob/dunfell/meta-mender-toradex-nxp/recipes-bsp/u-boot-distro-boot/files/toradex-bsp-5.4.0/0001-Adapt-boot.cmd.in-to-Mender.patch)). This gets compiled down to a `boot.scr` file in my boot directory which reflects these changes.

Several other bsp layers does this too (for e.g [meta-mender-community/boot.cmd.in at dunfell · mendersoftware/meta-mender-community · GitHub](https://github.com/mendersoftware/meta-mender-community/blob/dunfell/meta-mender-odroid/recipes-bsp/odroid-u-boot-scr/files/boot.cmd.in) and [meta-mender/boot.cmd.in at master · mendersoftware/meta-mender · GitHub](https://github.com/mendersoftware/meta-mender/blob/master/meta-mender-raspberrypi/recipes-bsp/rpi-u-boot-scr/files/boot.cmd.in))

I would imagine you would need to implement something similar as well (or atleast check that the `mender_*` commands are being called during boot

---

_[View the full topic](https://hub.mender.io/t/mender-on-imx8-plus-u-boot-setup-errors/4686)._