</>EmbeddedInterview

How does Zephyr differ from FreeRTOS?

MediumRTOS & Real-Time Systems

Short answer: FreeRTOS is a small, portable kernel (scheduler, queues, semaphores, timers, event groups) with optional add-on libraries; drivers usually come from the silicon vendor's SDK, and configuration is a header file. Zephyr is a full RTOS platform under the Linux Foundation: it uses Kconfig and devicetree (like Linux) for configuration, has a unified driver model and many in-tree drivers, networking (IPv4/IPv6, Bluetooth LE, Thread/Matter), file systems, a shell, logging, power management, MCUboot integration and optional user-mode isolation, built with CMake and the west tool. Zephyr does more out of the box but is larger and has a steeper learning curve.

FreeRTOS Zephyr
Scope kernel + optional libraries complete OS platform
Configuration FreeRTOSConfig.h Kconfig (prj.conf) + devicetree + board definitions
Drivers vendor SDK/HAL, or your own in-tree, generic APIs (gpio_pin_set_dt, i2c_write_read_dt)
Build any (Make, CMake, IDE projects) CMake + west meta-tool
Networking / BLE separate (FreeRTOS+TCP, vendor stacks, lwIP) integrated IP stack, Bluetooth host/controller, OpenThread
Memory protection FreeRTOS-MPU port user mode threads with MPU/MMU (CONFIG_USERSPACE)
Footprint very small (≈ 5–10 KB kernel) larger, but highly configurable (minimal builds of ~10 KB are possible)
Licensing MIT Apache 2.0
Learning curve gentle steep (devicetree, Kconfig, west)
Governance maintained by Amazon (AWS) Linux Foundation project with many vendors

When to choose which: FreeRTOS for small, simple products, existing vendor SDK-based projects, or teams that want minimal abstraction. Zephyr for connected products (BLE, Thread, Matter, IP), portability across many boards, a Linux-like development model, and long-term vendor-neutral support (Nordic's nRF Connect SDK is built on Zephyr).

Others worth knowing: Eclipse ThreadX (formerly Azure RTOS, with safety certifications), NuttX (POSIX-compatible, used by PX4 drones), RIOT (IoT), Mbed OS (end of life), and commercial safety RTOSes (SafeRTOS, VxWorks, QNX, INTEGRITY).