You can use the report_exceptions
-write_valid_exceptions command to export only the timing exceptions that
cover at least one valid timing path. This export includes the following:
- Only valid startpoint and endpoint pins
- Expanded object collections, as resolved in memory by the Vivado timer
- Constraints that are actively applied to timing paths
Usage Notes
- The export excludes timing constraints created with
set_clock_groupsandset_bus_skew. - Use this report with the coverage report (
-coverage) to refine the object patterns used in your timing exceptions. - This helps ensure your constraints are both effective and targeted to meaningful paths.
Example
The following figure illustrates report_exceptions -write_valid_exceptions from the case described in
Reporting the Ignored Objects, where two
set_false_path constraints were applied:
Figure 1. Valid Exceptions
