13.8 Generating Timing Reports

The following sections describe how to generate timing reports.

13.8.1 Types of Reports

The following table lists the types of timing reports you can generate using SmartTime.
Table 13-3. Types of Timing Reports
ReportDescription
Timer ReportDisplays the timing information organized by clock domain.
Timing Violations ReportProvides information about constraint violations.
Bottleneck ReportDisplays points in the design that contribute to the most timing violations.
Datasheet ReportDescribes the characteristics of the pins, I/O technologies, and timing properties in the design.
Constraints Coverage ReportDisplays the overall coverage of the timing constraints set on the current design.
Combinational Loop ReportDisplays loops found during initialization.
Clock Domain Crossing ReportAnalyzes timing paths that cross from one clock domain (the source clock) to another clock domain (the destination clock).

13.8.2 Generating a Timing Report

The Timing Report allows you to determine whether timing problems exist in your design.

The Maximum Delay Analysis Timing Report lists the following information about your design:
  • Maximum delay from input I/O to output I/O
  • Maximum delay from input I/O to internal registers
  • Maximum delay from internal registers to output I/O
  • Maximum delays for each clock network
  • Maximum delays for interactions between clock networks

To generate a Timing Report:

  1. From the SmartTime Max/Min Delay Analysis View, choose Tools > Reports > Timer.
  2. Select the options you want to include in the report, and then click OK.
    The Timing Report appears in a separate window.

13.8.3 Understanding Timing Reports

The following table lists the sections in the Timing Report.

Table 13-4 13-5 13-6. Timing Report Sections
SectionDescription
HeaderLists the:
  • Report type
  • Version of Designer used to generate the report
  • Date and time the report was generated
  • General design information (name, family, and so on)
SummaryReports the timing information for each clock domain. By default, the clock domains reported are the explicit clock domains that are shown in SmartTime. To filter the domains and show only specific sections in the report, use the Timing Report Options dialog box.
PathLists the timing information for different types of paths in the design. This section is reported by default. You can deselect this option in the Timing Report Options dialog box.

By default, the number of paths displayed per set is 5. You can filter the domains using the Timing Report Options dialog box. You can also view the stored filter sets in the generated report using the Timing Report options. The filter sets are listed by name in their appropriate section. The number of paths reported for the filter set is the same as for the main sets. By default, the filter sets are not reported.

13.8.3.2 Register to Register Set

This set reports the paths from the registers clock pins to the registers data pins in the current clock domain.

13.8.3.3 External Setup Set

This set reports the paths from the top-level design input ports to the registers in the current clock domain.

13.8.3.4 Clock to Output Set

This set reports the paths from the registers clock pins to the top-level design output ports in the current clock domain.

13.8.3.5 Register to Asynchronous Set

This set reports the paths from registers to asynchronous control signals, such as asynchronous set/reset.

13.8.3.6 External Recovery Set

This set reports the external recovery check timing for asynchronous control signals, such as asynchronous set/reset.

13.8.3.7 Asynchronous to Register Set

This set reports the paths from asynchronous control signals, such as asynchronous set/reset, to registers.

13.8.3.8 Inter-clock Domain

This set reports the paths from the registers clock pins of the specified clock domain to the registers data pins in the current clock domain. Inter-domain paths are reported by default.

13.8.3.10 Input to Output Set

This set reports the paths from the top-level design input ports to the top-level design output ports.

13.8.3.11 Expanded Paths

Expanded paths can be reported for each set. By default, the number of expanded paths to report is set to 1. You can select and change the number when you specify Timing Report options.

Figure 13-21. Timing Report
???

13.8.4 Generating a Timing Violation Report

The Timing Violations Report provides a Flat Slack Report centered around constraint violations.

To generate Timing Violations Report:
  1. From the SmartTime Max/Min Delay Analysis View window, choose Tools > Reports > Timing Violations.
  2. Select the options you want to include in the report, and then click OK.
    The Timing Violations Report appears in a separate window.

13.8.5 Understanding Timing Violation Reports

The following figure shows an example of a Timing Violations Report.

Figure 13-22. Sample Timing Violation Report
???

The following table lists the sections in the Timing Violation Report.

Table 13-4 13-5 13-6. Timing Violation Report Sections
SectionDescription
HeaderThis section lists the:
  • Report type
  • Version of Designer used to generate the report
  • Date and time the report was generated
  • General design information (name, family, and so on)
PathsThis section lists the timing information for different types of paths in the design. The number of paths displayed is controlled by the following parameters:
  • A maximum slack threshold to report
  • A maximum number or path to report

