Embedded Linux for Teams


A Linux kernel for each developer team, which uses it to bring up target boards. Bespoke, built, issued, and maintained over years by the vendor. Teams that focus on building great apps, rather than figuring out hardware dependencies. Happy developers that bootstrap smart devices in no time.

This is what highly productive embedded systems development should look like. Let’s unpack that vision.


Embedded systems developers can be as productive as web, desktop or mobile developers are. Most developers don’t have to worry about hardware dependencies like kernels, and BSPs, except for embedded software. 

Developers are in the business of building applications, not that of building and maintaining kernels and BSPs. building and maintaining hardware-dependent software artifacts is not the developers’ job to be done. Linux vendors should take care of that burden, so developers can focus on building great embedded applications.

As devices are becoming increasingly software-defined, new development experiences become possible. Build your embedded app, generate an OS image to deliver the app, burn and boot. Congratulations, you’ve built a smart appliance.

App focus

Developer-friendly embedded Linux should just deliver apps to devices. Satellite companies don’t build their own rockets. They focus on building satellites and lease a rocket to deliver it as a payload. Many developer teams also have to “build the rocket” to deliver embedded applications.

Developers would be more successful, if Linux vendors made it their job to provide and maintain the scaffold that teams need to deliver embedded apps. In such a world, teams would focus on creating apps.

The resulting app-centric development cycle could boil down to booting, building and deploying. Building on top of vendor-provided scaffolds, developers would create a bootable image for their target boards. Teams would then develop apps. After testing, they will build a system image that delivers all these apps. Then burn, deploy, done. 

App-centric embedded development cycle


Embedded software development practices pre-date the cloud-native and devops era. These practices come from a past when infinite compute capabilities of any architecture weren’t available on demand. They stem from a time when software was hosted locally, rather than on shared online repositories. They were made for a time when automated builds, and CI/CD were non-existent.

Building embedded software with modern CI/CD tools

Integrating embedded development toolchains with modern CI/CD tools unlocks devops-style collaboration. This means providing tools to mediate collaboration between security, product engineering, and operations focals. The security expert will push patches, product engineering will release features, and operations admins will manage device fleets. All in sync, using the same tools.

Ubuntu Core

Ubuntu Core puts developer teams first. Canonical engineers Ubuntu Core to unlock productive embedded software development workflows. Ubuntu Core comes with tools like Snapcraft, and infrastructure like IoT app stores. These capabilities enable developer teams to collaborate effectively around projects. We’ve made these things our job, delivering more than what embedded Linux vendors typically do. Our job is to free you up to do yours: inventing.