# NXP® i.MX 8MQuad Evaluation Kit (EVK)

**URL:** <https://hub.mender.io/t/nxp-i-mx-8mquad-evaluation-kit-evk/561>\
**Category:** Buildroot\
**Tags:** nxp, buildroot\
**Created:** [May 14, 2019, 8:23am UTC](https://hub.mender.io/t/nxp-i-mx-8mquad-evaluation-kit-evk/561 "2019-05-14T08:23:25Z")\
**Posts on this page:** 2\
**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 14, 2019, 8:23am UTC](https://hub.mender.io/t/nxp-i-mx-8mquad-evaluation-kit-evk/561/1 "2019-05-14T08:23:25Z")

</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.nxp.com/assets/images/en/dev-board-image/MCIMX8M-EVK-ANGLE.jpg)

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 Buildroot releases in the table below have been tested by the Mender community. Please update it if you have tested this integration on other releases

| Buildroot | Build | Runtime |
| --- | --- | --- |
| [2020.02.x](https://git.buildroot.net/buildroot/tag/?h=2020.02) | :test_works: | :test_works: |
| [2019.05.x](https://git.buildroot.net/buildroot/tag/?h=2019.05) | :test_works: | :test_works: |

**Build** Means that the Buildroot 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/devices/yocto-project/bootloader-support/u-boot/integration-checklistt?target=_blank) has been verified.

# Getting started

## Prerequisites

- A supported Linux distribution and dependencies installed on your workstation/laptop as described in the [Buildroot Manual](https://buildroot.org/downloads/manual/manual.html#requirement)
  - NOTE. Instructions depend on which Buildroot version you intend to use.

## Configuring the build

### Setup Buildroot environment

Set the Buildroot tag you are building for:

```auto
# set to your branch, make sure it is supported (see table above)
export BR2_TAG="2020.02.x"

```

Clone this repository:

```auto
git clone https://github.com/mendersoftware/buildroot-mender -b ${BR2_TAG}

```

Change directory to `buildroot-mender`:

```bash
cd buildroot-mender

```

Fetch submodules:

```bash
git submodule update --init

```

## Setup build environment

Generate configuration file (Mender configs merged with upstream config):

```auto
./buildroot-external-mender/board/freescale/imx8mqevk/gen-defconfig.sh 

```

Configure Buildroot:

```auto
make mender_freescale_imx8mqevk_defconfig

```

### 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 deployments](https://docs.mender.io/architecture/standalone-deployments?target=_blank), due to lack of server configuration.

You can edit the

- `buildroot-external-mender/board/common/rootfs_overlay/etc/mender/mender.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.

#### Build for Hosted Mender

To get your tenant token:

- log in to [https://hosted.mender.io](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 `TenantToken`

Example `buildroot-external-mender/board/common/rootfs_overlay/etc/mender/mender.conf`:

```auto
{
  "InventoryPollIntervalSeconds": 5,
  "UpdatePollIntervalSeconds": 5,
  "RetryPollIntervalSeconds": 10,
  "ServerURL": "https://hosted.mender.io",
  "TenantToken": "<paste tenant token here>"
}

```

#### Build for Mender demo server

This is if you have followed the [Getting started documentation](https://docs.mender.io/getting-started/create-a-test-environment) where you launch a Mender server locally and to configure your enviroment to connect to this local server you need to provide the IP address of the server on the local network.

By default the demo enviroment will connect to `docker.mender.io` and `s3.docker.mender.io` and we need to make sure that these are resolved to the local IP address of the running server by adding the following entry to `/etc/hosts`

```auto
echo "192.168.0.100" >> buildroot-external-mender/board/common/rootfs_overlay/etc/hosts

```

No changes are required to the `mender.conf ` file in this case it will be already setup to connecto to `docker.mender.io`.

### Building the image

You can now proceed with building an image:

```auto
make

```

### Using the build output

After a successful build, the images and build artifacts are placed in `buildroot/output/images`,

- `buildroot/output/images/sdcard.img.gz`
- `buildroot/output/images/release-1.mender`

The disk image with the `.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/artifacts/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/architecture/mender-artifacts?target=_blank) 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 only in [Standalone deployments](https://docs.mender.io/architecture/standalone-deployments?target=_blank).

# References

- Sources for this integration can be found at [buildroot-mender](https://github.com/mendersoftware/buildroot-mender)

* * *

_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:** ![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:** [October 25, 2019, 9:46am UTC](https://hub.mender.io/t/nxp-i-mx-8mquad-evaluation-kit-evk/561/2 "2019-10-25T09:46:44Z")

</div>

6 posts were split to a new topic: [CM3 module using Buildroot](https://hub.mender.io/t/cm3-module-using-buildroot/1184)
