Exceptions - 2025.2 English - UG906

Vivado Design Suite User Guide: Design Analysis and Closure Techniques (UG906)
Document ID
UG906
Release Date
2025-12-10
Version
2025.2 English

This section contains detailed tables for each type of timing exception. You can access these tables through the links in the Summary table. The format of the detailed tables depends on whether the Coverage option has been selected or not.

Without Coverage Enabled

Figure 1. Report Exceptions: Detailed Table Without Coverage

The Position column shows the constraint's position number, matching the timing constraints editor (TCE).

Figure 2. Timing Exception Inside Timing Constraint Editor

To go to the corresponding constraint in the TCE, double-click a row or right-click the row and select View Constraint.

Figure 3. Report Exceptions Context Menu

The From, Through, and To columns display the original patterns used. The same patterns are reported inside TCE.

With Coverage Enabled

The following figure shows an example of a detailed table with the Coverage option selected inside the Report Exception GUI.

Figure 4. Report Exceptions: Detailed Table with Coverage

  • The From, Through, and To columns include clickable hyperlinks to the targeted objects (cells, nets, pins, ports, or clocks)
  • Press F4 to open the schematic after selecting one or more objects
  • Coverage-specific columns (From (%), Through (%), To (%)) show the percentage of objects actually affected
  • The Status column explains the state of the constraint, such as the following:
    • Invalid endpoint
    • Partially overridden
    • Non-existent path
    • Totally overridden
Note:
  • Vivado calculates coverage in the order: From → Through → To
  • If coverage is 0% at one level, all levels below it show 0%
  • A constraint with 0% coverage is considered invalid
  • Pins tied to VCC or GND are reported as invalid

Clock Groups

Figure 5. Detailed Table for Clock Groups

Clock group constraints are not defined using -from, -through, or -to, so their table format is different.

  • Each row lists a unique clock pair within the constraint
  • The same constraint can span multiple rows, depending on how many clock pairs are covered
  • All rows share the same Position value

The constraint position number 443 in the previous figure is defined as follows:

set_clock_groups -physically_exclusive -group RFSCLK -group LB_MD1SFSCLK

The constraint spans over two rows because some timing paths exist from clock RFSCLK to clock LB_MD1SFSCLK and from clock LB_MD1SFSCLK to clock RFSCLK.