Build Before Installing: Zephyr Dev Environment Using Codespaces
summary
A GitHub Codespaces dev container, implemented as a 23-line devcontainer.json, boots a locked manifest Zephyr tree and toolchain so samples build in a browser VS Code in about 40s and cover 95% of the local workflow. Custom West commands like West download copy timestamped binaries into a downloads folder for use with nRF Connect to flash locally. USB-based flashing and West flash/debug don’t work in the cloud; local Docker can access USB on Linux only with privileged containers. Prebuilt images cut first-run latency; WebUSB is not available.
AI-written summary · about
chapters (20)
- 0:00Zephyr dev challenges
- 1:02Who is Goliath and why Zephyr
- 3:54GitHub Codespaces and Dev Containers
- 5:42Zephyr manifest setup
- 7:06Live demo: build Zephyr in Codespaces
- 8:55How Dev Containers work in detail
- 11:27Oncreate commands and env setup
- 13:14VS Code container customization
- 14:40Binary downloads from cloud
- 17:06Custom West commands for binaries
- 18:31Pre-built containers for speed
- 19:13Codespaces latency and regions
- 19:57Dev Containers locally
- 21:03Local flashing with Docker limits
- 23:12Web USB and cross-platform
- 24:15Current workflow and future uses
- 25:39Versioned Zephyr SDK in containers
- 26:22Acknowledgments and resources
- 27:03Closing and Goliath pitch
- 27:24Q&A
related talks
28mBuild Before Installing: Zephyr Dev Environment Using Codespaces
41mHands on Molding VS code into a care free development environment to develop with Zephyr RTOS
27mZephyr and You: A Developer Environment for Newcomers
37mZephyr Onboarding in 30 Seconds - Methods and Experiments During Zephyr Training
34mZephyr Tools for VSCode: Get Started with Zephyr Fast
41mZephyr & Visual Studio Code: How to Develop Zephyr Apps with a Modern, Visual IDE
43mGoing West: How We Develop and Maintain a Zephyr-based Microcontroller SDK
46mZephyr Workbench: Open Source Zephyr Extension for VSCode