BeaglePlay

Board Integrations Yocto Project
1

Board description

Linux computing made simple and fun with 1,000s of available off-the-shelf sensors, actuators, indicators and connectivity options over mikroBUS, Grove, and QWIIC connections, a TI Sitara AM625 system-on-chip with 1.4GHz quad-core Arm Cortex-A53, PRU and M4 microcontrollers, Gigabit Ethernet, full-size HDMI, USB, 5GHz, 2.4GHz and sub-1GHz wireless, and single-pair Ethernet with power-over-data-line. Camera and touchscreen display ribbon-cable connectors also included.

No breadboarding expertise needed to expand this system, just connect, power, and leverage the massive ecosystem of Linux drivers. Want a remote sensor? Utilize BeagleConnect® technology over the sub-1GHz IEEE 802.15.4 wireless network to a BeagleConnect® Freedom up to 1km away.

beagleplay
beagleplay1522Ă—1626 301 KB

URL: BeaglePlay

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
kirkstone (4.0) :test_works: 1 :test_works:

1. the .sdimg.bmap image type seems to produce buggy results, using the .sdimg artifact directly is required.

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="kirkstone"

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

mkdir mender-beagleplay && cd mender-beagleplay

Initialize repo manifest:

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

Fetch layers in manifest:

repo sync

Setup build environment

Initialize the build environment:

source setup-environment ti

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

Building the image

You can now proceed with building an image:

MACHINE=beagleplay 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 placed in tmp/deploy/images/beagleplay/.

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 standalone mode.

References

  • The official Mender documentation explains how Mender works. This is simply a board-specific complement to the official documentation.
  • The integration template is maintainted in the meta-mender-community repository.

Known issues

  • .sdimg.bmap support seems to be causing partition corruption. Use the .sdimg image directly, eventually after unpacking from .sdimg.bz2
1 Like