Zephyr RTOS



The Zephyr™ Project is a scalable real-time operating system (RTOS) supporting multiple hardware architectures, optimized for resource constrained devices, and built with safety and security in mind.



The Zephyr kernel is derived from Wind River’s commercial VxWorks Microkernel Profile for VxWorks. Microkernel Profile has evolved over 20 years from DSP RTOS technology known as Virtuoso. The RTOS has been used in several commercial applications including satellites, military command and control communications, radar, telecommunications and image processing. The most recent example of the technology’s success is the successful Philae Landing on Comet Churyumov–Gerasimenko and the accompanying Rosetta Orbiter.


The Zephyr Project, a Linux Foundation hosted Collaboration Project, is an open source collaborative effort uniting leaders from across the industry to build a best-in-breed small, scalable, real-time operating system (RTOS) optimized for resource-constrained devices, across multiple architectures.


The Zephyr Project’s goal is to establish a neutral project where silicon vendors, OEMs, ODMs, ISVs, and OSVs can contribute technology to reduce the cost and accelerate time to market for developing the billions of devices that will make up the majority of the Internet of Things

The Zephyr Project strives to be the best-of-breed, open source RTOS for connected, resource-constrained devices, and built with security and safety in mind.

The Zephyr Project is working with leaders across the industry to create a solution that integrates and creates a robust, easy to use, customizable RTOS for a variety of industries and comprehends varying degrees of development needs. Zephyr Project and Linux Foundation will take strides in continuously expanding membership, building awareness to the project, and reinforce the open source development model through encouragement of community contributions.

Why create another RTOS?

Connected devices are the future, and development is happening quickly. The technology requirements are so vast that no one person or company has all the answers. Collaboration is key to share expertise and drive down the cost of connected devices which are projected to be deployed by the billions by 2020. A platform to promote collaboration has to be commercially-neutral, inclusive of all contributors, and governed in such a way that all interests are fairly represented. Today, only one such project exists, and that is Zephyr Project.

In the past few years the world has seen numerous “small-footprint” RTOSes. There are new RTOSes released by companies at an increasing rate, open source and otherwise, why create another? It may be more appropriate to ask, “Why does the industry need RTOS consolidation?” With this proliferation in RTOSes and small OSes we’ve come to notice a few things:

Market Fragmentation

  • Several RTOS options for small devices, each with their own restrictions.
  • Paid-for, commercial license or restrictive non-IP-friendly open source licenses
  • Open source projects tailored to a single party’s goals

Other RTOSes are run by major stakeholders with promises of open source & collaboration

  • No clear way to upstream code that better suits your product development model
  • No community support ecosystem from professionals and experts.
  • No clear leader

Alternative Betriebssysteme für den ESP32

Ich dachte ja, wir wären relativ stark aufs FreeRTOS festgenagelt, wenn es sich um ordentliche Betriebssystemunterstützung für den ESP32 handelt. Und da sich das ja mittlerweile Amazon so halb…

Aus der Richtung https://www.zephyrproject.org/ kommend habe ich vorsichtige Hoffnung, dass das vielleicht auch was für Normalsterbliche werden könnte.

… bin nun seit einiger Zeit schon öfters mal bei https://docs.zephyrproject.org/ vorbeigesteuert und wollte das jetzt endlich mal mit Euch teilen. Wahrscheinlich wisst Ihr aber eh schon von dem ganzen Geschwummse und noch viel mehr?

This. -c 'set ESP32_RTOS none'

cd ~/esp/openocd-esp32
src/openocd -f interface/ftdi/flyswatter2.cfg -c 'set ESP32_ONLYCPU 1' -c 'set ESP32_RTOS none' -f board/esp-wroom-32.cfg -s tcl

ESP32 — Zephyr Project Documentation


Auf jeden Fall ganz ab vom Schuss, meilenweit von Pycom MPY entfernt – vermutlich. Man weiß es ja manchmal vorher noch nicht.


Q: Wenn man damit in der Theorie geschmeidig auch hin zu ARM Boards — Zephyr Project Documentation oder von dort dann rüber zu RISCV Boards — Zephyr Project Documentation wechseln kann…

A: Träum weiter.

Grundsätzlich gibt es seit kurzem einen MicroPython port to Zephyr RTOS.


Hardware example: Intellinium security shoes

Zephyr läuft sogar auf Sicherheitsschuhen.

KubeCon + CloudNativeCon + Open Source Summit China - Zephyr Project

Despite the title, this is a good summary about what Zephyr did to their configuration largely based around MCU and peripheral components from Nordic Semi.

That’s how it all started in 2015 already from the perspective of Intellinium.

Hardware example: PHYTEC reel board


reel board is an evaluation board based on the Nordic Semiconductor nRF52840 SoC. The board was developed by PHYTEC Messtechnik GmbH in cooperation with Zephyr Project for the Hackathon - “Get Connected”. The board has a built-in debug adapter based on the DAPLink interface firmware and NXP MK20DX128VFM5 SoC.

Zephyr Meetup @ The 1st Open Source IoT Projects Seminar in China - Zephyr Project