The official Mender documentation explains how Mender works. This is a board-specific complement to the official documentation.
Board description
The STM32MP157A-DK1 and STM32MP157C-DK2 Discovery kits leverage the capabilities of STM32MP1 Series microprocessors to allow users easily develop applications using STM32 MPU OpenSTLinux Distribution software for the main processor and STM32CubeMP1 software for the co-processor.
URL: https://www.st.com/en/evaluation-tools/stm32mp157c-dk2.html
Wiki: https://wiki.st.com/stm32mpu/wiki/OpenSTLinux_distribution
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) |  |
|
NOTE! This integration has only be tested using the SD card as boot medium and would require additional changes to support booting from e.g NAND or eMMC.
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="thud"
Create a directory for your mender-stm32mp setup to live in and clone the
meta information.
mkdir mender-stm32mp && cd mender-stm32mp
Initialize STM32 repo manifest:
repo init -u https://github.com/STMicroelectronics/oe-manifest.git -b ${BRANCH}
Fetch Mender amendments to manifest:
wget --directory-prefix .repo/manifests https://raw.githubusercontent.com/mendersoftware/meta-mender-community/${BRANCH}/meta-mender-st-stm32mp/scripts/stm32mp-mender.xml
Initialize stm32mp-mender.xml:
repo init -m stm32mp-mender.xml
Fetch layers in manifest:
repo sync
Setup build environment
Initialize the build environment:
. stm32mp-setup-mender.sh
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
MENDER_DEMO_HOST_IP_ADDRESS = "192.168.0.100"
Building the image
You can now proceed with building an image:
bitbake st-image-core
Replace st-image-core with your desired image target.
Using the build output
After a successful build, the images and build artifacts are placed in tmp/deploy/images/odroid-c2/.
tmp-glibc/deploy/images/stm32mp1-disco/st-image-core-stm32mp1-disco.gptimgtmp-glibc/deploy/images/stm32mp1-disco/st-image-core-stm32mp1-disco.mender
The disk image with .gptimg 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 sources of the Yocto integration can be found in meta-mender-community/meta-mender-st-stm32mp
Known issues
NOTE! This integration has only be tested using the SD card as boot medium and would require additional changes to support booting from e.g NAND or eMMC.
U-boot compile error
For some (not yet known) reason the U-Boot recipe can sporadically fail to compile. Clearing the cache typically resolves it by e.g running:
bitbake u-boot-fw-utils-mender-auto-provided -c cleansstate
bitbake u-boot -c cleansstate
bitbake u-boot
bitbake st-image-core
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!