Skip to content

FPGA flow

The Synthesis, Implementation and Bitstream pages run your vendor’s tools on the machine where your project is: AMD Vivado for Xilinx parts, and Intel Quartus Prime for Intel parts.

  • Target part: select Choose part… to search the parts and boards that your installed toolchain knows, on the Parts and Boards tabs. To use a part that isn’t listed, type its full name and choose Use “…” as the part.
  • Project toolchain: the vendor tool that builds the project, Vivado or Quartus Prime. If you have several versions installed, choose the one for this project here. A part from the other vendor changes the toolchain to match.

The assistant can also suggest a part, and set the target and toolchain for you after you approve.

Each page has the same inputs:

  • Sources: tick the design files the run uses. Select a file’s name to open it.
  • Constraints: tick the constraint files, .xdc for Vivado or .sdc for Quartus Prime.
  • Top module: the design’s top-level module.
  1. On Synthesis, select Run Synthesis.
  2. On Implementation, select Run Implementation. Implementation continues from the result of the last synthesis run, so run synthesis first.
  3. On Bitstream, with Generate selected, select Run Bitstream.

To run all three stages from your sources in one go, turn on Run Full Flow (synth → impl → bitstream) on the Bitstream page, then select Run Full Flow.

The tool’s output streams into the page while it runs. To stop a run, select Cancel.

When a run finishes, the page summarises it in its Report: resource use, timing and the warnings worth reading. Its Artifacts list the files it produced. Select a report or log there to open it in the editor. History lists earlier runs.

A design that misses timing still finishes, but its run is reported as failing timing.

Each run keeps its reports, and its bitstream, in its own folder under chipforge/runs/ in your project, so a later run can’t overwrite them. The bitstream is output.bit from Vivado, or chipforge.sof from Quartus Prime.

Add an IP’s .xci file to the run’s sources. If the IP’s generated files are missing or out of date, Chipforge prepares them in its own chipforge/work folder, without changing your IP files. If the IP was customised in a newer version of Vivado than the one building it, Chipforge stops and tells you which version to use.

To add IP to a project, see IP catalog.

  1. Connect the board to the machine where the companion runs: your computer, or your remote server.
  2. On the Bitstream page, select Program device.
  3. Select Use this build for the bitstream you built last, or Choose .bit… to pick a bitstream file.
  4. Choose your board from the list. If it isn’t there, select Rescan.
  5. Select Program.

Chipforge programs Xilinx boards with AMD’s hw_server and xsdb, and Intel boards with quartus_pgm. These come with Vivado and Quartus Prime. See Toolchains and simulators.