The official Mender documentation explains how Mender works. This is simply a board-specific complement to the official documentation.
Device description
It’s an open-source single-board computer. It can run Android 4.4, Ubuntu, Debian. It uses the AllWinner H2 SoC, and has 256MB/512MB DDR3 SDRAM(256MB version is Standard version)
URL: http://www.orangepi.org/orangepizero/
Wiki: : http://www.orangepi.org/Docs/mainpage.html
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 |
|---|---|---|
| dunfell (3.1) |  |
|
| zeus (3.0) | |
|
| thud (2.6) | |
1
|
| sumo (2.5) | |
|
1. Disabled GRUB integration for ARM systems which is default in meta-mender/thud. U-boot is still primary integration method for this platform.
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
Prerequisites
- 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-orangepi setup to live in and clone the
meta information.
mkdir mender-orangepi && cd mender-orangepi
Initialize repo manifest:
repo init -u https://github.com/mendersoftware/meta-mender-community \
-m meta-mender-sunxi/scripts/manifest-sunxi.xml \
-b ${BRANCH}
Fetch layers in manifest:
repo sync
Setup build environment
Initialize the build environment:
source setup-environment sunxi
Building the image
You can now proceed with building an image:
MACHINE=orange-pi-zero 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:
tmp/deploy/images/orange-pi-zero/core-image-base-orange-pi-zero.sdimgtmp/deploy/images/orange-pi-zero/core-image-base-orange-pi-zero.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 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 (upload it under Releases in the server UI) or by using the Mender client only in Standalone deployments.
References
- The Mender integration layer for OrangePi PC Plus and template files can be found in meta-mender-community.
Known issues
- The default Linux kernel image format (
uImage) set in meta-sunxi for OrangePi PC Plus does not boot, this might apply to other boards as well. Therefore there is an entrylocal.confthat changes the Linux kernel image format tozImage
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!
