Debugging
Debugging Discipline for Firmware
Structured triage: hypotheses, tracepoints, fault isolation, and postmortems that survive audits.
- Duration
- 4 weeks · 48 lab hours
- Format
- Weekend sprints
- Cohort
- October 2025
- Informational price
- KRW 920,000
Program narrative
Move from printf panic to repeatable routines. You will build a personal triage playbook, practice bisecting regressions with git-bisect and hardware revision tags, and learn when to reach for instruction trace versus SWO. Includes collaborative drills on flaky I2C and ghost interrupts.
What ships in the syllabus
- Fault tree templates tuned for intermittent bugs
- SWO vs UART trace budgeting exercises
- Postmortem writing clinic with redacted real examples
- Pair debugging rotations with rotating roles
- GDB + scripting micro-automations
- Checklist for when to freeze binaries vs continue probing
- Bench etiquette brief for shared lab gear
Outcomes we can observe
- Close a seeded bug using a documented five-step loop
- Author a postmortem with causal chain and prevention hooks
- Lead a 15-minute debug huddle with evidence-first norms
Aya Matsuda
Student support manager turned trace coach; ex-field apps for industrial drives.
Cohort murmurs
Quote-first
Client in industrial sensing — the fault tree template is now mandatory on our firmware PRs.
D. (anonymous)
Pair rotations felt awkward day one, invaluable by week three.
Kenji · QA bridge · Bluegrain Labs · 5/5 · Google
Straight answers
We provide debug probes; bring a laptop with two USB-C ports or a powered hub.