Field Software Engineer - Spanish/English, Remote

Canonical Zephyr 26.04 LTS: 15-Year MCU Support and the EU CRA. 2 hours ago 0 Canonical announced Zephyr 26.04 LTS on September 21, 2026 - the first enterprise-grade, commercially supported distribution of the Zephyr RTOS, timed to land at Embedded World North America in Anaheim. Available through an Ubuntu Pro for Devices subscription, it commits to 15 years of security patches, toolchain maintenance, and CVE coverage for microcontroller-based products. The timing is deliberate: the EU Cyber Resilience Act's first reporting obligations kicked in on September 11, 2026, and device makers without a patching plan are already exposed. What Zephyr 26.04 LTS actually covers. The critical distinction here is not just the kernel. Canonical's Zephyr 26.04 LTS bundles the RTOS kernel alongside West - Zephyr's meta-tool for managing repositories, building firmware, and flashing devices - plus a Workshop SDK that provides a ready-to-use environment on any hardware. A developer can run west build immediately without working through a complex toolchain setup. That detail matters more than the headline number: embedded teams have long complained that setting up, building, and integrating libraries in Zephyr is the real friction, not the RTOS itself. For comparison: upstream Zephyr 3.7 LTS (released July 2024) is community-maintained for roughly five years, covers the kernel, and carries no commercial SLA. Zephyr 26.04 LTS triples that to 15 years, covers the full stack, and comes with Canonical backing. The Linux Foundation's 2026 survey of 413 Zephyr users found that 49% named long-term maintenance support as their single biggest challenge over the next five years. Canonical's announcement is a direct response to that number. Why the EU CRA makes this urgent. The EU Cyber Resilience Act is not a future concern. As of September 11, 2026, manufacturers shipping products with digital elements to the EU must already report actively exploited vulnerabilities to ENISA within 24 hours. Full compliance - including SBOMs, a documented support lifecycle, and a minimum five-year patch commitment - is required by December 11, 2027. An unmaintained Zephyr fork with no upstream CVE patching is a compliance liability under that framework. The EU CRA compliance guidance from Mend.io is blunt: "If you don't have SBOMs and a vulnerability management process in place before September 2026, you cannot comply." Canonical's commercial distribution covers the patching pipeline explicitly, and their Embedded World session is titled "Surviving the CRA: Architecting Zephyr for 15-Year Lifecycles and Long-Term Compliance." Who should be paying attention. The direct targets are silicon vendors, ODMs, and OEMs building products with decade-plus lifecycles - medical devices, industrial controllers, smart metering, automotive-adjacent hardware. The Linux Foundation survey found that 52% of organizations already support Zephyr-based products for five to ten years or longer. Those organizations, along with anyone newly evaluating Zephyr for long-lived products, now have a commercial support option that matches actual lifecycle requirements. Renesas Electronics - one of the launch partners - stated: "By pairing this hardware foundation with Canonical's enterprise-grade, long-term support for Zephyr, customers can gain the hardware longevity, software stability, and security maintenance needed across the entire product lifecycle." Canonical's embedded stack is now complete. This announcement completes a pattern Canonical has been building throughout 2026. In May, Ubuntu Core 26 extended the LTS model to Linux-class IoT and edge devices. Zephyr 26.04 LTS now brings the same framework to bare-metal microcontrollers. A silicon vendor or ODM with products across device classes can now cover the entire stack through a single vendor relationship and a single Ubuntu Pro for Devices subscription. Whether Canonical can sustain 15-year commitments across a rapidly evolving ecosystem is the real question. The Zephyr project itself moves fast; maintaining a stable, commercially supported branch while tracking upstream changes for a decade and a half is a serious operational commitment. But the model is proven - Ubuntu LTS has been doing exactly this since 2006. The market signal is clear: 70% of US and Canadian organizations already deploy Zephyr in commercial products, and the EU CRA is forcing everyone to think about patch lifecycles for the first time. Zephyr 26.04 LTS is available now as part of Ubuntu Pro for Devices. Canonical will be at Embedded World North America in Anaheim from September 22-24. I am a playful and cute mascot inspired by computer programming. I have a rectangular body with a smiling face and buttons for eyes. My mission is to cover latest tech news, controversies, and summarizing them into byte-sized and easily digestible information.

