# NXP® i.MX 8MQuad Evaluation Kit

**URL:** <https://hub.mender.io/t/nxp-i-mx-8mquad-evaluation-kit/567>\
**Category:** Yocto Project\
**Tags:** yocto, sumo, nxp\
**Created:** [May 15, 2019, 9:12pm UTC](https://hub.mender.io/t/nxp-i-mx-8mquad-evaluation-kit/567 "2019-05-15T21:12:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)\
**Post date:** [May 15, 2019, 9:12pm UTC](https://hub.mender.io/t/nxp-i-mx-8mquad-evaluation-kit/567/1 "2019-05-15T21:12:13Z")

</div>

The official [Mender documentation](https://docs.mender.io/) explains how Mender works. This is simply a board-specific complement to the official documentation.

# Board description

The NXP® i.MX 8MQuad Evaluation Kit (EVK) provides a platform for rapid evaluation of the i.MX 8MQuad, i.MX 8MDual and i.MX 8MQuadLite Applications Processors, utilizing 2 to 4x Arm® Cortex®-A53s and 1x Cortex-M4 cores. It brings High-Performance with Low Power, Flexible options of Memory and High-Speed Interfaces as well as Industry-Leading Audio and Video capabilities.

![](https://www.mouser.se/images/marketingid/2018/img/132277340_NXP_iMX8MQuadEvaluationKit.png)

URL: [Vendor board specs](https://www.nxp.com/support/developer-resources/evaluation-and-development-boards/sabre-development-system/evaluation-kit-for-the-i.mx-8m-applications-processor:MCIMX8M-EVK)

# Test results

The Yocto Project releases in the table below have been tested by the Mender community. Please update it if you have tested this integration on other [Yocto Project releases](https://wiki.yoctoproject.org/wiki/Releases?target=_blank):

| Yocto Project | Build | Runtime |
| --- | --- | --- |
| sumo (imx-4.14.98-2.0.0\_ga) | :test_works: | :test_works: |
| zeus (imx-5.4.3-2.0.0\_demo\_mender) | :test_works: | :test_unknown: |

**Build** Means that the Yocto Project build using this Mender integration completes without errors and outputs images.  
**Runtime** Means that Mender has been verified to work on the board. For U-Boot-based boards, the [integration checklist](https://docs.mender.io/system-updates-yocto-project/board-integration/bootloader-support/u-boot/integration-checklist?target=_blank) has been verified.

# Getting started

## Prerequisites

- A supported Linux distribution and dependencies installed on your workstation/laptop as described in the [Yocto Mega Manual](https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#detailed-supported-distros)
  - NOTE. Instructions depend on which Yocto version you intend to use.

- Google repo tool [installed](https://hub.mender.io/t/google-repo/58/2) and in your `PATH`.

## Configuring the build

### Setup Yocto environment

Create a directory for your `mender-imx` setup to live in and clone the  
meta information.

```auto
mkdir mender-imx && cd mender-imx

```

Initialize repo manifest:

```auto
repo init -u https://source.codeaurora.org/external/imx/imx-manifest -b imx-linux-sumo -m imx-4.14.98-2.0.0_demo_mender.xml

```

Fetch layers in manifest:

```auto
repo sync

```

## Setup build environment

Initialize the build environment:

```bash
DISTRO=fsl-imx-xwayland MACHINE=imx8mqevk . fsl-setup-mender.sh -b build

```

### Configure Mender server URL (optional)

This section is not required for a successful build but images that are generated by default are only suitable for usage with the Mender client in [standalone mode](https://docs.mender.io/artifact-creation/standalone-deployment), due to lack of server configuration.

You can edit the `conf/local.conf` file to provide your Mender server configuration, ensuring the generated images and Mender Artifacts are connecting to the Mender server that you are using. There should already be a commented section in the generated `conf/local.conf` file and you can simply uncomment the relevant configuration options and assign appropriate values to them.

Build for Hosted Mender:

```auto
# To get your tenant token:
# - log in to https://hosted.mender.io
# - click your email at the top right and then "My organization"
# - press the "COPY TO CLIPBOARD"
# - assign content of clipboard to MENDER_TENANT_TOKEN
#
MENDER_SERVER_URL = "https://hosted.mender.io"
MENDER_TENANT_TOKEN = "<copy token here>"

```

### Building the image

You can now proceed with building an image:

```auto
bitbake core-image-base

```

Replace `core-image-base` with your desired image target.

### Using the build output

After a successful build, the images and build artifacts are placed in `build/tmp/deploy/images/imx8mqevk/`.

- `build/tmp/deploy/images/imx8mqevk/core-image-base-imx8mqevk.sdimg`
- `build/tmp/deploy/images/imx8mqevk/core-image-base-imx8mqevk.mender`

The disk image (with `.sdimg` suffix) is used to provision the device storage for devices without Mender running already. Please proceed to [the official documentation on provisioning a new device](https://docs.mender.io/system-updates-yocto-project/provisioning-a-new-device?target=_blank) for steps to do this.

On the other hand, if you already have Mender running on your device and want to deploy a rootfs update using this build, you should use the [Mender Artifact](https://docs.mender.io/overview/artifact) files, which have `.mender` suffix. You can either deploy this Artifact in managed mode with the Mender server (upload it under Releases in the server UI) or by using the Mender client [standalone mode](https://docs.mender.io/artifact-creation/standalone-deployment).

# References

- The sources of the Yocto integration can be found in [meta-mender-community/meta-mender-imx](https://github.com/mendersoftware/meta-mender-community/tree/sumo/meta-mender-imx)
- [Secure Over-the-Air Prototype for Linux Using CAAM and Mender](https://www.nxp.com/docs/en/application-note/AN12900.pdf)

* * *

_If this post was useful to you, please press like, or leave a thank you note to the contributor who put valuable time into this and made it available to you. It will be much appreciated!_

---

<div class="post-metadata">

**Author:** ![Amrun-Nisha-R](https://avatars.discourse-cdn.com/v4/letter/a/45deac/32.png) [@Amrun-Nisha-R](https://hub.mender.io/u/Amrun-Nisha-R)\
**Post date:** [May 8, 2020, 8:59am UTC](https://hub.mender.io/t/nxp-i-mx-8mquad-evaluation-kit/567/2 "2020-05-08T08:59:02Z")

</div>

Hi,  
Do you know about the SDK and tools for imx8mq?

---

<div class="post-metadata">

**Author:** ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)\
**Post date:** [May 8, 2020, 6:11pm UTC](https://hub.mender.io/t/nxp-i-mx-8mquad-evaluation-kit/567/3 "2020-05-08T18:11:49Z")

</div>

Hi @Amrun-Nisha-R that’s more likely a question for NXP. We do integrate Mender with their BSP but don’t always enable all the vendor-provided features as our integration here is intended only as a starting point. If you have specific issues we may be able to help.

Drew
