Testing Zephyr Bluetooth Devices at Scale
summary
Practical checklist: a scalable farm built from nRF52840 dongles plus Raspberry Pi runners with Balena and GitHub Actions runs nightly firmware across 100+ devices for 24+ hours, deliberately crashing devices to collect core dumps and catch low‑probability bugs. Measured point‑characterisation shows L2CAP beats GATT on Android and led to dropping coded PHY for the office profile. Simulation using Root Canal/native sim and OpenTelemetry tracing complements hardware tests for reproducible CI and system visibility.
AI-written summary · about
chapters (12)
- 0:00Bluetooth testing challenges
- 2:11Desk to scalable validation
- 4:22Bluetooth testing complexity
- 7:59Early real-device characterization
- 11:10Isolating non-Bluetooth code
- 13:18Hardware-in-the-loop with Pi
- 16:50100+ device test bed
- 20:48Rare bugs with crash dumps
- 26:16OpenTelemetry for insights
- 28:01Zephyr Native Sim
- 31:14Key lessons in Bluetooth testing
- 33:19Q&A
related talks
40mTesting Zephyr Bluetooth Devices at Scale
32mBoF: Quality and Testing Processes for Zephyr + Discussion
48mRiding the Upstream Wave: Keeping Your Zephyr Apps Regression Free
37mStreamlining Testing with Generic Tests and Emulators
35mTest Automation for Bluetooth Connected IoT Devices
46mZephyr Application Development Using TDD: Getting Started
46mZephyr Application Development Using TDD: Getting Started
18mKeynote: From Zephyr’s Structured Data to Traceable and Testable Open Hardware