Start here
Zephyr fundamentals
Why Zephyr, and how Device Tree, Kconfig and the build fit together, for engineers coming from bare metal or FreeRTOS.
Latest writing
Zephyr as I learned it, coming from bare metal: why I moved to it, and how Device Tree, Kconfig and native_sim actually work. Every post is also in Turkish.
Zephyr Series
Developing firmware without hardware, with native_sim
It compiles your code for the host, not the target. How native_sim works, what it emulates, and how GDB and AddressSanitizer find bugs before a board exists.
Zephyr Series
How project configuration with Kconfig works
Configuring a project without touching the source: where Kconfig values come from, in what order they merge, and how to find out why one did not take.
Zephyr Series
What Device Tree is, from a bare-metal developer's point of view
Zephyr moved what Linux does at runtime to compile time. What a devicetree is, how an overlay adds a sensor, and why the result costs nothing at runtime.Topics
7 guides
Zephyr fundamentals
Why Zephyr, and how Device Tree, Kconfig and the build fit together, for engineers coming from bare metal or FreeRTOS. Open the guide
1 guide
Testing and CI
Developing and testing firmware before the boards exist: native_sim, ztest, emulated peripherals, Twister and CI. Open the guide
What I work on
Most products need several of these at once. Working across all of them, from the register map to the release process, is where I am most useful.
Contact
Want to talk about embedded systems, RF or firmware architecture? Send me an email, or find me on LinkedIn.