Continuing with the OTA blog series part one and part two, this article shows you how to deploy OTA Connect using the OTA Community Edition into Google’s Kubernetes Engine (GKE). After completion of these instructions, you’ll have an OTA Connect server available on the internet with a single QEMU device registered to it.
One of the first big decisions we had to make for the Linux microPlatform was our Over-The-Air Update (OTA) strategy. This decision required a lot of time, meetings, beer, and coffee. This article is the first of a small series explaining our recommended approach to OTA for the LMP. This article explains how and why we ultimately chose OTA Connect and its open source deployment project OTA Community Edition.
In this blog we describe how to use the Zephyr microPlatform and the in-tree Zephyr samples to build, flash and perform an over the air (OTA) update of a Zephyr application over Bluetooth Low Energy (BLE). This demonstration uses the DFU support within Zephyr provided by mcumgr.
OMA Lightweight M2M (LWM2M) offers a firmware object interface for directing client devices to download and apply firmware updates. Using the Zephyr microPlaform and Eclipse’s Leshan Demo Server, this seemingly complex process can be demonstrated in a few easy steps.
To illustrate how a firmware update is delivered via LwM2M, you will make a small change to the Zephyr microPlatform (ZMP) LwM2M sample project which disables the Light Control object. When flashed to an embedded device, the Leshan UI will be missing the “Light Control” portion near the bottom of the client detail page. Once this “bug” is found, you will fix the LwM2M sample, recompile and deliver your updated firmware as an over the air (OTA) update. The new firmware can be confirmed by locating the “Light Control” object in the Leshan UI.