Microchip SAMA5d27-SOM1-EK1

atmel
sama5
microchip
sumo
thud
yocto

#1

Board description

The SAMA5D27-SOM1-EK1 is a fast prototyping and evaluation platform for the SAMA5D2 based System in Packages (SiPs) and the SAMA5D27-SOM1 (SAMA5D27 System On Module). The kit comprises a baseboard with a soldered ATSAMA5D27-SOM1 module. The module features an ATSAMA5D27C-D1G-CU SIP embedding a 1-Gbit (128 MB) DDR2 DRAM

URL: https://www.microchip.com/developmenttools/ProductDetails/atsama5d27-som1-ek1

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
sumo (2.5) :test_works: :test_works:
thud (2.6) :test_works: :test_works:

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 .

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-atmel setup to live in and clone the
meta information.

mkdir mender-atmel && cd mender-atmel

Initialize repo manifest:

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

Fetch layers in manifest:

repo sync

Next, initialize the build environment:

source setup-environment atmel

Building the image

You can now proceed with building an image:

MACHINE=sama5d27-som1-ek-sd bitbake core-image-base

Replace core-image-base with your desired image target.

Using the build output

  • tmp/deploy/images/sama5d27-som1-ek-sd/core-image-base-sama5d27-som1-ek-sd.sdimg
  • tmp/deploy/images/sama5d27-som1-ek-sd/core-image-base-sama5d27-som1-ek-sd.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 as described in Deploy to physical devices or by using the Mender client only in Standalone deployments.

References

  • The official Mender documentation explains how Mender works. This is simply a board-specific complement to the official documentation.

#2

@texierp cool thanks for sharing.