# Booting Solidrun ClearFog Base from eMMC

**URL:** <https://hub.mender.io/t/booting-solidrun-clearfog-base-from-emmc/933>\
**Category:** General Discussions\
**Created:** [June 28, 2019, 6:27pm UTC](https://hub.mender.io/t/booting-solidrun-clearfog-base-from-emmc/933 "2019-06-28T18:27:57Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![henzigen](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/henzigen/32/286_2.png) [@henzigen](https://hub.mender.io/u/henzigen)\
**Post date:** [June 28, 2019, 6:27pm UTC](https://hub.mender.io/t/booting-solidrun-clearfog-base-from-emmc/933/1 "2019-06-28T18:27:57Z")

</div>

Hi Mirzak,

I wasn’t able to get this to run on the eMMC or when booting from USB on ClearFog Base. I have been able to boot the Debian image successfully from the eMMC. Have you tested the images produced and have been able to boot? I should also say I didn’t modify the recipes other than activating hosted mender and putting in my token.

---

<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:** [June 28, 2019, 6:36pm UTC](https://hub.mender.io/t/booting-solidrun-clearfog-base-from-emmc/933/2 "2019-06-28T18:36:30Z")

</div>

Hi @henzigen,

No this was never tested using eMMC as I did not have an eMMC module when I did this integration. This has only been tested using SD as boot medium. I should probably have put a note on this in the tutorial.

With that said it might work with eMMC, if you add the following in e.g `local.conf`:

```
 MENDER_STORAGE_DEVICE = "/dev/mmcblk1" 

```

As I assume `mmcblk0`is the SD card.

---

<div class="post-metadata">

**Author:** ![henzigen](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/henzigen/32/286_2.png) [@henzigen](https://hub.mender.io/u/henzigen)\
**Post date:** [June 28, 2019, 6:51pm UTC](https://hub.mender.io/t/booting-solidrun-clearfog-base-from-emmc/933/3 "2019-06-28T18:51:24Z")

</div>

Thanks for the quick reply. The eMMC is actually mmcblk0 if you order the eMMC version and the sdcard slot is disabled. It’s one or the other.

So I followed the guide [here](https://developer.solid-run.com/knowledge-base/a388-debian/) but instead replacing the debian image with the image built with yocto. The eMMC has two boot partitions, and a data partition. The guide provides a u-boot-mmc to dd onto boot partition 0 and then set the eMMC to boot from there. When I did that, it failed to boot but interestingly enough it did have some messages regarding mender-setup not being defined. I also tried to set the eMMC to boot directly from the data partition because I see that /dev/mmcblk0 ends up having 4 partitions (boot, data, primary, secondary) but that fails completely. No boot messages at all. I was thinking of dd’ing the /dev/mmcblk0p1 onto the eMMC boot parition 0. Do you think that would work?

---

<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:** [June 28, 2019, 7:00pm UTC](https://hub.mender.io/t/booting-solidrun-clearfog-base-from-emmc/933/4 "2019-06-28T19:00:57Z")

</div>

> [@SolidRun ClearFog Base](https://hub.mender.io/t/solidrun-clearfog-base/370/7):
>
> When I did that, it failed to boot but interestingly enough it did have some messages regarding mender-setup not being defined

This probably means that you did not get the correct U-boot binary flashed as it is trying to execute the following,

> <https://github.com/mendersoftware/meta-mender-community/blob/thud/meta-mender-clearfog/recipes-bsp/clearfog-u-boot-scr/files/boot.cmd.in>

But it wont be that easy and this probably requires some additional integration work. If i recall correctly, they have different U-boot configuration depending on where you will load it from, so you need to adjust this,

> <https://github.com/mirzak/meta-clearfog/blob/master/conf/machine/include/clearfog-common.inc#L8-L18>

Also the `sdimg` can not have an embedded U-boot for eMMC so you would need to manually write it after you have flashed the `sdimg`, and this is the command according to Solidrun docs that you execute on a running system to flash U-boot,

```
  echo 0 | sudo tee /sys/block/mmcblk0boot0/force_ro
  sudo dd if=u-boot-spl-mmc.kwb of=/dev/mmcblk0boot0 conv=sync

```

---

<div class="post-metadata">

**Author:** ![henzigen](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/henzigen/32/286_2.png) [@henzigen](https://hub.mender.io/u/henzigen)\
**Post date:** [June 28, 2019, 7:28pm UTC](https://hub.mender.io/t/booting-solidrun-clearfog-base-from-emmc/933/5 "2019-06-28T19:28:07Z")

</div>

Mirzak, you’re amazing. That did it. I added UBOOT\_BINARY = “u-boot-spl-mmc.kwb” and ran bitbake. It produced “u-boot-spl-mmc.kwb”. I flashed that to boot 0 parition of eMMC and it worked perfectly. The device popped up on my hosted mender. Thank you so much for your help.

---

<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 1, 2019, 7:30am UTC](https://hub.mender.io/t/booting-solidrun-clearfog-base-from-emmc/933/6 "2019-07-01T07:30:32Z")

</div>

Glad it worked out for you.
