ToolBB-0155

hardware-logging: crash-aware serial capture built for coding agents

The hwlog daemon in hardware-logging owns a board's serial port and records every session to disk, split by boot. It decodes ESP32 panics against ELF files archived at flash time and pauses capture while the flasher runs. Agents query it through bounded CLI commands or an MCP server. Other boards get generic capture; the README shows no hardware session.

Open original source github.com · Gurucharan Lingamallu

Claimed
Why this evidence label?

README text and a hero image; no hardware session shown.

How we check entries
Preview image for hardware-logging: crash-aware serial capture built for coding agents
The source's own preview image, from github.com.

Briefing

hwlog flash -- <cmd> takes an exclusive lease on the port, runs the board's own flasher and archives that build's ELF, against which later crash reports are decoded. hwlog wait --pattern then checks output since the flash and exits 0 on a match, 1 on a timeout and 2 on bad input. ESP-IDF and Arduino logs are parsed into timestamp, boot, level, tag and message, and --boot -1 returns everything since the last reboot.

It runs on macOS and Linux with Python 3.11. Summaries scan only the newest 16 MiB, storage defaults to 512 MiB per session, and output sent while the flasher holds the port is lost. The README says the tests simulate serial devices and that passing them is separate from validation on a board.

From the GitHub API

Repository facts

Repository facts for gurul/hardware-logging, from the GitHub API
Repositorygurul/hardware-logging
Stars2
LicenseMIT Permissive
LanguagePython
Last push3 Oct 2026 28 d ago

Tags

Board

Report a problem with this entry