Software-defined Hardware with Zephyr
summary
Zephyr claims to let teams ship IoT products faster by separating hardware mapping, software and config and that claim is shown concretely: Devicetree lets the same application run on two boards with different accelerometers and buses, Kconfig produces three distinct builds from one codebase in about 30 seconds, and MCUboot enforces integrity and rollback protection while relying on an OTA orchestrator like nRF Cloud memfault to deliver images. The approach is used with OEM platforms and it works in production.
AI-written summary · about
chapters (10)
- 0:00Zephyr for IoT development
- 1:05Traditional embedded challenges
- 2:28Zephyr accelerates hardware porting
- 3:51Zephyr’s Device Tree superpowers
- 4:54Device Tree in practice
- 5:36Kconfig for customization
- 6:38MCUboot for secure updates
- 7:42Blecon’s Zephyr workflow
- 8:46Just-in-time OTA updates
- 9:29Adopt Zephyr for faster IoT
related talks
49mThe Zephyr™ Project – An Updated Overview
33mSponsored Session: Why NXP is Doubling Down on Zephyr Project
33mSponsored Session: Why NXP is Doubling Down on Zephyr Project
13mKeynote: How Zephyr Enables Industry Collaboration
39mBoF: Meet the Zephyr Community
13mKeynote: Zephyr is Not a Product!- 13mKeynote: Zephyr is Not a Product!
40mBoF: Zephyr: Meet the Maintainers