Board description
The SAMA5D3 Xplained is a fast prototyping and evaluation platform for SAMA5D36 Cortex-A5 Microprocessor. The board comes with a rich set of ready to use connectivity with1x SD/eMMC and 1x MicroSD slots and expansions headers (Arduino DUE, 3.3v Uno R2 & R3, and Mega R3 shield) compatible for easy customization. A Linux distribution and software package gets you evaluating fast. A USB device connector can be used to power the board as well as programming and debugging it.
URL: https://www.microchip.com/DevelopmentTools/ProductDetails/ATSAMA5D3-XPLD
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) |  |
|
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=sama5d3-xplained-sd bitbake core-image-base
Replace core-image-base with your desired image target.
Using the build output
tmp/deploy/images/sama5d3-xplained-sd/core-image-base-sama5d3-xplained-sd.sdimgtmp/deploy/images/sama5d3-xplained/core-image-base-sama5d3-xplained-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 (upload it under Releases in the server UI) 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.
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!