Insights on the Re-Architecting to a Single Codebase, Running on Different Hardware...
summary
Claims a working single codebase for multiple PCBs using Zephyr OS and MCUboot and shows how it actually migrates deployed devices over BLE by staging bootloader and app artifacts in external flash. Memory and throughput workarounds include squeezing a Zephyr build to fit a 64 KB device, using mempool, stack sentinels and DMA/PPI, and profiling with a picoscope. Flash streaming latency drops from 4.5 ms to 220 μs after API and callback changes. Uses LittleFS, Memfault and proves the migration and runtime optimizations succeed.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:19What is Augury?
- 1:37The start point
- 2:33Single Code Base Concept
- 2:52Why Zephyr fits SCB
- 9:57Migrating Size Uncertainty
- 13:25Migrating functional Uncertainty
- 17:30Single Code base Design
- 19:30SCB Device API Expansion
related talks
35mBoosting Product Development With the Zephyr RTOS – a Critical Reflection
25mChallenging Hardware Contests With Zephyr and Lessons Learned
49mOne Code Base, Multiple Targets- 35mBoosting Product Development With the Zephyr RTOS – a Critical Reflection
31mA Zephyr User Story
17mHow We Got DOOM Running on Zephyr (And Why You Should Try It)
08mKeynote: Zephyr as the Foundation for a Microcontroller SDK
15mLightning Talk: A Reusable Zbus Based Architecture, Abstracting Core Application Components