By default, the slack threshold is 0 and the number of paths is limited. The default maximum number of paths reported is 100. All clocks domains are mixed in this report. The paths are listed by decreasing slack.

You can also choose to expand one or more paths. By default, no paths are expanded. For details, see the Timing Violation Report options.

13.8.6 Generating a Constraints Coverage Report

The Constraints Coverage Report contains information about the constraints in the design.

To generate a Constraints Coverage Report:
  1. From the SmartTime Max/Min Delay Analysis View, choose Tools > Reports > Constraints Coverage.
  2. Select the text format and number of unconstrained instances and click OK.
    The report appears in a separate window.

13.8.7 Understanding Constraints Coverage Reports

The Constraints Coverage Report shows the overall coverage of the timing constraints set on the current design. You can generate this report either from within Designer or within SmartTime Analyzer.

Figure 13-23. Sample Constraints Coverage Report
???

The following table lists the sections in the Constraints Coverage Report.

Table 13-4 13-5 13-6. Constraints Coverage Report Sections
SectionDescription
Coverage SummaryShows statistical information about the timing constraint in the design. For each type of timing checks (Setup, Recovery, Output, Hold, and Removal), it specifies how many are Met (there is a constraint and it is satisfied), Violated (there is a constraint and it is not satisfied), or Untested (no constraint was found).
Results by Clock DomainThis section provides a coverage summary for each clock domain.
Enhancement SuggestionsReports, per clock domain, a list of constraints that can be added to the design to improve the coverage. It also reports if some options impacting the coverage can be changed.
Detailed StatsProvides detailed suggestions about specific clocks or I/O ports that may require to be constrained for every pin/port that requires checks.

13.8.8 Generating a Bottleneck Report

To generate a Bottleneck Report:

From the SmartTime Max/Min Delay Analysis View, choose Tools > Reports > Bottleneck. The report appears in a separate window.

13.8.9 Understanding Bottleneck Reports—SmartFusion 2, IGLOO 2, RTG4, and PolarFire

A bottleneck is a point in the design that contributes to multiple timing violations. The Bottleneck Report lists the bottlenecks in the design. You can generate this report from SmartTime Analyzer.
Note: The bottleneck can be computed only when a cost type is defined. There are two cost type options available:
  • Path count: Associates the severity of the bottleneck to the count of violating/critical paths that traverse the instance.
  • Path cost: Associates the severity of the bottleneck to the sum of the timing violations for the violating/critical paths that traverse the instance.
Figure 13-24. Sample Bottleneck Report
???

The following table lists the sections in the Bottleneck Report.

Table 13-7. Bottleneck Report Sections
PartDescription
Device DescriptionContains general information about the design, including:
  • Design name
  • Family
  • Die
  • Package
  • Software version
Bottleneck Analysis

Lists the core of the bottleneck information. It is organized into two columns:

  • Instance Name: Refers to the output pin name of the instance.
  • Path Count: Shows the number of violating paths that include the instance pin.

13.8.10 Generating a Datasheet Report

The Datasheet Report shows information about a design’s external characteristics.

To generate a Datasheet Report:
  1. From the SmartTime Max/Min Delay Analysis View, choose Tools > Reports > Datasheet.
    The report appears in a separate window.

13.8.11 Understanding Datasheet Reports

The Datasheet Report displays the external characteristics of the design. You can generate this report from SmartTime Max/Min Delay Analysis View.

Figure 13-25. Sample Datasheet Report
???

The following table lists the tables in the Datasheet Report.

Table 13-8. Datasheet Report Tables
TableDescription
Pin DescriptionProvides the port name in the netlist, location on the package, type of port, and I/O technology assigned to it. Types can be input, output, or clock. Clock ports are ports shown as "clock" in the Clock domain browser.
DC Electrical CharacteristicsProvides the parameters of the different I/O technologies used in the design. The number of parameters displayed depends on the family for which you have created the design.
AC Electrical CharacteristicsProvides the timing properties of the design ports

For each clock, this section includes the maximum frequency. For each input, it includes the external setup, external hold, external recovery, and external removal for every clock where it applies. For each output, it includes the clock-to-out propagation time. This section also displays the input-to-output propagation time for combinational paths.

13.8.12 Generating a Combinational Loop Report

The Combinational Loop Report shows all loops found during initialization and reports pins associated with the loop(s) and the location where a loop is broken.

To generate a Combinational Loop Report:
  1. From the Tools menu, choose Reports > Combinational Loops.
    The Combinational_Loops Report Options dialog box appears.
  2. Select either Plain Text or Comma Separated Values.
  3. Click OK.

