Skip to content

Build Gates (Stage 3)

Stage 3 runs Vivado through one generated script, build_all.tcl. This page explains what that script checks and what it refuses to build.

One entry point

build_all.tcl is the only Stage 3 entry. It creates the Vivado project from the files Stage 2 generated and nothing else. The board repository's own vivado_generate_project.tcl and vivado_build.tcl scripts are not staged and are not run. Do not run or edit them to build a generated design. To change what gets built, change the Stage 2 inputs and run the build again.

The script and its reports are in the board directory under your output folder (pcileech_datastore/output/<board>/ by default). The bitstream is copied into that directory's output/ folder.

Stage 2 inputs are checked

Stage 2 writes a manifest of the files Stage 3 may use, with a SHA-256 and size for each. Stage 3 refuses to start if:

  • the manifest is missing, unreadable or in an unsupported format;
  • the manifest was written for a different board than the one you asked to build;
  • any listed file is missing, empty or has changed since Stage 2 finished;
  • the staged IP memory files no longer match the generated data.

Stage 3 does not fall back to the stock board sources. If it refuses, rerun Stage 2 for the same board into the same output directory.

A rerun does not overwrite an earlier result. An existing output/ folder is renamed to previous-output-<id> before the new build starts.

Gates that must pass before the bitstream is written

After place and route (with post-route physical optimization), the script runs these checks. Any failure stops the build with an error and no bitstream is written.

Gate What it checks
Routed timing The timing summary reports that all user specified constraints are met, including pulse width. Worst setup and hold slack must be at least zero.
Clock coverage check_timing finds no unclocked or unconstrained internal endpoints and no partial input or output delays. Asynchronous board I/O such as PERST#, buttons and LEDs counts only if it is covered by a board false-path constraint.
DRC No DRC violation with severity Error or Critical Warning.
CDC Boards that ship a CDC checker run it on the routed design. It accepts only that board's known findings and fails on any new or missing one. Other boards fail on any Critical CDC finding.

The reports (timing_summary.rpt, clocks.rpt, cdc.rpt, drc.rpt, check_timing.rpt) are written to a reports/ folder next to build_all.tcl.

When a gate fails

  1. Read error_report.txt in your output folder (pcileech_datastore/output/ by default). It is the parsed summary. The full Vivado log is vivado_build.log in the same folder.
  2. Open the matching file in the board directory's reports/ folder.
  3. Fix the cause and rerun. build_all.tcl is regenerated on every build and checked against the manifest, so edits to it do not carry over.

Typical causes are listed in Vivado Setup.

Timing margin depends on placement. If you change the RTL for the 100T, rerun the build with several implementation directives and check the margin on each internal clock.

Vivado version

The generator does not pin a Vivado version for ordinary builds. The README states Vivado 2022.2 or newer. The one exception is a build that uses the requester startup guard on the CaptainDMA 100T, which requires Vivado 2026.1. See MSI-X and Requester Support.