# Microchip SAMA5d27-SOM1-EK1
**URL:** https://hub.mender.io/t/microchip-sama5d27-som1-ek1/127
**Category:** Yocto Project
**Tags:** yocto, sumo, atmel, sama5, microchip, thud, mender-convert, dunfell
**Created:** [November 6, 2018, 7:22pm UTC](https://hub.mender.io/t/microchip-sama5d27-som1-ek1/127 "2018-11-06T19:22:46Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@texierp](https://hub.mender.io/u/texierp)
#### Post date: [November 6, 2018, 7:22pm UTC](https://hub.mender.io/t/microchip-sama5d27-som1-ek1/127/1 "2018-11-06T19:22:46Z")
The official [Mender documentation](https://docs.mender.io/) explains how Mender works. This is a board-specific complement to the official documentation.
# 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: [Dynamic Dev Tool Page 2025 | Microchip Technology](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](https://wiki.yoctoproject.org/wiki/Releases?target=_blank):
| Yocto Project | Build | Runtime |
| --- | --- | --- |
| sumo (2.5) | :test_works: | :test_works: |
| thud (2.6) | :test_works: | :test_works: |
| warrior (2.7) | :test_works: | :test_works: |
| zeus (3.0) | :test_works: | :test_works: |
| dunfell (3.1) | :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/system-updates-yocto-project/board-integration/bootloader-support/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="dunfell"
```
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=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](https://docs.mender.io/system-updates-yocto-project/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/overview/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](https://docs.mender.io/artifact-creation/standalone-deployment).
# References
- The sources of the Yocto integration can be found in [meta-mender-community/meta-mender-atmel](https://github.com/mendersoftware/meta-mender-community/tree/dunfell/meta-mender-atmel)
* * *
_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!_
---
### Author:  [@MarekBelisko](https://hub.mender.io/u/MarekBelisko)
#### Post date: [November 7, 2018, 12:47pm UTC](https://hub.mender.io/t/microchip-sama5d27-som1-ek1/127/2 "2018-11-07T12:47:47Z")
@texierp cool thanks for sharing.
---
### Author:  [@mirzak](https://hub.mender.io/u/mirzak)
#### Post date: [September 18, 2019, 6:49am UTC](https://hub.mender.io/t/microchip-sama5d27-som1-ek1/127/3 "2019-09-18T06:49:35Z")
2 posts were split to a new topic: [Issue adding python on SAMA5d27-SOM1-EK1](https://hub.mender.io/t/issue-adding-python-on-sama5d27-som1-ek1/1032)
---
### Author:  [@mirzak](https://hub.mender.io/u/mirzak)
#### Post date: [August 13, 2020, 12:02pm UTC](https://hub.mender.io/t/microchip-sama5d27-som1-ek1/127/7 "2020-08-13T12:02:02Z")
10 posts were split to a new topic: [Boot from MMC1 on Microchip SAMA5d27-SOM1-EK1](https://hub.mender.io/t/boot-from-mmc1-on-microchip-sama5d27-som1-ek1/2314)
---
### Author:  [@martind](https://hub.mender.io/u/martind)
#### Post date: [January 15, 2021, 6:11pm UTC](https://hub.mender.io/t/microchip-sama5d27-som1-ek1/127/8 "2021-01-15T18:11:51Z")
Hi,
Mircochip has another version of the SAMA5d27 that includes Wifi and Bluetooth [SAMA5D27WLSOM1](https://www.linux4sam.org/bin/view/Linux4SAM/Sama5d27WLSom1EKMainPage#Kit_Information). If I wanted to try our mender on this EK what is involved to convert the steps from this board integration? I’m just trying to understand the level of effort involved.
Thanks!