Hands on Molding VS code into a care free development environment to develop with Zephyr RTOS
summary
Field report shows a concrete VS Code + Docker workflow that makes Zephyr development reproducible: a repo contains devcontainer.json plus workspace settings, tasks.json to run West init/update, and CMake presets for Release/Debug/tests; Docker image houses Zephyr SDK, pip deps and Conan for gtest, avoiding local installs. Remote debugging uses Raspberry Pi “test-gates” that run a GDB server and J-Link for shared devices. Sample repo on GitHub demonstrates first-time setup, builds native posix unit tests and launches debugger.
AI-written summary · about
chapters (13)
- 0:00Introduction and motivation
- 2:25Understanding Zephyr
- 4:23Development setup challenges
- 7:34Dev container configuration
- 10:02Setup requirements and tips
- 11:36Using tasks.json
- 13:24Remote debugging strategies
- 14:46Launch configuration
- 17:02Refining project structure
- 21:48Demonstration of the workflow
- 27:47Success stories and outlook
- 30:52Advanced integration tools
- 33:53Q&A session
related talks
28mBuild Before Installing: Zephyr Dev Environment Using Codespaces
29mZephyr Development Environment for Students
28mBuild Before Installing: Zephyr Dev Environment Using Codespaces
41mZephyr & Visual Studio Code: How to Develop Zephyr Apps with a Modern, Visual IDE
27mZephyr and You: A Developer Environment for Newcomers
46mZephyr Workbench: Open Source Zephyr Extension for VSCode- 46mZephyr Workbench: Open Source Zephyr Extension for VSCode
34mZephyr Tools for VSCode: Get Started with Zephyr Fast