Users invoke these DRCs using the Vivado DRC interface like the built-in DRCs. Results are provided in tabular form in the GUI with hyperlinks to design elements related to potential isolation violations. The VIV DRCs also contribute to the text-based output of the Vivado DRC reporting system.
Each line can be selected for additional detail in the Design Rule Properties window. Design objects associated with the DRC are automatically highlighted in the Device and Package windows.
report_drc -verbose -checks {IDF_VIV2-1 IDF_VIV2-2 IDF_VIV2-3
IDF_VIV2-4 IDF_VIV2-5 IDF_VIV2-6}
DRCs can be invoked at several stages of the flow. Some IDF DRCs can be run on the design constraints. IDF DRCs (for the implemented design) can be run after the design is implemented.
- IDF_VIV2-1 is a provenance DRC and can be run at any time in the flow.
- IDF_VIV2-2, IDF_VIV2-3 & IDF_VIV2-4 can be run once synthesis has been performed.
- IDF_VIV2-5 and IDF_VIV2-6 examine the implementation, thus the Implementation step must be completed for IDF_VIV2-5 and IDF_VIV2-6 to have something to check.
An example DRC report in the Vivado GUI is shown in the following figure.
The text of the violation is displayed in two places in the GUI. The first line of the text is displayed in the DRC report table as shown in the previous figure. The complete text along with links to the sites associated with the violation, are displayed in the Details pane of the Violation Properties window as shown in the following figure.
set_param drc.maxReportedNames 9999
set_param
drc.maxReportedChars 9999