Understanding Reporting Differences - 2024.1 English

In the ISE Design Suite, reports are automatically generated when each application is run through the design flow. This includes but is not limited to the following:

• .syr for xst
• .bld for ngdbuild
• .mrp for map
• .par for par
• .twr for trce
• .pwr for xpwr

In the Vivado Design Suite, you can generate reports at any design stage. The benefits of on-demand report generation are:

Better runtime

You can better manage runtime by generating reports only when needed.

More available reports

At any point in the design flow, you can generate a report, making more reports available to you. For example, you can generate a utilization report for your design post-synthesis, post-optimization or post-route to see current information.

When you use Project Mode in the Vivado IDE, a fixed set of reports automatically generate that you can access from the Reports window.

When you use Non-Project Mode with Tcl commands or a script, you must add Tcl reporting commands to generate reports at stages where you require them while the design is in memory.

Specific report_* commands report different types of information, for example, utilization, timing, and DRC results. By default, the report output is sent to the tool transcript and the vivado.log file, but it can also be directed to a file. For a list of reports and their descriptions, type help -category report at the Tcl Command prompt.

The following table shows the relationship between ISE Design Suite report information and Vivado Design Suite reporting commands.