CoffeeCaller – a Fully Open Source Product Development Example
summary
Prototype becomes a compact PCB with an nRF52840 SOC, KiCad files and a UF2 bootloader, running Zephyr RTOS with device tree as the hardware/software bridge. Development starts on ESP32 dev kits then moves from flaky BLE Mesh to open thread transport, 15–20 units run in offices, production cost targets ~€9 per board at 200 units. Native-sim, fake drivers and CI tests replace hardware for iterations; regulatory CE and EMC compliance remain unresolved.
AI-written summary · about
chapters (16)
- 0:00CoffeeCaller project intro
- 1:50Coffee communication problem
- 3:14Product vision and requirements
- 5:19Proof of concept prototype
- 7:04Software with Zephyr RTOS
- 9:31First prototype rollout
- 11:38Professional hardware design
- 15:17Hardware development and feature creep
- 18:51Final hardware and MCU architecture
- 21:38Software refactoring
- 22:20Native simulation for testing
- 28:16Project modularity structure
- 30:23Feature subsystem creation
- 32:58Shell testing and CI
- 34:25Lessons learned and next steps
- 36:37Answering audience questions
related talks
49mOne Code Base, Multiple Targets
08mKeynote: Zephyr as the Foundation for a Microcontroller SDK
34mPractical Tips to Boost Your Productivity When Using Zephyr
13mOpenHW CORE-V MCU DevKit for Cloud Connected IoT
25mChallenging Hardware Contests With Zephyr and Lessons Learned
43mGoing West: How We Develop and Maintain a Zephyr-based Microcontroller SDK
40mArduino to RTOS - A Pilgrim's Progress
27mInsights on the Re-Architecting to a Single Codebase, Running on Different Hardware...