System requirements
Desktop app
Section titled “Desktop app”| Windows | macOS | Linux | |
|---|---|---|---|
| Processor | 64-bit x86 (Intel or AMD) | Apple silicon | 64-bit x86 (Intel or AMD) |
| Operating system | Windows 10 or later | macOS 12 Monterey or later | Ubuntu 22.04 or later, Debian 12 or later |
| Installer | .exe or .msi |
.dmg |
.deb |
The desktop app also needs:
- A web browser, set as your default, to sign in.
- Your system’s keychain, where Chipforge keeps the key to your saved sign-in: Credential Manager on Windows, Keychain on macOS, and a Secret Service keyring such as GNOME Keyring or KWallet on Linux. On Linux, Chipforge doesn’t start without one.
- On Windows, the Microsoft Edge WebView2 Runtime. The installer adds it if it’s missing.
- On Linux, polkit, so that you can approve installing updates.
aptinstalls it with Chipforge. - Access to the Chipforge service. See Network requirements.
There are no Chipforge installers for Macs with Intel processors, for Linux distributions that don’t use .deb packages, or for Arm-based Windows and Linux computers.
Remote EDA server
Section titled “Remote EDA server”To run your designs on a Linux server, the server needs:
- Linux on 64-bit x86.
- An OpenSSH server that lets users forward a connection to a Unix socket. That’s the default. It’s turned off by
AllowStreamLocalForwarding noorremote, orDisableForwarding yes, insshd_config, and byrestrictorno-port-forwardingon a key inauthorized_keys. - SSH key login for each engineer that works without a password or one-time-code prompt, so that Chipforge can open the connection for you. Engineers who must type a password can open the connection themselves instead.
systemdwith user services, recommended to keep the companion running when you log out.- Your EDA tools and access to their licences.
Each engineer’s computer needs an OpenSSH client (ssh). See Work on a remote EDA server.
EDA tools
Section titled “EDA tools”Chipforge doesn’t include any EDA tools: it runs the ones installed on the machine where your designs run. It works with these:
| Tool | Chipforge uses it for | Notes |
|---|---|---|
| AMD Vivado | Synthesis, implementation, bitstreams, the IP catalog, simulation with xsim, and programming Xilinx boards | Not available for macOS. To program boards only, Vivado Lab or the Hardware Server is enough. |
| Intel Quartus Prime Standard or Lite | Synthesis, fitting and bitstreams (.sof) |
Not available for macOS. |
| Intel Quartus Prime (any edition) or the Quartus Prime Programmer | Programming Intel boards | Not available for macOS. |
| Icarus Verilog | Simulation | vvp must be installed with it. |
| Verilator | Simulation | Version 5.0 or newer, with g++ or clang++. Not available natively on Windows. |
| Questa or ModelSim, including the editions that come with Quartus | Simulation | vlog and vlib must be beside vsim. |
| Cadence Xcelium | Simulation | Linux only. |
| Synopsys VCS | Simulation | Linux only. |
Chipforge doesn’t require a particular version of Vivado or Quartus Prime. Verilator is the only tool with a minimum version.
For how Chipforge finds these tools and how to point it at yours, see Toolchains and simulators.