### Author:  [@andrewtimoshenko](https://hub.mender.io/u/andrewtimoshenko)
#### Post date: [October 16, 2019, 12:46pm UTC](https://hub.mender.io/t/boot-from-mmc1-on-microchip-sama5d27-som1-ek1/2314/6 "2019-10-16T12:46:20Z")
Hey guys,
@texierp @mirzak
Thanks a lot for your help.
If someone wants to boot sama5d27 and Mender from microSD, here is a brief manual:
1. Add to your local.conf file the line:
```auto
MENDER_STORAGE_DEVICE = "/dev/mmcblk1"
```
1. Add to meta-atmel/conf/machine/sama5d27-som1-ek-sd.conf for a at91bootstrap booting from MMC1:
```auto
AT91BOOTSTRAP_TARGET ?= "${AT91BOOTSTRAP_MACHINE}sd1_uboot_defconfig"
```
If you do not, at91bootstrap will still boot from MMC0.
1. Undefine CONFIG\_SYS\_MMC\_ENV\_DEV in the include/configs/at91-sama5\_common.h file of the u-boot-at91:
```auto
From b51c78c57b95d3074c819ab2257f16dafddaec8c Mon Sep 17 00:00:00 2001
From: andrewtimoshenko
Date: Wed, 16 Oct 2019 14:34:27 +0300
Subject: [PATCH] Booting from MMC1 microSD
---
include/configs/at91-sama5_common.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/configs/at91-sama5_common.h b/include/configs/at91-sama5_common.h
index fc46540a10..1af5dbc02d 100644
--- a/include/configs/at91-sama5_common.h
+++ b/include/configs/at91-sama5_common.h
@@ -41,6 +41,7 @@
#define CONFIG_ENV_OFFSET 0x2000
#define CONFIG_ENV_SIZE 0x1000
#define CONFIG_SYS_MMC_ENV_DEV 0
+#undef CONFIG_SYS_MMC_ENV_DEV
#else
/* u-boot env in sd/mmc card */
#define CONFIG_ENV_SIZE 0x4000
```
1. And keep on rocking 🙂
My build configuration:
```auto
BB_VERSION = "1.40.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "sama5d27-som1-ek-sd"
DISTRO = "poky-atmel"
DISTRO_VERSION = "2.6.3"
TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard cortexa5"
TARGET_FPU = "hard"
meta
meta-poky
meta-yocto-bsp = "HEAD:e6949336479e611a142834b6d9241514cbaeaf80"
meta-oe
meta-python
meta-networking = "thud:9b3b907f30b0d5b92d58c7e68289184fda733d3e"
meta-mender-atmel = "HEAD:c2f777bdccba7e8c281fdb520cde98b301ac7acd"
meta-mender-core
meta-mender-demo = "thud:352cd81fe4dd6e44ba0819da1d8e189109e805e6"
meta-iot-cloud = "feature/bsp_porting_RLPR-64:c4b12f6ca0ca5a5aa144c543a7464c921fb49efb"
meta-atmel = "thud:d6773b92ae0805d941493a2950fd167d7bdfff1b"
meta-qt5 = "thud:1520d5b2b2beec5e1c3209d3178219e93ef08bca"
```
---
### Author:  [@mirzak](https://hub.mender.io/u/mirzak)
#### Post date: [October 17, 2019, 6:19am UTC](https://hub.mender.io/t/boot-from-mmc1-on-microchip-sama5d27-som1-ek1/2314/7 "2019-10-17T06:19:24Z")
Thanks for sharing @andrewtimoshenko. Maybe this is something that can be integrated in to [https://github.com/mendersoftware/meta-mender-community/tree/thud/meta-mender-atmel](https://github.com/mendersoftware/meta-mender-community/tree/thud/meta-mender-atmel)
---
### Author:  [@andrewtimoshenko](https://hub.mender.io/u/andrewtimoshenko)
#### Post date: [October 23, 2019, 8:59am UTC](https://hub.mender.io/t/boot-from-mmc1-on-microchip-sama5d27-som1-ek1/2314/8 "2019-10-23T08:59:38Z")
Hi guys,
I want to add a new flexcom0 node for UART supporting to the device tree of at91-sama5d27\_som1\_ek board. I’ve described this node in the arch/arm/boot/dts/at91-sama5d27\_som1\_ek.dts file, but my changes are not included in the sdimage.
My flexcome0 UART node:
```auto
flx0: flexcom@f8034000 {
compatible = "atmel,sama5d2-flexcom";
reg = < 0xf8034000 0x200 >;
clocks = < 0x51 >;
#address-cells = < 0x01 >;
#size-cells = < 0x01 >;
ranges = < 0x00 0xf8034000 0x800 >;
status = "okay";
atmel,flexcom-mode = < 0x01 >;
phandle = < 0xaa >;
serial@200 {
compatible = "atmel,at91sam9260-usart";
reg = < 0x200 0x200 >;
interrupts = < 0x13 0x04 0x07 >;
clocks = < 0x51 >;
clock-names = "usart";
atmel,use-dma-rx;
atmel,use-dma-tx;
dmas = < 0x39 0xb004000 0x39 0xc004000 >;
dma-names = "tx\0rx";
pinctrl-names = "default";
pinctrl-0 = < 0x52 >;
atmel,fifo-size = < 0x20 >;
status = "okay";
phandle = < 0xab >;
};
```
Is there another way how to include new nodes to the device tree? Could you provide some examples for adding nodes with dt-overlay, perhaps it can be an alternative way for device tree editing?
---
### Author:  [@texierp](https://hub.mender.io/u/texierp)
#### Post date: [October 24, 2019, 9:35am UTC](https://hub.mender.io/t/boot-from-mmc1-on-microchip-sama5d27-som1-ek1/2314/9 "2019-10-24T09:35:12Z")
Hi @andrewtimoshenko,
It is not related to Mender, but anyway, in fact you have to create a patch into your meta layer to include this specific node in your DTS file.
It means a specific ‘bbappend’ of linux-at91 (like [this](https://github.com/MOVE-II/meta-cdh/commit/1553841126f0b4be8c838a76baeca6dc0346b029))
---
### Author:  [@andrewtimoshenko](https://hub.mender.io/u/andrewtimoshenko)
#### Post date: [October 24, 2019, 3:37pm UTC](https://hub.mender.io/t/boot-from-mmc1-on-microchip-sama5d27-som1-ek1/2314/10 "2019-10-24T15:37:24Z")
Thank you anyway @texierp .
Just needs to remember about the cleaning of kernel build directory periodically 🙂