Skip to content

Chipforge 0.5.4

Released on 2026-10-13.

Chipforge 0.5.4 is the first production release. This page summarises what it contains.

  • The desktop app for Windows on x64, macOS on Apple silicon, and Linux on x64 as a .deb package. Most installers include the companion, which runs your EDA tools and works with your project files on your computer.
  • Remote EDA servers. Run the companion on a Linux server and connect the app to it over SSH. Chipforge can open and watch the SSH connection for you, and reconnects when it drops.
    • Move files between your computer and a project on the server. In the Explorer, use the upload button, Upload Files… on a folder, or drag files onto the file tree. To download a file, right-click it and choose Download.
    • The assistant can run commands on the server after you approve them. The approval card names the server: “Run a shell command on ….” The server needs companion 0.3.3 or later.
  • Sign-in in your web browser, with the account from your invitation.
  • Projects in ordinary folders, on your computer or on a server. The Projects page shows the state of each project and which machine it’s on, when that isn’t the one you’re connected to.
    • Names you give new, renamed or uploaded files and folders may use only A–Z, a–z, digits, ., _ and -, can’t start with - or end with ., and can’t be a reserved Windows name such as CON, because other names break EDA tools. Chipforge explains what to change. Existing files keep their names, but a run is refused, with the reason, if a path would break the tool it uses.
    • When a project folder’s path stops some tools from working, Chipforge names them and suggests where to move it. A folder that no tool can work in can’t be attached.
  • Planning with the assistant. Describe your design and answer the assistant’s questions. It proposes a plan with its modules, a block diagram and a test plan, and builds only after you approve it.
    • Approving a plan saves a readable copy to docs/PLAN.md and opens it on the Design page. Projects that already have chipforge/plan.md, or a docs/PLAN.md you wrote, keep using chipforge/plan.md.
    • After the plan is approved, the assistant tries to log the changes you agree in docs/PLAN-CHANGES.md.
  • Building with the assistant, in Manual or Auto mode. The assistant writes RTL and testbenches, and runs your tools. In Manual mode it asks your approval before edits, runs and commands; in Auto mode it edits files and runs lint and simulations without asking. You can undo the changes a run made.
    • Once a chat is about half full, a ring in the message box shows how much room is left.
    • When a chat runs out of room, the assistant writes a short handover and offers Continue in new chat, which carries the handover into a new chat in the same project.
  • Simulation with the Vivado simulator (xsim), Icarus Verilog, Verilator, Questa or ModelSim, Cadence Xcelium and Synopsys VCS.
    • Each project has its own simulator. Choose it on the Simulation page, and the assistant uses it too, unless you or the plan name a different simulator. When a project has no simulator chosen, Chipforge uses the Vivado simulator (xsim) if this machine can run it, otherwise another installed simulator.
    • If your machine doesn’t have the project’s simulator, Chipforge runs one that is installed and tells you which: This project uses …, which isn't available on this machine — running with … instead.
    • Each simulation run keeps its report, log and waveform together in one folder under chipforge/runs/.
  • A waveform viewer for VCD and FST files that opens large waveforms quickly.
    • Markers: press M to add one at the cursor, or Shift+click a trace. The time axis shows the span between neighbouring markers and the cursor.
    • Step the cursor to the previous or next change of the selected signal with ← and →.
    • Choose each bus’s radix from its right-click menu: Hexadecimal, Binary, Octal, Unsigned decimal, Signed decimal or ASCII. In hexadecimal, binary and octal, partly unknown values keep their known digits.
    • Ctrl+wheel and pinch zoom around the pointer, and horizontal swipes and Shift+wheel pan.
    • A time scrollbar under the waveform shows the whole trace. Drag it, or click it to jump.
    • Signal names show over the trace while the signal list is closed. Press ? to see every waveform shortcut.
  • Synthesis, implementation and bitstream generation with AMD Vivado or Intel Quartus Prime, with a picker for your target part or board, and a report for each run.
    • Designs that use Vivado IP synthesise. Chipforge prepares the IP in its own chipforge/work folder without changing your IP files, and explains when an IP was customised in a newer Vivado than the one you build with.
    • Reports, logs and other text outputs of a run open in the editor, listed under the run that wrote them.
  • Board programming for Xilinx and Intel boards.
  • An IP catalog for browsing the Vivado IP catalog and generating cores into your project, with your own tags and notes on each IP.
  • A terminal in your project folder, on your computer or on your remote server.
  • Toolchain settings to point Chipforge at your tools and set licence variables, in Settings → Local Toolchains.
  • Updates. Chipforge checks for updates in the background while it runs, and from Settings → Updates. When an update has downloaded, an Update ready button appears in the top bar; the update installs when you quit.