Canonical Evolution of Enterprise Open Source RISC-V at Hot Chips 2026. September 7, 2026 Canonical presented the Evolution of Enterprise Open Source RISC-V at Hot Chips 2026. Gordan Markuš, Canonical's Director of Silicon Alliances, walked through how Ubuntu is built, how ISA support is managed across architectures, and what it will take to make RISC-V enterprise-ready. ServeTheHome Networks, Inc. did this one live like its other Hot Chips coverage, but are publishing it a bit later around a cluster of RISC-V pieces. Canonical's underlying argument is that an Ubuntu system should behave like an Ubuntu system no matter what processor drives it. Its presentation builds from how Ubuntu packages are assembled and supported, then applies that model to RISC-V. Ubuntu is assembled from a kernel and user space that Canonical commits to supporting for years. This Universe package archive contains roughly 30,000 packages, while the smaller Main archive contains about 3,000 packages and offers a longer support window, up to 15 years with Ubuntu Pro. Canonical also maintains a portfolio of kernels tuned for hyperscaler and silicon partners, which matters for RISC-V because there is no single reference design. The core aim is for an Ubuntu system to always behave like an Ubuntu system, regardless of the ISA or platform. Canonical says its work is not done until it can long-term patch and maintain the released binary aggregation and deliver a unified Ubuntu experience, meaning every new architecture has to flow through the same release and maintenance cycle. Packages are built for each supported architecture, and each architecture gets a baseline, the oldest or least capable ISA and extension set that can run Ubuntu of that generation. Canonical provides server resources for building and distributing packages and maintains a core development team responsible for their upkeep. RISC-V may sound exotic, but Ubuntu supports not only Arm and x86 CPUs but also IBM POWER and Z mainframes. Canonical shows where each architecture baseline sits today. This amd64 target assumes the original 64-bit AMD and Intel CPUs, while arm64 uses an ARMv8-A baseline with VFPv4 and NEON. This RISC-V riscv64 target moved from the RVA20 profile to the RVA23 profile with Ubuntu 25.10. Beyond baselines, Ubuntu 25.10 introduced architecture variants, allowing packages to be built more than once, each targeting different CPU features. This amd64v3 variant targets the x86-64-v3 microarchitecture level, adding instructions such as AVX2, FMA, and BMI2 while retaining support for older machines. This is the same pattern Canonical plans to apply to future RISC-V profiles. If you saw the Update on RISC-V Standards and Adoption at Hot Chips 2026, the motivation will make sense. Ubuntu introduced arm64 support back in 2011, but really it was Ubuntu 16.04 LTS that made Arm server CPUs usable without lots of custom patching. It wants to support advanced features and platform-specific acceleration on new ISAs without weakening security and support SLAs. RVA23 is the standardized application baseline Canonical is targeting for 64-bit application processors. Since it requires vector operations, hypervisor support, and bit manipulation out of the box, RVA23 aims to deliver binary portability across diverse silicon and remove software porting ambiguity. The RVA23 profile ratification is done, and so is server platform ratification, with server-class RVA23 hardware expected from multiple vendors in 2026 and 2027. Canonical notes that unlocking a new major profile is non-trivial, since its build systems require upgrades and cross-team coordination. Profiles help ensure that hardware implementer roadmaps and software developer roadmaps can intersect. Package coverage on RISC-V is close to catching up with the mainstream builds. Around 95% of packages are currently available on RISC-V compared with amd64, while Snap support is still a work in progress because most publicly available snaps today target the client and desktop ecosystem. Its STH team generally prefers to use the more generic apt package manager rather than snaps, but here ServeTheHome Networks, Inc. is. With 3,443 packages under test and 1,898 passing, RISC-V posts about a 55.1 percent pass rate on an Ubuntu 26.10 test snapshot, well below the roughly 92 percent seen on amd64. Canonical attributes part of that to emulated build and test targets, stretching execution times from hours to days, and to adding native RISC-V builders with help from partners supplying server-grade RVA23 platforms. It also has a much lower percentage of packages that have tests than the other architectures, which gives you a good idea of just how mature RISC-V is. Canonical Kubernetes and MicroCloud are being ported for native RISC-V container orchestration and edge cloud. The company is working on bringing RISC-V out across its stack though. Open source collaboration is central to the push. Canonical participates in the RISE Project with RISC-V International, which targets commercial software readiness across mobile, consumer electronics, datacenter, and automotive. RISE focuses on accelerating open-source software for RISC-V, improving platform implementation quality, and aligning ecosystem efforts. Native RISC-V runners on Ubuntu 24.04 back a build and board farm hosted at Scaleway Elastic Metal with Alibaba and SpacemiT hardware, and the project reports 24,000 jobs and 700,000 minutes across 116 organizations. Taken together, Canonical is betting that standardized profiles and broad upstream collaboration can push RISC-V past the software readiness gap that has historically slowed open source adoption of new ISAs. It frames RVA23-style profiles as the way to make software targeting predictable and to make multi-architecture maturity the foundation for enterprise-grade deployments. Final words. With server-class RVA23 hardware arriving over the next two years, the software stack now has a fixed target to converge on. Hopefully this moves RISC-V into a more mainstream role. Still, it seems like there is quite a bit of ground to cover.