BlogEventsMeetup

What to Expect at the Zephyr Project Meetup (October 29, 2026) – Dublin, Ireland

By October 28, 2026No Comments
Agenda is live - Zephyr Project Meetup (October 29, 2026) – Dublin, Ireland

The Zephyr Project community is heading to Dublin, Ireland!

Join us on Thursday, October 29, 2026, from 5:00-9:00 PM for an in-person Zephyr Project Meetup hosted by Analog Devices.

The event is open to developers, engineers, contributors, students, technology professionals, and anyone interested in open source, embedded systems programming, and software development. Whether you are an experienced Zephyr developer or just beginning to explore embedded technologies, you are welcome to join.

As the Zephyr Project celebrates its 10th anniversary, this meetup offers an opportunity to connect with fellow community members, hear from industry experts, and explore how Zephyr is used in embedded and edge computing applications.

About the Host:

Analog Devices is hosting the Dublin meetup, bringing developers and open source enthusiasts together for an evening of technical learning, shared experiences, and networking centered around the Zephyr RTOS ecosystem.

Event Details:

  • Date: Thursday, October 29, 2026
  • Time: 5:00–9:00 PM, local time
  • Venue: Analog Device Office Dublin
  • Address: Beaver House, Beech Hill Office Campus, Clonskeagh, Dublin, D04 Y8X5, Ireland
  • Google Map link here.

Technical Sessions:

The evening will feature technical presentations covering open source development, system design, emerging technologies, and best practices for building connected devices with Zephyr.

Zephyr contributors, ecosystem partners, and industry experts will share practical applications and development experiences. Whether you are exploring Zephyr for your first project or already using it in embedded products, the sessions offer an opportunity to learn from others and gather ideas for your own work.

Agenda is live - Zephyr Project Meetup (October 29, 2026) – Dublin, Ireland

Agenda:

5:00 PM – 5:25 PM – Welcome Snacks & Drinks

5:25 PM – 5:30 PM – Welcome Note – Analog Devices Team

5:30 PM – 6:00 PM – Where Did My Message Go? Robust IPC on zbus for a Medical Wearable, Jason Murphy, Analog Devices

Many Zephyr-based embedded devices consist of independent subsystems running in parallel, including sensors, storage, logging, connectivity and power management, and they all need to talk to each other reliably. zbus is a solid foundation for that, but out of the box it’s a publish/subscribe bus, not a complete IPC system. This talk presents the architecture of an IPC layer built on top of zbus for a medical wearable project. The layer includes a command/response model with matched replies and timeouts, broadcast events for system-wide state, and data pipes for streaming bulk data. Although it was designed for a medical device, the patterns apply to any multi-component Zephyr application that needs reliable IPC.

6:05 PM – 6:35 PM – Is Zephyr on your radar?, Matthew O’Connor, Beara

Zephyr supports radars that do their own processing and report targets, but not the growing range of FMCW mmWave radars that stream raw ADC samples for the MCU to process. Today every project using one writes its own driver and hard-codes chirp settings and antenna layout into its signal processing, so that processing only works with one chip.

At Beara, we are building a privacy-preserving assisted living device using sensor fusion around a mmWave radar and a ToF sensor, and we’ve proposed a common API to close the mmWave streaming gap in Zephyr. mmWave drivers stream raw frames through RTIO and describe how they were captured: chirp timing, frequencies, antenna positions and sample layout. Processing configures itself from the radar instead of from hard-coded constants; the chirp profile lives in devicetree, and the build fails if it doesn’t match the register list that programs the chip.

This talk walks through the design of our open source BGT60TR13C driver, and walks through the pipeline we run on top of it; range-Doppler processing, target detection, 3D angle estimation, multi-target tracking and breathing detection. We’ll finish with the question we’d like the community’s input on before an upstream RFC: should raw radar frames get their own driver class, or build on the sensor API?

Attendees will take away:

  • Why radar and ToF sensors suit assisted living, where cameras raise privacy concerns
  • How raw mmWave radar data differs from typical sensor data, and why it needs its capture configuration alongside it
  • Using RTIO to stream large frames, and devicetree to check a vendor configuration at build time
  • The trade-offs between a new driver class and extending the sensor API

