Magic SmokeBB-0074

Claude Code with Nordic's MCP misses a two-board BLE bug that only the device logs reveal

Adsum Networks set Claude Code with Nordic's MCP on a BLE bug where data flowed one way between nRF52 and nRF53 boards. Running Claude Haiku 4.5, it guessed at fixes from the source and looped without solving it. Adsum's own IoT Coder, on the same model and with live logs from both boards, found the boards' roles were inverted.

Open original source youtube.com · Adsum Networks

Shown working
Why this evidence label?

Twelve-minute screen recording of both sessions against the physical nRF52 and nRF53 boards, including live log capture from both devices.

How we check entries
Play videoClaude Code with Nordic's MCP misses a two-board BLE bug that only the device logs revealThe player loads from youtube-nocookie.com when you press play.
The source video, on YouTube.

Briefing

Adsum chose a bug that reading the code alone cannot solve, and gave Claude Code explicit step-by-step instructions on top of Nordic's MCP knowledge base. In the 12-minute video, Claude Code falls back to the source it can read and spends tokens in cycles. IoT Coder captures live logs from both boards before it proposes anything.

Adsum makes IoT Coder, so this is a vendor comparing its own product with Claude Code. The video compares approach rather than finishing the fix; Adsum says the bug takes about 5 flashes to close and documents full runs in an open benchmark.

“a general agent debugs the code it can read and ignores the hardware it can't.”

Adsum Networks, in the source on youtube.com

Tags

Report a problem with this entry