ukasol

7 posts · 2 languages

Blog

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.

Latest 9 min

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. Zephyrnative_simTesting
8 min

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. ZephyrKconfig
10 min

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. ZephyrDevice Tree
7 min

Why Zephyr, for companies

Zephyr is spreading fast, and hardware dependence is now a strategic risk. The two main reasons to move a team, what else comes with it, and what it costs. ZephyrProduct Development
7 min

Why I use Zephyr

Every part of Zephyr leans on the others, and that is deliberate. One blinky, three boards, three drivers: what that coherence buys you, and where it costs. Zephyrnative_simBLE
6 min

Why invest in Zephyr as an engineer

Learning Zephyr takes time and effort. In return you get faster, better work, habits that make you a better engineer, and a skill the market asks for. ZephyrCareer
6 min

Zephyr confused me at first

Hello World ran on day one; after that I was lost. Why Zephyr is not a new library, what the build hides behind main.c, and the order that made it click. ZephyrEmbedded Software