# SolidRun ClearFog Base **URL:** \ **Category:** Yocto Project\ **Tags:** yocto, thud\ **Created:** [March 18, 2019, 9:42am UTC](https://hub.mender.io/t/solidrun-clearfog-base/370 "2019-03-18T09:42:54Z")\ **Posts on this page:** 8\ **Page:** 1
**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:** [March 18, 2019, 9:42am UTC](https://hub.mender.io/t/solidrun-clearfog-base/370/1 "2019-03-18T09:42:54Z")
The official [Mender documentation](https://docs.mender.io/) explains how Mender works. This is simply a board-specific complement to the official documentation. # Board description ClearFog Base SBC is equipped with numerous I/O options, and is compatible with a variety of power, memory and storage configurations. Device makers can easily bridge a variety of different network standards like LAN, Wi-Fi, Cellular, Fiber and DSL, as well as utilize mikroBUS boards for IoT type networking standards such as ZigBee, Sub GHz, Bluetooth and others. ![clearfog-base-with-som-01-300x300](https://canada1.discourse-cdn.com/flex036/uploads/mender/original/1X/643dddd2de490c3a21ab82b13e79e237725d8754.jpeg) URL: [https://www.solid-run.com/marvell-armada-family/clearfog/](https://www.solid-run.com/marvell-armada-family/clearfog/) Wiki: [https://developer.solid-run.com/](https://developer.solid-run.com/) # 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/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`. ## Configuring the build ### 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-clearfog` setup to live in and clone the meta information. ```auto mkdir mender-clearfog && cd mender-clearfog ``` Initialize repo manifest: ```auto repo init -u https://github.com/mendersoftware/meta-mender-community \ -m meta-mender-clearfog/scripts/manifest-clearfog.xml \ -b ${BRANCH} ``` Fetch layers in manifest: ```auto repo sync ``` ## Setup build environment Initialize the build environment: ```auto source setup-environment clearfog ``` ### Configure Mender server URL (optional) This section is not required for a successful build but images that are generated by default are only suitable for usage with the Mender client in [standalone mode](https://docs.mender.io/artifact-creation/standalone-deployment), due to lack of server configuration. You can edit the `conf/local.conf` file to provide your Mender server configuration, ensuring the generated images and Mender Artifacts are connecting to the Mender server that you are using. There should already be a commented section in the generated `conf/local.conf` file and you can simply uncomment the relevant configuration options and assign appropriate values to them. Build for Hosted Mender: ```auto # To get your tenant token: # - log in to https://hosted.mender.io # - click your email at the top right and then "My organization" # - press the "COPY TO CLIPBOARD" # - assign content of clipboard to MENDER_TENANT_TOKEN # MENDER_SERVER_URL = "https://hosted.mender.io" MENDER_TENANT_TOKEN = "" ``` ### Building the image You can now proceed with building an image: ```auto MACHINE=clearfog-base bitbake core-image-base ``` Replace `core-image-base` with your desired image target. ### Using the build output **Note!** The default configuration is booting from a SD card After a successful build, the images and build artifacts are placed in `tmp/deploy/images/clearfog-base/`. - `tmp/deploy/images/clearfog-base/core-image-base-clearfog-base.sdimg` - `tmp/deploy/images/clearfog-base/core-image-base-clearfog-base.mender` - `tmp/deploy/images/clearfog-base/u-boot-spl-sdhc.kwb` The disk image with `.sdimg` 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. The `u-boot-spl-sdhc.kwb` file is used to provision the device with a Mender compatible U-Boot. 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). ### Boot medium configuration and flashing instructions Depending on which medium you intend to boot from you need to adjust the `UBOOT_BINARY` variable, please take a look in below link for further information: > Flashing instructions depend-on which boot medium was choosen and you can find more information in the Solidrun documentation, [https://developer.solid-run.com/knowledge-base/a388-u-boot/#installing-manually](https://developer.solid-run.com/knowledge-base/a388-u-boot/#installing-manually) # Known issues SolidRun does not provide an official Yocto BSP for the ClearFog Base boards and this integration is based on a layer that I have created which can be found here: - [https://github.com/mirzak/meta-clearfog](https://github.com/mirzak/meta-clearfog) I am on the lookout to find a better location for above code. * * * _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:** ![ramu](https://avatars.discourse-cdn.com/v4/letter/r/e95f7d/32.png) [@ramu](https://hub.mender.io/u/ramu)\ **Post date:** [April 2, 2019, 10:42am UTC](https://hub.mender.io/t/solidrun-clearfog-base/370/2 "2019-04-02T10:42:18Z")
Hi Mirzak, I am using Solidrun imx6 board and I have built image using your manifest-clearfog.xml and generated .sdimg. But Board unable to boot… Dont know whether its because of difference between your integration meant for solidrun clearfog base and my board is solidrun imx6… Any suggestions from you…? ---
**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:** [April 2, 2019, 11:04am UTC](https://hub.mender.io/t/solidrun-clearfog-base/370/3 "2019-04-02T11:04:46Z")
This is only for the ClearFog Base board which is based on Marvell SoC, and will not work on Solidrun i.MX6 based devices. ---
**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:** [April 2, 2019, 12:53pm UTC](https://hub.mender.io/t/solidrun-clearfog-base/370/4 "2019-04-02T12:53:45Z")
A post was split to a new topic: [Solidrun i.MX6 integration errors](https://hub.mender.io/t/solidrun-i-mx6-integration-errors/439) ---
**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:** [August 15, 2019, 8:45am UTC](https://hub.mender.io/t/solidrun-clearfog-base/370/5 "2019-08-15T08:45:17Z")
6 posts were split to a new topic: [Booting Solidrun ClearFog Base from eMMC](https://hub.mender.io/t/booting-solidrun-clearfog-base-from-emmc/933) ---
**Author:** ![Valks](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/valks/32/321_2.png) [@Valks](https://hub.mender.io/u/Valks)\ **Post date:** [September 16, 2019, 9:11am UTC](https://hub.mender.io/t/solidrun-clearfog-base/370/6 "2019-09-16T09:11:54Z")
Well it looks like SolidRun are now maintaining a layer to support the clearfog boards (based on yocto: warrior). I wish they did it a little earlier but at least there’s something 🙂 > **[SolidRun/meta-clearfog](https://github.com/SolidRun/meta-clearfog)** > > Yocto meta layer for SolidRun Clearfog platforms. Contribute to SolidRun/meta-clearfog development by creating an account on GitHub. Supports Clearfog-base, Clearfog-Pro and Clearfog-GTR ---
**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:** [September 16, 2019, 9:15am UTC](https://hub.mender.io/t/solidrun-clearfog-base/370/7 "2019-09-16T09:15:41Z")
Shame, I reached out to them way back but never got any response of their intentions, > > > Hi, > I am a bit curious what the intentions with this layer is? I recently had the opportunity to work with a... ---
**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:** [December 17, 2019, 6:00pm UTC](https://hub.mender.io/t/solidrun-clearfog-base/370/8 "2019-12-17T18:00:35Z")
## Summary I have ran into a new issue with this board and the mender service. The issue seems to be isolated to the mender service and how the daemon works. It seems if one of the network interfaces is connected but does not have access to public internet, meaning it cannot connect to the mender server, then the mender service cannot poll for update or update inventory even if the another network interface is connected. If however, I bring down the isolated interface and restart the mender service, then it works fine. Furthermore, if I bring the isolated interface backup after it is already connected, then everything works fine as well. ## Steps to reproduce 1. Connect interface ‘eth0’ (leftmost) to a network with public access / connectivity to the mender server. 2. Connect interface ‘eth1’ to a network with no public access / no connectivity to the mender server. ## What is the current bug behavior? The device is unable to connect to the mender server to update inventory or poll for updates. ## What is the expected correct behavior? The device should be able to connect to the mender server through interface ‘eth0’. ## Systemd Mender Service `Dec 17 17:25:30 ipessentials systemd[1]: Started Mender OTA update service. Dec 17 17:25:30 ipessentials mender[2424]: time="2019-12-17T17:25:30Z" level=info msg="Configuration file does not exist: /var/lib/mender/mender.conf" module=config Dec 17 17:25:30 ipessentials mender[2424]: time="2019-12-17T17:25:30Z" level=info msg="Loaded configuration file: /etc/mender/mender.conf" module=config Dec 17 17:25:30 ipessentials mender[2424]: time="2019-12-17T17:25:30Z" level=info msg="Mender running on partition: /dev/mmcblk0p2" module=main Dec 17 17:25:30 ipessentials mender[2424]: time="2019-12-17T17:25:30Z" level=info msg="State transition: init [none] -> init [none]" module=mender Dec 17 17:25:30 ipessentials mender[2424]: time="2019-12-17T17:25:30Z" level=info msg="State transition: init [none] -> idle [Idle]" module=mender Dec 17 17:25:30 ipessentials mender[2424]: time="2019-12-17T17:25:30Z" level=info msg="authorization data present and valid" module=mender Dec 17 17:25:30 ipessentials mender[2424]: time="2019-12-17T17:25:30Z" level=info msg="State transition: idle [Idle] -> check-wait [Idle]" module=mender Dec 17 17:25:30 ipessentials mender[2424]: time="2019-12-17T17:25:30Z" level=info msg="State transition: check-wait [Idle] -> inventory-update [Sync]" module=mender Dec 17 17:27:40 ipessentials mender[2424]: time="2019-12-17T17:27:40Z" level=error msg="failed to submit inventory data: Patch https://hosted.mender.io/api/devices/v1/inventory/device/attributes: dial tcp 34.196.11.110:443: connect: network is unreachable" module="client_inventory" Dec 17 17:27:40 ipessentials mender[2424]: time="2019-12-17T17:27:40Z" level=warning msg="failed to refresh inventory: failed to submit inventory data: inventory submit failed: Patch https://hosted.mender.io/api/devices/v1/inventory/device/attributes: dial tcp 34.196.11.110:443: connect: network is unreachable" module=state `