13.8.13 Understanding Combinational Loop Reports

The Combinational Loop Report shows all loops found during initialization, reports the pins associated with the loops, and identifies the locations where loops are broken.

Figure 13-26. Sample Combinational Loop Report
???

13.8.14 Generating a Clock Domain Crossing (CDC) Report

The Clock Domain Crossing (CDC) Report analyzes timing paths that cross from one clock domain (the source clock) to another clock domain (the destination clock). The CDC Report helps identify instances where there may be data loss or metastability issues.

To generate the CDC Report:
  1. From the Tools menu, choose Reports > Clock Domain Crossing (CDC)..
    The Clock Domain Crossing Report Options dialog box appears.
  2. Select either CDC Table or Comma Separated Values.
  3. Click OK.

    Selecting CDC Table displays a graphical table with color-coded cells. Each cell represents a CDC type between the source clock and the destination clock domains that have constraints. Clocks without constraints do not appear in the CDC table.

    The attributes present in the path table are as follows:

    • Source Clock: Source of the clock

    • Destination Clock: Destination of the clock

    • Worst Slack (ns): Worst slack of the CDC path in nanoseconds

    • Worst Slack Edge: Source/sink edge for the worst path of CDC

    • Max Delay Cstr: See the following table.

      ValueDescription

      Yes

      All paths in CDC have set_max_delay applied

      No

      No paths in CDC have the constraints applied

      Partial

      Any path in CDC has the constraint applied

    • Multicycle Path Cstr: see the following table.

      ValueDescription

      Yes

      All paths in CDC have set_multicycle_path applied

      No

      No paths in CDC have the constraints applied

      Partial

      Any path in CDC has the constraint applied

    • Clock Group Cstr: See the following table.

      ValueDescription

      Yes

      CDC has set_clock_group applied

      No

      CDC does not have set_clock_group applied

    • Clock Uncertainty Cstr: Uncertainty value for the worst path in CDC; otherwise, the clock uncertainty field is left empty.

    • Num of Paths: Number of paths in CDC. For User Ignored paths, the value is 0.

    • Clock Pair Status: Status can be Timed Safe, Timed Unsafe or User Ignored.

    In the CDC Report dialog box, you can select the clocks to view or hide. Clicking the Clock Selection button at the top left of the dialog box lists all clocks that can be viewed or hidden. By default, all clocks are checked and visible. To hide a clock, clear its check box.

    Figure 13-27. Showing or Hiding Clocks
    ???

    The following table describes the colors in the CDC Report shown in the preceding figure.

    PatternStatusColor
    Paths from the source clock domain to the destination clock domain have all been disabled by false path or clock group constraints.User-Ignored PathsLight blue
    No Paths found from the source clock domain to the destination clock domain.No PathsGray
    The source and destination clocks are synchronous: Both the clocks have a common primary clock and paths are found from the source clock domain to the destination clock domain.TimedDark Blue
    The source and destination clocks are asynchronous: Both the clocks have NO common primary clock, while paths are found from the source clock domain to the destination clock domain. Currently, synchronizers, if present, are not accounted for in this report.Timed (unsafe)Brown

    There are certain scenarios related to the path table as explained in the following:

    1. When CDC Report is generated, path table is shown by default for all CDC having paths. Each row shows the worst slack for a clock crossing. Similarly, when clicking on a particular CDC crossing in CDC Report, you can have a single row showing the worst slack for CDC crossing.

      Example: The path table shown in the following figure, the worst path for reg_com_clk_10mhz to reg_com_clk_5mhz has the worst slack of 93.541. The same path is displayed by default, when the CDC crossing is selected.

      Figure 13-28. Worst Path with Slack 93.541 ns
      Figure 13-29. Smarttime Showing the Worst Path with Slack 93.541 ns
    2. Clicking on the CDC box shows the worst slack for a clock crossing as in path table in the following figure.

      Figure 13-30. Highlighted CDC Box Showing the Worst Slack in Path Table

      Clicking on the same CDC box again shows details for all the clocks selected in the CDC Report.

      Figure 13-31. CDC Path Table Showing All Clocks on Deselecting the Selected CDC Box

      For all clocks having large names, tool-tips for columns have been added.

      Figure 13-32. CDC Path Table Showing Tool-Tip for a Source Clock Name
    3. Selecting/deselecting clocks in clock selection dynamically changes the path table along with the CDC table. Both the tables are in sync. Example: Here, clk_input_100mhz is selected, therefore, the clock is displayed in CDC table and path table.

      Figure 13-33. CDC Table in Sync with Clock Selection Section

      When the clock clk_input_100mhz is unselected, then the same clock is removed from the CDC table. The crossings related to the clock are also removed from the path table as shown in the following figure.

      Figure 13-34. Deselecting a Clock in Clock Selection Section Syncs the Path Table Accordingly

    After clicking any one of the four options in the CDC category, the clock table is filtered according to the CDC category selected.

    In the following scenario, the Timed button has been selected and Timed safe CDC is displayed only in the clock table.

    Figure 13-35. CDC Report When Timed Button is Selected in CDC Category
    Clicking on the same CDC category shows the details for all the clocks selected in CDC Report. Selecting/unselecting clocks in clock selection does dynamically change the clock table along with the CDC table.

    In the following figure, the User Ignored CDC category button is chosen and clk_input_100mhz is selected. Therefore, the clock is displayed in CDC table and clock table.

    Now, when clock clk_input_100mhz is unselected, the same clock is moved from CDC table and the crossings related to that clock are also removed from clock table. Therefore, when the User Ignored CDC category is selected, entries related to clk_input_100mhz are not visible.

    After right-clicking a CDC box, you can choose to Copy, Add a Clock Group Constraint or Go to Timing Explorer.

    Figure 13-36. CDC Report with Go to Timing Explorer Option

    Selecting the Go to Timing Explorer option opens the Timing Explorer dialog box.

    Figure 13-37. Timing Report Explorer

    There are corner scenarios when cross probing between CDC and Timing Explorer:

    Scenario 1:

    This is a scenario where difference is seen between SmartTime and Verify timing, when two clocks are defined on same port and when cross probing for CDC reg_com_clk_10mhz and reg_com_clk_5mhz is unable to find the same in Timing Report Explorer.

    The constraints are as follows:

     create_clock -name {reg_com_clk_10mhz} -period 100 -waveform {0 50 } [ get_ports { reg_com_clk_10mhz } ]
    create_clock -name {reg_com_clk_5mhz} -period 200 -waveform {0 100 } -add [ get_ports { reg_com_clk_10mhz } ]

    The Timing Report Explorer does not pick reg_com_clk_5mhz as destination clock, and Smart time does pick the reg_com_clk_10mhz and reg_com_clk_5mhz pair as CDC, as shown in the following figure.

    Figure 13-38. Timing Report Explorer Snapshot - 1
    Figure 13-39. Timing Report Explorer Snapshot - 2
    Figure 13-40. SmartTime Snapshot
    Timing Explorer is picking the worst slack path for a pair of start and end point. Therefore, you can miss CDC and other reg to reg paths with lower slack values.

    Scenario 2:

    This is a scenario where due to different operating conditions set in Smart Time, you can have different results, when cross probing between CDC and Timing Report Explorer. SmartTime and CDC are in sync.

    Figure 13-41. Worst Slack of 97.958 ns in Timing Report Explorer
    Figure 13-42. Worst Slack of 98.154 ns in SmartTime
    Figure 13-43. Operating Conditions
    The Timing Report Explorer reports the path from slow_lv_lt, and SmartTime reports using the operating condition fast_hv_lt. When the operating condition in SmartTime is changed to slow_lv_lt, the worst slack becomes the same as in the Timing Report Explorer.
    Figure 13-44. Slack After Changing the Operating Condition to slow_lv_lt

    CDC Reports worst path for a particular corner selected in SmartTime, and Timing Report Explorer reports the worst path across all the corners.

    In such cases, you can see changes in values when navigating from CDC to Timing Report Explorer. To make you aware of such situations, Corner Info column is added to display the operating conditions.

    Note:
    • The path details for the same clock crossing (C1 to C1) are not shown in the path tale as they are not valid clock crossings and are currently shown as timed safe by default in CDC Report.

    • The clock table has CDC details only related to clocks checked in clock selection from CDC Report.

    • Path table will not show any CDC having no paths.

    • For User Ignored CDC columns, “Worst Slack (ns)”, “Worst Slack Edge”, “Max Delay Cstr”, “Multicycle Path Cstr”, and “Clock Uncertainty Cstr” are empty.

    • Cross probing is allowed to Timing Report Explorer for the same clock crossing (C1 to C1).
    • For User Ignored CDC category, Corner Info column is empty.

    Selecting Comma Separated Value exports the CDC Report to a CSV file. If you select this option, a window appears in which you assign a name to the CSV file and specify the location where it will be exported. The CSV file shows details about the CDC between each clock domain in numeric format. Each CDC type is represented as a number similar to colors in the table. The CSV file includes an explanation of each number type and CDC type.

    Figure 13-45. Sample CSV Report
    ???