patch notes · unreleased

Build without device-file output redirection

CLI simulation keeps stdout live and filters stderr from a temporary file after make returns, preserving its exit status. Editor diagnostics use a merged pipe for absolute paths. Frame conversion writes its normal output filename directly. This removes the /dev/fd and /dev/stdout dependency that prevented validation in restricted execution environments; no permissions were changed. Simulation stderr is now delivered when make completes, rather than streamed during execution.

The installed editor task's command and environment were invoked on the nested multi-file Working Lab fixture. Simulation passed; build produced a 2.2 MB bitstream and passed timing. Programming reached openFPGALoader and returned board-not-found. This validates the command path, not a GUI keystroke or physical board behavior. Failing-testbench and simulation-timeout regressions both passed.

Follow-up: probes 96 and 96b now pass all four stages through the unmodified probe runner and the actual CLI, without manually invoking intermediate stages. This closes their earlier restricted-environment validation gap, not physical board acceptance.

previous: Editor tasks find the installed Homebrew tools; Distinguish programmer access from macOS USB visibility
next: Your own project, from editor to board
This entry in the full list
Every SystemVerilog construct measured so far, next to what Vivado does: the probes, stage by stage