Skip to content
hw.dev
hw.dev/signal/siliconcompiler-run-listener-replay-debug-2026
SignalSiliconCompiler

SiliconCompiler Turns EDA Flow Failures Into Replayable Events

SiliconCompiler 0.38.11 adds run events, interactive node replay, and one configuration surface for debugging hardware builds as software pipelines.

Thesis connection

Event hooks and node replay shorten the path from a failed EDA step to a reproducible diagnosis, making silicon builds behave more like observable CI jobs.

#eda#tools#verification#software
Read Original

SiliconCompiler 0.38.11 makes an EDA flow observable at the same boundaries a CI system uses: run start, node start, node finish, and run end. Its new RunListener API lets external systems react to those events, while each node's replay script can reopen the failed step in a GUI, web viewer, or interactive shell.

Hardware build failures usually arrive as a directory full of logs plus a question about which tool state mattered. Node replay preserves the exact step and gives the engineer the native inspection surface without rerunning the whole graph. The new sc-config command also pulls cache cleanup, job-status email setup, settings, and file locations behind one interface. That is mundane infrastructure, but mundane infrastructure is what turns a collection of EDA executables into an operable build system.

Teams with multi-tool ASIC or FPGA flows should wire RunListener events into their existing CI telemetry and issue automation. The cost is a small integration. The payoff is replacing manual log archaeology with a reproducible failed node that another engineer can open directly.