MinnowBoard Turbot



Board description

The MinnowBoard Turbot is an open source hardware Single Board Computer based on a 64-bit Intel® Atom™ E38xx Series System on a Chip (SoC), with dual- and quad-core versions. It is a software-compatible descendant of the MinnowBoard MAX.


Web: https://minnowboard.org/minnowboard-turbot/technical-specs

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:

Yocto Project Build Runtime
thud (2.6) :test_works: :test_fails: 1
sumo (2.5) :test_works: :test_works:

1. Outputs boot error and drops to systemd maintenance mode. Once exiting maintenance mode the board boots correctly.

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 has been verified.

Getting started


  • A supported Linux distribution and dependencies installed on your workstation/laptop as described in the Yocto Mega Manual
    • NOTE. Instructions depend on which Yocto version you intend to use.
  • Google repo tool installed and in your PATH .

Configuring the build

Setup Yocto environment

Set the Yocto Project branch you are building for:

# set to your branch, make sure it is supported (see table above)
export BRANCH="sumo" 

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

mkdir mender-minnowboard && cd mender-minnowboard

Initialize repo manifest:

repo init -u https://github.com/mendersoftware/meta-mender-community \
           -m meta-mender-intel/scripts/manifest-intel.xml \
           -b ${BRANCH}

Fetch layers in manifest:

repo sync

Setup build environment

Initialize the build environment:

source setup-environment intel

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, 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:

# 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>"

Build for Mender demo server:

# https://docs.mender.io/getting-started/create-a-test-environment
# Update IP address to match the machine running the Mender demo server

Building the image

You can now proceed with building an image:

MACHINE=intel-corei7-64 bitbake core-image-full-cmdline

Replace core-image-full-cmdline with your desired image target.

Using the build output

After a successful build, the images and build artifacts are:

  • tmp/deploy/images/intel-corei7-64/core-image-full-cmdline-intel-corei7-64.uefiimg
  • tmp/deploy/images/intel-corei7-64/core-image-full-cmdline-intel-corei7-64.mender

The disk image (with .uefiimg 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 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 files, which have .mender suffix. You can either deploy this Artifact in managed mode with the Mender server as described in Deploy to physical devices or by using the Mender client only in Standalone deployments.

Booting from SD card

If you are writing the disk image to a SD card, you need to update the Minnowboard’s BIOS settings to boot from it. You need to have a keyboard and monitor attached when booting the first time in order to change the boot settings. This can be achieved with a serial cable or by plugging in a USB keyboard and monitor directly into the board.

Insert the SD card into the Minnowboard, and connect power. Press F2 immediately during boot to enter Setup.

In the BIOS menu, select Boot Maintenance Manager -> Boot Options -> Change Boot Order. Then go to the boot order listing and press Enter.

Use the down arrow to Select “Misc Device” and use + to move it to the top.

Then press F10 and Y to save selection and ESC three times followed by Continue to reboot the board with these new settings. All following boots should now boot from the SD card.

Create Mender Artifacts to control LED blinking (optional)

Now that we have the device provisioned and connected to the Mender server, we can build some updates to deploy. The most common place to start is with the blinkenlights!

Note that to make testing easier, we will use the meta-mender-demo layer. If you did not include this layer above, you need to adjust the steps below.

The meta-mender-demo layer already comes with a script that is configured to run at boot, called bootscript.sh. By default it is a no-op script, so we will simply overwrite this script with our code to blink the MinnowBoard LED.

Build an Artifact to blink the LED slowly

This section assumes that you have setup the Yocto environment and that you are located in the build/ directory.

cat << "EOF" > ../sources/meta-mender/meta-mender-demo/recipes-mender/boot-script/files/boot-script.sh

# Blink the D2 LED on a MinnowBoard Turbot board
# D2 LED is GPIO 360
# Tell the system we'll be using the GPIO for the D2 LED
if [ ! -d /sys/class/gpio/gpio$LED2 ]; then
        echo $LED2 > /sys/class/gpio/export
# and we'll be using it for Output (out) and not Input (in)
echo out > /sys/class/gpio/gpio$LED2/direction
# alternate writing a 0 (ON) and 1 (OFF) every second, until interrupted
while true ; do
        echo $i > /sys/class/gpio/gpio$LED2/value
        sleep 2

Open conf/local.conf and change MENDER_ARTIFACT_NAME to blinkslow:


Then build an Artifact that will blink the LED slowly:

bitbake core-image-full-cmdline

The build should finish within 5-10 minutes. After it finishes, copy the generated Artifact to save it for later and name it blinkslow:

cp tmp/deploy/images/intel-corei7-64/core-image-full-cmdline-intel-corei7-64.mender ~/core-image-full-cmdline-intel-corei7-64-blinkslow.mender

Build an Artifact to blink the LED fast

To switch between blinking fast and slow using Mender, we build another Artifact, one that blinks faster.

Open ../sources/meta-mender/meta-mender-demo/recipes-mender/boot-script/files/boot-script.sh and change line 16 from sleep 2 to sleep 0.2:

sleep 0.2

Then open conf/local.conf and change MENDER_ARTIFACT_NAME to blinkfast:


Then build an Artifact that will blink the LED fast:

bitbake core-image-full-cmdline

The build should finish within 5-10 minutes. After it finishes, copy the generated Artifact to save it for later and name it blinkfast:

cp tmp/deploy/images/intel-corei7-64/core-image-full-cmdline-intel-corei7-64.mender ~/core-image-full-cmdline-intel-corei7-64-blinkfast.mender

Deploy the blinkenlights updates

Upload the two Artifacts (blinkslow and blinkfast) to your Mender server.

Deploy them to the Minnowboard. This will typically take 5-6 minutes, depending on your network speed.

After deploying them you should see the LED2 light blink fast or slow, depending on which Artifact you deployed!