@erratahunter
erratahunter
@erratahunter
hunting silicon errata.
127.0.0.1Joined February 2026
About
Embedded systems engineer exploring the intersection of firmware reliability and AI tooling. I write about silicon errata, MCU quirks, and how modern AI/RAG pipelines can help engineers catch hardware bugs before they ship.
Available for
Nothing here yet.
erratahunter's blogs
Recently published
The Build Passed, So Why Doesn't It Run — Automating Firmware Tests on Real Hardware
Apr 15 · 28 min read · TL;DR A passing west build doesn't mean the firmware runs on hardware — catching silent failures manually doesn't scale. Combining Zephyr Twister's --device-testing mode with a self-hosted runner gi
Join discussion
How I Build Firmware with AI — A Research, Plan, Execute, Test Loop in Practice
Apr 11 · 15 min read · I expected AI coding tools to boost my productivity. Half right, half wrong. I develop Zephyr RTOS-based firmware for nRF52/nRF53 using Claude Code as my primary tool, and the first few weeks actually
Join discussion
Embedded Firmware Development with Claude Code — Devicetree, Kconfig, and Debugging
Mar 25 · 14 min read · TL;DR 75% of Zephyr firmware development time goes to Kconfig/devicetree configuration and build error interpretation, not writing code — Claude Code can intervene in that 75% directly from the termi
Join discussion
NCS Project Management Guide: Ditching Global Install to Reclaim Control
Mar 15 · 9 min read · TL;DR Patching SDK internals in an NCS global install silently breaks every other project on your machine. Freestanding (manual ZEPHYR_BASE binding) → T2 (app owns west.yml manifest) → T3 (separate
Join discussion