# Microchip SAMA5D3 Xplained

**URL:** https://hub.mender.io/t/microchip-sama5d3-xplained/194
**Category:** Yocto Project
**Tags:** yocto, atmel, microchip, thud
**Created:** [February 1, 2019, 10:18pm UTC](https://hub.mender.io/t/microchip-sama5d3-xplained/194 "2019-02-01T22:18:54Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![jorisoffouga](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/jorisoffouga/32/64_2.png) [@jorisoffouga](https://hub.mender.io/u/jorisoffouga)
#### Post date: [February 1, 2019, 10:18pm UTC](https://hub.mender.io/t/microchip-sama5d3-xplained/194/1 "2019-02-01T22:18:55Z")

</div>

# 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.

![Screenshot%20at%202019-02-01%2023%3A09%3A27](https://canada1.discourse-cdn.com/flex036/uploads/mender/original/1X/b535d4bb6d96078fed9f2dff4d893febff135053.jpeg)

URL: [https://www.microchip.com/DevelopmentTools/ProductDetails/ATSAMA5D3-XPLD](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](https://wiki.yoctoproject.org/wiki/Releases?target=_blank):

| Yocto Project | Build | Runtime |
| --- | --- | --- |
| 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](https://docs.mender.io/devices/integrating-with-u-boot/integration-checklist?target=_blank) has been verified.

# Getting started

## Prerequisites

- A supported Linux distribution and dependencies installed on your workstation/laptop as described in the [Yocto Mega Manual](https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#detailed-supported-distros)
  - NOTE. Instructions depend on which Yocto version you intend to use.

- Google repo tool [installed](https://hub.mender.io/t/google-repo/58/2) and in your `PATH` .

### Setup Yocto environment

Set the Yocto Project branch you are building for:

```auto
# 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.

```auto
mkdir mender-atmel && cd mender-atmel

```

Initialize repo manifest:

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

```

Fetch layers in manifest:

```auto
repo sync

```

Next, initialize the build environment:

```bash
source setup-environment atmel

```

### Building the image

You can now proceed with building an image:

```auto
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.sdimg`
- `tmp/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](https://docs.mender.io/artifacts/provisioning-a-new-device?target=_blank) 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](https://docs.mender.io/architecture/mender-artifacts?target=_blank) 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](https://docs.mender.io/architecture/standalone-deployments?target=_blank).

# References

- The official [Mender documentation](https://docs.mender.io/) 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!_

---

<div class="post-metadata">

### Author: ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)
#### Post date: [July 31, 2020, 1:13pm UTC](https://hub.mender.io/t/microchip-sama5d3-xplained/194/2 "2020-07-31T13:13:16Z")

</div>

3 posts were split to a new topic: [ERROR: Actual rootfs size (21223 kB) is larger than allowed size 16384 kB](https://hub.mender.io/t/error-actual-rootfs-size-21223-kb-is-larger-than-allowed-size-16384-kb/2270)
