跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
法律与合规

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 · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add adeleempurpled290/FPGA-Agent-skills --skill vivado-analysis

技能说明


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 TypeSource ClockData PathDestination Clock
Setup/Recovery (max delay)Slow_maxSlow_maxSlow_min
Setup/Recovery (max delay)Fast_maxFast_maxFast_min
Hold/Removal (min delay)Slow_minSlow_minSlow_max
Hold/Removal (min delay)Fast_minFast_minFast_max

Key rule: Delays from different corners are NEVER mixed on same path during slack calculation.

Report Selection Guide

GoalCommandWhen to Use
Quick timing signoffreport_timing_summaryAfter implementation, mandatory before bitstream
Analyze specific pathsreport_timing -from/-to/-throughDebugging specific failing paths
Overall QoR score (1-5)report_qor_assessmentAfter routing, assess closure likelihood
Auto optimization hintsreport_qor_suggestionsWhen stuck on timing closure
Path characteristicsreport_design_analysisDeep analysis of logic levels, fanout, physical spread
Methodology compliancereport_methodologyEarly in flow to catch methodology violations
Resource usagereport_utilizationAfter synthesis or implementation
CDC checksreport_cdcAfter synthesis, verify clock domain crossings
Congestion analysisreport_design_analysis -congestionAfter placement, if timing degraded
Design rule checksreport_drcBefore bitstream generation
Bus skewreport_bus_skewIf set_bus_skew constraints exist (NOT in report_timing_summary)

Timing Report Header Fields

FieldMeaning
SlackPositive = meets timing. Negative = violation
SourceStartpoint cell + launch clock (edge, name, period)
DestinationEndpoint cell + capture clock (edge, name, period)
Path GroupClock group containing endpoint (async pins → async_default)
Path TypeMax (setup/recovery) or Min (hold/removal); corner (Slow/Fast)
RequirementClock period (same clock) or smallest positive delta (different clocks)
Data Path DelayTotal delay through logic section
Logic LevelsCount of each primitive type in data path
Clock Path SkewDestination - Source insertion delay + CPR
CPRClock Pessimism Removal — shared clock circuitry correction
Clock UncertaintyTSJ + TIJ + DJ + PE + UU (see below)

Clock Uncertainty Components

ComponentSource
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

ValueMeaning
UnplacedCell not placed, delay estimated
EstimatedCell placed but not routed
RoutedFinal routed delay

Clock Phase Shift Mode (Device Defaults)

Device FamilyDefault ModeBehavior
7 SeriesWAVEFORMModifies clock waveform edges
UltraScaleWAVEFORMModifies clock waveform edges
UltraScale+LATENCYModels as MMCM/PLL insertion delay
VersalLATENCYModels 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

ScoreInterpretationAction
1Design will likely NOT complete implementationMajor redesign needed
2Will complete but will NOT meet ti
阅读完整来源 ↗