ID 683493
Date 11/06/2019
Public

## 1.3.2. Step 2: Identify Timing-Critical Design Blocks

Follow these steps to identify the timing-critical design blocks in the Intel® Quartus® Prime Timing Analyzer:
1. To open the Timing Analyzer, click Tools > Timing Analyzer .
2. In the Timing Analyzer, on the Tasks pane, double-click Update Timing Netlist to load the final timing netlist generated during the compilation.
Figure 5.  Timing Analyzer Tasks Pane
3. To run the report_timing.tcl script to identify any failing paths in the timing-critical design blocks, type the following command in the Console window. If not already visible, click View > Console in the Timing Analyzer to display the Console. The script runs commands to identify any failing paths.
source report_timing.tcl

The tcl script runs the report_timing command, capturing timing for the top 100 paths with the worst slack. The script is also preconfigured to capture timing between specific nodes for some of the design blocks. You analyze timing for these nodes later in this tutorial.

Figure 6.  Timing Analyzer Report Folders
Table 2.  Timing Analysis Reports that report_timing.tcl Generates
Timing Analysis Folder Generated For Timing Reports Show
inst_big u_big_partition1_top Analysis of top 100 paths with worst slack
inst_big_path1 u_big_partition1_top Analysis of timing between specific nodes
4. In the inst_big folder, right-click the Slow 900 mV 100C Model report, and then click Generate in All Corners. Repeat this step for the inst_i1, inst_i2, inst_i3, and inst_i4 folders.
5. View the Multi Corner Summary report that generates under each folder in the Report pane. Reports in red text in the inst_i3 and inst_i4 folders indicate timing-critical design blocks with failing paths.
6. Open the Multi Corner Summary report in the inst_i3 folder. Check the values in the From Node and To Node fields. Analysis indicates that the failing paths in u_blinking_led_i3 are in the 64-bit counter. This counter counts the number of cycles equivalent to 8s, where each cycle is of 1.818 ns.
Figure 7. Multi Corner Summary for u_blinking_led_i3
Note: Placement and routing results can vary by processor, OS, and software version.
7. Open the Multi Corner Summary report in the inst_i4 folder. Check the values in the From Node and To Node fields. Analysis indicates that the failing paths in u_blinking_led_i4 are in the 64-bit counter. This counter counts the number of cycles equivalent to 16s, where each cycle is of 1.818 ns.
Figure 8. Multi Corner Summary for u_blinking_led_i4
The timing analysis identifies u_blinking_led_i3 and u_blinking_led_i4 as timing-critical design blocks for optimization.