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
In the works
-
Secure firmware delivery
MCUboot, signed and encrypted images, and over-the-air updates that roll back when something goes wrong.
- NextMCUboot explained: what happens between reset and main()
- NextFirmware signing keys: from a developer laptop to the factory
- NextOTA over BLE with MCUmgr, and why a new image must confirm itself
-
Power and field reliability
Getting down to real microamps, and finding out why a device failed once it is out in the field.
- NextMeasuring power on Zephyr: from PM settings to real microamps
- NextWhen firmware fails in the field: coredumps, retained memory and a watchdog that tells you why
-
From prototype to production
Taking a design past the prototype: bring-up, production test, traceability and releases you can reproduce.
- NextThe production-ready firmware checklist
- NextBuilding an open sensor node in public, part 1: requirements and architecture