User Manual

Reports Chapter 3. Concepts
each clock is analyzed in isolation, ignoring the relations between them. (For clocks which have no related
clocks, the result is the same as for part II.)
By necessity, the analysis in part III must make an approximation at the boundaries between clock domains,
and should not be interpreted as describing the actual behavior of the circuit. For this reason, part III is
disabled by default.
I/O Timing Report
The I/O Timing Report provides details on how well the synchronous portion
23
of the current design is
meeting timing on the selected device.
Timing analysis can be performed at several points in the flow, each time generating a different report. If
the design has not yet been routed, placement and/or routing are estimated.
This report is automatically generated by the Flow during any of the Run . . . Timing Analysis flow steps.
To generate this report manually, see the Tcl command run timing analysis.
Routing Report
The Routing Report collects a number of routing-related statistics and any related errors into an easily
readable report format.
This report is automatically generated by the Flow during the Run Route and Post-Process Design flow
steps.
To generate this report manually, see the Tcl command report routing.
Power Dissipation Report
The Power Dissipation Report shows various power-related statistics for the current design on the selected
Achronix device.
This report is not automatically generated by the Flow, but can be generated manually using the Tcl
command report power.
Multiprocess Summary Report
The Multiprocess Summary Report provides a comparative summary of the achieved frequencies
24
and
flow execution times for all Implementations executed from the Multiprocess view. This report will
be automatically shown in the ACE Editor Area as new results become available during Multiprocess
execution.
The Multiprocess Summary Report is generated/updated multiple times during a Multiprocess execution,
as new data becomes available from the executing Implementations. While the Multiprocess flow is still
executing, the report will contain incomplete results - rows containing incomplete data will be marked as
such.
If errors are encountered during flow execution for one of the selected Implementations, the row(s) of data
for that implementation will be marked accordingly.
Because the Multiprocess Summary Report summarizes the results of multiple Implementations (unlike the
other reports, which are generated for a single implementation), the HTML file containing the report is not
placed in any implementation’s report folder. Instead, this report is placed in the directory containing the
.acxprj ACE Project file, and is named multiprocess summary.html.
25
This report is only available in HTML format. There is no Tcl command available to generate this report
manually.
For more info on how this report is used, see Running Multiple Flows in Parallel and Attempting Likely
Optimizations Using Option Sets.
23
synchronous circuits are only found within the I/O Ring of ACX devices
24
if the ”Run Post-Route Timing Analysis” or ”Run Sign-off Timing Analysis” flow steps are enabled
25
Note that all implementations selected for execution within the Multiprocess View must come from a single Project; the directory
containing this project will also contain the Multiprocess Summary Report file.
233 http://www.achronix.com UG001 Rev. 5.0 - 5th December 2012