Debugging a Pi Zero 2W BadUSB with Claude Code: Fixing an 'Impossible' Bug

About 10 months ago, a developer built a Pi Zero 2W BadUSB toolkit but one feature — "fully resets between attacks" — never worked. Marked as WIP, it was abandoned. This week, they rebuilt the project end-to-end with Claude Code as a pair-programmer. The result: the "impossible" feature now works, and the session uncovered several subtle bugs.
What Claude Code Did
- Diagnosed root cause in one read: The listener watched
/dev/hidg0existence — true from boot — so it fired payloads on power-up regardless of host attachment. The correct signal is/sys/class/udc/<udc>/state == "configured". - Empirically confirmed hardware limitation: When the first fix didn't fully work, Claude SSHed in, asked the dev to plug/unplug while it polled sysfs and the dwc2 debugfs
regdumpregister. It found theGOTGCTLregister freezes at0x000d0000regardless of cable state — the Pi Zero 2W has no VBUS sense wired to the SoC's OTG block. It pivoted to an active-unbind workaround with cooldown + rate-limit safeguard. - Caught a silent Python bug:
open(udc_path, "w").write("")doesn't invokewrite(2)with zero bytes — CPython'sTextIOWrapperelides the call. The unbind was a no-op for an hour of testing. Fixed toos.write(fd, b"\n")to force a syscall. - Fixed forbidden-on-configfs teardown:
rm -rfwas failing because configfs forbids unlinking kernel-managed attribute files. Proper sequence isrmdir-only, leaf-to-root. - Wrote a 34-test pytest suite against a mock HID engine, enabling parser testing on any host without a Pi.
- Updated AI memory: The developer uses Postgres as long-term memory for Claude — those bug entries are now referenced in similar configfs/USB-gadget projects.
The entire working session took about 4 hours, mostly waiting for physical plug/unplug. The PR had six well-scoped commits with proper co-author tags and a test plan. The project (Pi-Zero-2W-Bad-USB) is MIT licensed, with Ducky-Script-style payload language, variables, IF/WHILE, HOLD/RELEASE, INJECT MOD, RANDOM *, US/UK keymaps, optional RO mass-storage gadget, systemd integration, and idempotent installer.
For developers doing hardware-in-the-loop workflows with Claude Code, this is a compelling case study in AI-assisted debugging at the sysfs and register level.
📖 Read the full source: r/ClaudeAI
👀 See Also

Patient uses Claude AI to interpret medical data and navigate brain cancer treatment
A 27-year-old patient with primary mediastinal B-cell lymphoma with CNS involvement uses Claude AI daily to interpret immunohistochemistry panels, analyze PET-CT scan results, evaluate CAR-T clinical trial data, understand drug mechanisms, and prepare questions for medical team.

Developer Builds Habit Tracker App with Claude AI, Earns First Revenue
A developer with no programming background used Claude Code to build a Matrix-themed habit tracker app with 47,000+ lines of code, generating $25 in revenue from 6 paying users in the first week of marketing.

Developer Builds AI Baseball Simulation Engine with Claude Code in Two Weeks
A developer used Claude Code to build a complete baseball simulation system with 30 AI-managed MLB teams, game recaps, press conferences, and audio podcasts. The project cost $50 in API credits and includes a simulation engine, content pipeline, Discord bot, and website.

Running Claude Code as a Pure Judgment Engine Across the Full SDLC
A developer shares their architecture for using Claude Code as a reasoning engine inside a multi-layer system: Python handles orchestration, Claude Code handles code writing and review, with isolated subagents and a persistent wiki layer.