Zephyr Onboarding in 30 Seconds - Methods and Experiments During Zephyr Training
summary
New users repeatedly fail at installing Zephyr toolchains so the experiments focus on reproducible setups: Chasm desktop-in-browser gives a full Ubuntu VS Code session that reaches a build in 30 to 60 seconds, but still requires downloading binaries to flash local boards and suffers network congestion with many attendees. Image laptops, USB sticks, and VMs reduce variability; switching to Nordic dev kits with on-board J-Link improves debugging. Best ratios are one trainer per five learners; remote training costs scale by EC2 instances and Chasm licenses.
AI-written summary · about
chapters (9)
- 0:00Zephyr onboarding training
- 1:44Training challenges and importance
- 3:08Failed training lessons
- 7:22Training environment truisms
- 9:06Current setup with Chasm
- 14:59Training experiments and improvements
- 18:29Remote training tool challenges
- 20:33Future experiments and alternatives
- 25:49Q&A
related talks
28mBuild Before Installing: Zephyr Dev Environment Using Codespaces
28mBuild Before Installing: Zephyr Dev Environment Using Codespaces
46mZephyr Workbench: Open Source Zephyr Extension for VSCode
31mA Zephyr User Story
27mZephyr and You: A Developer Environment for Newcomers
02h 02mTutorial: Hands-on with Zephyr-based IoT Hardware - Data Goes in, Dat...- 46mZephyr Workbench: Open Source Zephyr Extension for VSCode
25mChallenging Hardware Contests With Zephyr and Lessons Learned