Vivado report
context.

FPGA report analysis, starting with the evidence.

FPGA implementation generates detailed reports covering timing, resource utilization, design-rule checks, power, and other implementation metrics. Silver recognizes and renders the following AMD Vivado report kinds to make these results easier to review.

Timing, DRC, methodology, power, route status, and utilization also have typed JSON models. Other recognized kinds are rendered without a typed model.

Action items are classified as blocking, functional risks, or quality suggestions. Unknown rules default to quality rather than being silently treated as informational. A green result is not Vivado sign-off.

Connect report findings to their source context.

Silver groups findings using the relationships available in parsed reports. Source file and line references appear only when source files are supplied and a match is found. The graph helps navigate report findings; it does not prove RTL root cause.

Compare FPGA implementation report snapshots.

Compare supported timing, utilization, and design-rule data across report snapshots. Stage labels are shown when available, and stage mismatches are called out. DRC occurrence-count changes can be reported as improvements or regressions.

Silver compares reports supplied by the user. It does not rerun Vivado or prove that an RTL or constraint edit caused a result change.

Monitor Vivado build progress from the desktop.

The Windows desktop widget can monitor a project's build progress using available logs and status files. Detected stages and failure details depend on the inputs produced by the build.

Review a watched build from a paired device.

Phone control is an optional desktop feature. It is disabled until enabled in the desktop tool and requires pairing. The phone can request analysis of the watched project and access only the permitted generated report artifacts. Network exposure and setup depend on the selected LAN or Tailscale mode.

Read the phone setup guide before enabling it. Plain HTTP on a local network does not protect traffic from other devices on that network.

Integrate report checks into your CI workflow.

The CI command parses supplied artifacts, applies configured baseline checks, returns a status code, and can write a Markdown pull-request comment. It does not launch Vivado.

vivado-report-ci <project-folder> --comment pr_comment.md

Configure the baseline and timing threshold for your project. Review the generated comment and status against the reports available in that run.