vivado-analysis
Use this skill when the user needs help with Vivado design analysis, timing report interpretation, or timing closure. This includes report_timing interpretation (slack calculation, path analysis, clock skew/uncertainty), report_timing_summary signoff verification, report_qor_assessment (QoR scoring 1-5, assessment categories), report_qor_suggestions (automated optimization suggestions, .rqs workflow), report_design_analysis (timing path characteristics, complexity/Rent analysis, congestion analysis), report_methodology (design rule compliance), report_utilization (resource usage analysis), report_cdc (clock domain crossing checks), report_drc (design rule checks), report_bus_skew, timing closure strategies (setup/hold violation resolution, congestion mitigation), message severity management, and design check waivers. This skill provides analysis and interpretation knowledge — for TCL command execution use vivado-tcl, for constraint modifications use vivado-constraints, for implementati
adeleempurpled290 · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add adeleempurpled290/FPGA-Agent-skills --skill vivado-analysisAbout this skill
name: vivado-analysis description: Use this skill when the user needs help with Vivado design analysis, timing report interpretation, or timing closure. This includes report_timing interpretation (slack calculation, path analysis, clock skew/uncertainty), report_timing_summary signoff verification, report_qor_assessment (QoR scoring 1-5, assessment categories), report_qor_suggestions (automated optimization suggestions, .rqs workflow), report_design_analysis (timing path characteristics, complexity/Rent analysis, congestion analysis), report_methodology (design rule compliance), report_utilization (resource usage analysis), report_cdc (clock domain crossing checks), report_drc (design rule checks), report_bus_skew, timing closure strategies (setup/hold violation resolution, congestion mitigation), message severity management, and design check waivers. This skill provides analysis and interpretation knowledge — for TCL command execution use vivado-tcl, for constraint modifications use vivado-constraints, for implementation strategy changes use vivado-impl.
Vivado Design Analysis & Timing Closure Guide
Based on UG906 (v2025.2). This skill helps interpret analysis reports and make timing closure decisions. For complete command syntax, see REFERENCE.md. For TCL execution, use vivado-tcl. For constraint changes, use vivado-constraints. For implementation strategies, use vivado-impl.
Timing Path Fundamentals
Four common path types:
1. Input Port → Register (constrained by set_input_delay)
2. Register → Register (constrained by clock period)
3. Register → Output Port (constrained by set_output_delay)
4. Input Port → Output Port (combinational, set_max_delay)
Path structure (three sections):
Source Clock Path → Data Path → Destination Clock Path
(clock source (launch pin (clock source
to launch cell) to capture to capture
cell input) cell)
Slack formula:
- Max delay (Setup/Recovery):
slack = data_required_time - data_arrival_time - Min delay (Hold/Removal):
slack = data_arrival_time - data_required_time
Max/Min Delay Analysis Corner Selection
| Analysis Type | Source Clock | Data Path | Destination Clock |
|---|---|---|---|
| Setup/Recovery (max delay) | Slow_max | Slow_max | Slow_min |
| Setup/Recovery (max delay) | Fast_max | Fast_max | Fast_min |
| Hold/Removal (min delay) | Slow_min | Slow_min | Slow_max |
| Hold/Removal (min delay) | Fast_min | Fast_min | Fast_max |
Key rule: Delays from different corners are NEVER mixed on same path during slack calculation.
Report Selection Guide
| Goal | Command | When to Use |
|---|---|---|
| Quick timing signoff | report_timing_summary | After implementation, mandatory before bitstream |
| Analyze specific paths | report_timing -from/-to/-through | Debugging specific failing paths |
| Overall QoR score (1-5) | report_qor_assessment | After routing, assess closure likelihood |
| Auto optimization hints | report_qor_suggestions | When stuck on timing closure |
| Path characteristics | report_design_analysis | Deep analysis of logic levels, fanout, physical spread |
| Methodology compliance | report_methodology | Early in flow to catch methodology violations |
| Resource usage | report_utilization | After synthesis or implementation |
| CDC checks | report_cdc | After synthesis, verify clock domain crossings |
| Congestion analysis | report_design_analysis -congestion | After placement, if timing degraded |
| Design rule checks | report_drc | Before bitstream generation |
| Bus skew | report_bus_skew | If set_bus_skew constraints exist (NOT in report_timing_summary) |
Timing Report Header Fields
| Field | Meaning |
|---|---|
| Slack | Positive = meets timing. Negative = violation |
| Source | Startpoint cell + launch clock (edge, name, period) |
| Destination | Endpoint cell + capture clock (edge, name, period) |
| Path Group | Clock group containing endpoint (async pins → async_default) |
| Path Type | Max (setup/recovery) or Min (hold/removal); corner (Slow/Fast) |
| Requirement | Clock period (same clock) or smallest positive delta (different clocks) |
| Data Path Delay | Total delay through logic section |
| Logic Levels | Count of each primitive type in data path |
| Clock Path Skew | Destination - Source insertion delay + CPR |
| CPR | Clock Pessimism Removal — shared clock circuitry correction |
| Clock Uncertainty | TSJ + TIJ + DJ + PE + UU (see below) |
Clock Uncertainty Components
| Component | Source |
|---|---|
| TSJ (Total System Jitter) | Combined system jitter on both clocks |
| TIJ (Total Input Jitter) | From set_input_jitter constraint |
| DJ (Discrete Jitter) | Hardware primitives (MMCM/PLL) |
| PE (Phase Error) | Phase variation between clock signals |
| UU (User Uncertainty) | From set_clock_uncertainty constraint |
Delay Type in Path Details
| Value | Meaning |
|---|---|
| Unplaced | Cell not placed, delay estimated |
| Estimated | Cell placed but not routed |
| Routed | Final routed delay |
Clock Phase Shift Mode (Device Defaults)
| Device Family | Default Mode | Behavior |
|---|---|---|
| 7 Series | WAVEFORM | Modifies clock waveform edges |
| UltraScale | WAVEFORM | Modifies clock waveform edges |
| UltraScale+ | LATENCY | Models as MMCM/PLL insertion delay |
| Versal | LATENCY | Models as MMCM/PLL insertion delay |
Warning: Migrating 7 Series/UltraScale designs to UltraScale+ changes phase shift modeling. Review and remove legacy multicycle path constraints used for phase shift.
QoR Assessment Interpretation (report_qor_assessment)
Score Meaning
| Score | Interpretation | Action |
|---|---|---|
| 1 | Design will likely NOT complete implementation | Major redesign needed |
| 2 | Will complete but will NOT meet ti |