Now August 2026 · 3 days ago
Firmware's been done for months. The board hasn't.
On the bench
- SpotOn blocked
An nRF54L15 sensor node on Zephyr, sampling one ICM-42688-P at 1kHz and pulling modal features out of the impact window on-device.
Firmware and app are code-complete: FLASH 251,724 B, RAM 159,451 B, behind a CI gate that fails on 2% drift.
One milestone out of 87 is blocked, and it is the board order itself. Routing came back from the vendor this week at 0 unrouted and LVS pass, so there is a DRC-0 candidate. Three rework items went back.
R4 EVT · 0.8mm 4L · DRC 0
Industrial design
Battery door · CR1632
Assembly · 24mm across - harness-maker shipping
v0.45.1. The thing that reads a repo and builds that repo its own agent harness. 47,986 lines, 5,645 tests, 174 SPECs.
This month it turned out the review auto-fix loop was reproducing defects at roughly 1:1. Nine of thirty findings were introduced by an earlier round’s own fix. It now re-derives the model before it batches.
- EmbedEval published
v0.2.0. 267 firmware cases across Zephyr, ESP-IDF, STM32 and Yocto, scored through five layers that end in a real cross-compile.
Sonnet 5 scored 67.0% pass@1 against Sonnet 4.6’s 68.0%. On the 232 cases both models saw, that is 0.9 points down, which is a tie. A model generation went by with no measurable gain on embedded firmware.
Chewing on
Whether an LLM-driven improvement loop can keep a firmware codebase honest. Three times this month the answer came back that the check was wrong, not the code.
Open to
Conversations about making AI agents run as products on real embedded hardware: firmware code audits, reliability, and getting agents to behave on a hardware codebase.
contact@edgelog.dev