How embedded Linux accelerates IoT development
How embedded Linux accelerates IoT development
You'll find that the quickest way to build components of an IoT ecosystem is to use embedded Linux, whether you're augmenting existing devices or designing a new device or system from the beginning. Embedded Linux shares the same source code base as desktop Linux, but it is coupled with different user interface tools and other high-level components. The base of the system is essentially the same.
Let's look at a few common cases.
Often, extremely low-power applications, such as sensors, run for months at a time on disposable cells or even on energy harvesting applications. Any usage of Linux may seem to be rather heavy. The low-power nature often precludes direct IP connectivity. This implies a gateway for Internet connectivity. A gateway would speak the low-power protocol to the sensors and would translate them to IP. Depending on the protocol, Linux may have existing protocol support or something similar enough to leverage.
Consider an outdoor thermometer with a wireless link running from a CR2032 coin cell or a "smart light bulb." A smart light bulb may not appear to be a low-power application, depending on its approach to handling things in the off state. A pure Linux approach where it sleeps when off could mean you'd have a boot time issue (most users would not be willing to wait 10 to 20 seconds for a light bulb to turn on for the first time).
If either of these were to run some flavor of IEEE 802.11 ("Wi-Fi") directly, battery life would be extremely limited. Similarly, bulb-off power usage would be considerably higher than a normal bulb. (A smart light bulb typically allows the user to switch it on via the Internet from the off state.) Instead, they can use a bulb designed for low-power protocol, such as a simple 2.4GHz signaling system or Bluetooth Low Energy to maintain the low-power aspect. An embedded Linux gateway translates the low-power wireless link to Wi-Fi or even Ethernet for Internet connectivity. A Linux-based gateway along with a low-power wireless protocol is exactly what you see on numerous devices on the market today.
Another common case is a fresh design. Embedded Linux is already found in many non-IoT devices today. A common dilemma for designers is choosing between a bare metal/RTOS (Real-Time Operating System) approach versus using a Linux on a SoC (System on a Chip), which is an integrated circuit that incorporates all of a computer's components. A bare metal option can appear at first to have a lower BOM (Bill of Materials) cost, but that ignores common issues, such as time to market, development costs, and support costs. Embedded Linux can be quicker to turn around and a larger user base can mean lower development costs in terms of available resources, including qualified engineers and development tools, such as those that allow you to simulate aspects of your projects. A large Linux user base can augment test coverage and simplify support issues.
A main requirement for an IoT device is connectivity, usually in the form of IP. Often this is via a web server. Bare metal/RTOS can offer IP connectivity, but unless you scrutinize it carefully you run the risk of buggy and potentially substandard IP implementations. For example, many RTOSs do not isolate the IP stack user from the IP stack itself. Internet connectivity can require potentially dealing with low speed or congested links. This can translate into obscure and hard-to-debug buffer handling issues when the stack is intermingled with other code. In contrast, an embedded Linux implementation leverages hardware separation and a widely utilized IP stack that probably has been exposed to corner cases. If you consider this and other risks associated with bare metal/RTOS implementation, you can quickly offset the minimal added BOM cost of Linux with a quicker time to market, lower support and development costs, and widely available development resources.
Another common case is augmenting an existing design for IoT capabilities. This includes both nearly complete but still in development projects and upgrades to an existing product. The key issue is adding the IoT features. For discussion's sake, this means adding a read device status, configuration and control, or all, to a device with a web browser (like on a phone). This means you need an IP stack, a web server, and software glue on the device.
Security is an essential concern of retrofitting IoT connectivity to an embedded Linux device. This is applicable to both retrofitting and fresh designs. IoT services are often exposed to the dangerous, unfiltered Internet. A system compromise on the Internet interface can have consequences beyond giving an intruder information on the device or control of the device. However, exploring security issues further would easily add up to another article. You can leverage several native, embedded Linux features—multiuser, SELinux, and containers—to contain and limit the damage. This is on top of potential fixes shared by other parts of the Linux community.
These cases show how embedded Linux accelerates IoT development. Linux can future proof, simplify augmentation, and provide IP gateway services to the IoT ecosystem. The vast library of drivers and features within the Linux ecosystem along with the power of open source is a natural reservoir to draw from when building IoT projects.
Hunyue Yau will be speaking at SCALE 15x, delivering the talk: The Many IoT Roles of embedded Linux.