6:40 PM – 7:10 PM – Life of a Zephyr Pull Request – Fabio Baltieri, Google

What happens with a Zephyr Pull Request from the perspective of a maintainer and the release engineering team. CI, maintainer assignment, releases, backports and more.

7:10 PM – 7:40 PM – Break Time

7:40 PM – 8:10 PM – MLForge: an AI agent in the Zephyr build loop, Owen O’Hehir, Electronics Consult

Embedded ML models are usually trained for accuracy first and checked against the hardware last. That’s when RAM, flash and latency turn up as surprises, and every surprise costs a retrain.

MLForge is an open-source proof of concept that reverses the order. You describe the target in one YAML file: board, tensor arena, RAM, flash, latency deadline and error target. An AI agent proposes a Keras network, and the pipeline trains it and quantises it to int8 TFLite. It then builds real TFLite Micro firmware with west, runs it under QEMU or on the board, and feeds every measured result back into the next proposal, failures included.

Zephyr makes this practical, because the same application builds for qemu_cortex_m3 and for real hardware. Cheap iterations run in emulation, and board time goes on the numbers that matter. The talk covers how the loop is put together, how it measures latency and error honestly (error bars, noise floors, on-device scoring), and what we measured on the FRDM-MCXN947. It also covers the Zephyr lessons we learnt the hard way: CMSIS-NN running 18 times faster than the reference kernels, silent console truncation, float formatting in printk, and why the Neutron NPU path is built but still blocked.

It opens with a short aside on where this started: detecting elephant trumpets on a solar-powered ESP32 recorder (ELOC). The talk ends with a live demo on the NXP board.

8:15 PM – 8:35 PM – PyTorch to ExecuTorch: Deploying ML to Microcontrollers with Zephyr, Eoin Jordan, Edge Impulse

A few months ago I contributed the TensorFlow path for this in the form of the Edge Impulse Zephyr module SDK, and I’ve just had my first small PR merged into ExecuTorch itself.

This talk revisits the same deployment with the new ExecuTorch Zephyr module. ExecuTorch is PyTorch’s on-device runtime, and it can now be pulled into a Zephyr build as a West module with a single Kconfig option.

The target is the Arduino UNO Q, a dual-architecture board with an STM32U585 Cortex-M33 running Zephyr alongside a Qualcomm QRB2210 Linux core, comparable to pairing a Raspberry Pi with the original UNO.

I’ll walk through, as simply as possible, how to train a small PyTorch model, export it to a .pte, and run it on the MCU under Zephyr in tens of microseconds per inference, with the Linux side consuming the results over the internal UART without ever sitting in the real-time path.

The example is open source and reproducible with west init, so attendees leave with a working template for putting a PyTorch model on any Zephyr board.

8:35 PM – 9:00 PM – Closing Note & Networking, Shane McAllister, Analog Devices

Registration

Registration is required to help the host plan the space and event logistics. Seats are limited, so we encourage you to register early to secure your place. Register here.

For questions about the meetup, contact meetups@zephyrproject.org.

You can also join the Zephyr Project Discord server, to participate in community discussions.

Thank You to Our Supporters

Thank you to Analog Devices for hosting the meetup and bringing the Zephyr community together in Dublin. We also appreciate the speakers, volunteers, and attendees whose participation makes this event possible.

Support an Upcoming Zephyr Meetup

Interested in sponsoring development board giveaways or food and beverages for an upcoming Zephyr meetup? Complete the sponsorship interest form, and our organizers will contact you with event details and coordination information.

About the Zephyr Community Meetups

This meetup is part of the Zephyr Community Meetup Series, a collection of local gatherings hosted by community members with support from the Zephyr Project.

These events provide a welcoming space for developers, students, researchers, and embedded systems enthusiasts to exchange technical knowledge, present real-world projects, discuss challenges, and build stronger local open source communities.

Whether you are based in Dublin or another part of the world, we encourage community members, companies, universities, and developer groups to get involved. Contact meetups@zephyrproject.org or complete the meetup interest form to explore how you can bring Zephyr to your community.

We look forward to seeing everyone in Dublin!