We’ve received many requests for Yocto support on our Nitrogen8M SBC. Below you will find the download link for the image as well as detailed instructions for the build including a features set.
For the Impatient
You can download the Yocto image from here:
As usual, you’ll need to register on our site and agree to the EULA because it contains NXP content.
Since the Nitrogen8M board has no SD card slot, you need to program this image via fastboot or
using U-Boot USB Mass Storage Gadget. Instructions on programming the SW can be found below:
However, you can still flash the image onto an SD card and use an SD Card to USB adapter or flash to a USB stick via zcat and dd under Linux:
~$ zcat *boundary-image*.wic.gz | sudo dd of=/dev/sdX bs=1M
In addition, you can use the etcher utility to flash the SD Card or USB stick via Windows or Linux:
This image uses the warrior branch of our boundary-bsp-platform repository.
This is mostly a clone of fsl-community-bsp-platform with meta-boundary added in.
To build the image, you’ll need these packages installed as well as this repo tool that can be installed like this:
~$ sudo apt-get install repo
Then create your build directory and initialize everything.
~$ mkdir ~/yocto-imx8m && cd yocto-imx8m ~/yocto-imx8m$ repo init -u https://github.com/boundarydevices/boundary-bsp-platform -b warrior ~/yocto-imx8m$ repo sync
~/yocto-imx8m$ MACHINE=nitrogen8m DISTRO=boundary-wayland . setup-environment build
Now bitbake boundary-image-multimedia-full which is equivalent to fsl-image-multimedia-full with Boundary-specific packages such as BD-SDMAC support
~/yocto-imx8m/build$ bitbake boundary-image-multimedia-full
After some time this should build the same image as above.
The image file will deploy to
The image built above contains the following components:
- GPU Vivante libraries 6.2.4p1.8
- VPU Hantro libraries v1.8.0
- GStreamer1.0 1.14.0 for i.MX
- Weston 4.0.0 for i.MX
- qcacld-2.0 Wi-Fi driver for BD-SDMAC
- BlueZ 5.50 with support for BD-SDMAC
The next sub-sections will describe how to test most features.
Please make sure your platform includes the latest U-Boot for i.MX8M:
This version of U-Boot supports the display configuration, allowing to use any of the following displays:
- HDMI display (up to 4k, 1080p recommended)
- 7″ 1280×800 MIPI BD070LIC2_8M
- 8″ 1920×1200 MIPI BD080MCC1
- 10″ 1280×800 MIPI BD101LCC2_8M
Note that we’ve noticed that the NXP HDMI driver is picky when it comes to custom display timings (sometimes refuses to set the clock).
So if you are experiencing any issue with HDMI, please try entering the following commands in U-Boot in order to force the use of standard timings:
=> setenv cmd_custom 'setenv bootargs $bootargs drm_kms_helper.edid_firmware=HDMI-A-1:edid/1280x720.bin' => saveenv
In order to test the GPU, you can either use the standard Weston EGL programs or the ones provided by Vivante.
Here are a few examples:
root@nitrogen8m:~# weston-simple-egl & root@nitrogen8m:~# cd /opt/viv_samples/vdk/ root@nitrogen8m:/opt/viv_samples/vdk# ./tutorial7
The i.MX8MQ processor can decode videos with a resolution up to 4K so here is an example using GPlay tool:
root@nitrogen8m:~# wget http://linode.boundarydevices.com/videos/SKYFALL-4K.mp4 root@nitrogen8m:~# gplay-1.0 SKYFALL-4K.mp4
Camera MIPI-CSI input can be checked using our OV5640 MIPI with GStreamer:
root@nitrogen8m:~# gst-launch-1.0 v4l2src device=/dev/video0 ! video/x-raw,width=1280,height=720 ! glimagesink
eth0 interface is up, you can use
iperf3 to check Ethernet performances:
root@nitrogen8m:~# iperf3 -c 192.168.1.60 Connecting to host 192.168.1.60, port 5201 [ 5] local 192.168.1.13 port 32880 connected to 192.168.1.60 port 5201 [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 1.09 GBytes 938 Mbits/sec 0 sender [ 5] 0.00-10.04 sec 1.09 GBytes 932 Mbits/sec receiver
Same goes for the Wi-Fi that can be tested just as easily:
root@nitrogen8m:~# nmcli d wifi connect password root@nitrogen8m:~# iw wlan0 link Connected to a4:3e:51:08:54:f6 (on wlan0) SSID: Jabu_5GHz freq: 5240 RX: 3243 bytes (31 packets) TX: 9117 bytes (48 packets) signal: -79 dBm tx bitrate: 15.0 MBit/s MCS 0 40MHz short GI root@nitrogen8m:~# ping google.com -Iwlan0 PING google.com (220.127.116.11): 56 data bytes 64 bytes from 18.104.22.168: seq=0 ttl=55 time=3.470 ms ...
For products with Bluetooth, you’ll be able to connect using these commands:
root@nitrogen8m:~# hciconfig hci0 up root@nitrogen8m:~# hcitool scan Scanning ... 11:22:DE:AD:BE:EF Some Device
As usual, feel free to leave a comment below to share your experience.