Page 2
Altera warrants performance of its semiconductor products to current specifications in accordance with Altera's standard warranty, but reserves the right to make changes to any products and services at any time without notice. Altera assumes no responsibility or liability arising out of the application or use of any information, product, or service described herein except as expressly agreed to in writing by Altera Corporation.
1. About this Tutorial This tutorial describes the steps to constrain and perform static timing analysis with the TimeQuest Timing Analyzer. For this tutorial, use the fir_filter design that ships with the Quartus ® II software. Figure 1–1 shows the fir_filter design schematic.
6.0. APEX, FLEX, and Mercury device families are not supported. Procedures Use the following steps to constrain and analyze a design with the TimeQuest Timing Analyzer. Each step includes the GUI procedure and the command-line equivalent. Step 1: Open and Setup Your Design in the Quartus II Software In the Quartus II software, browse to and open the fir_filter located in the <qdesign folder>/fir_filter/ folder.
You can also create a post-fit netlist for the initial database. However, creating a post-map is less time consuming and is sufficient for this tutorial example. Step 4: Launch the TimeQuest Timing Analyzer Launch the TimeQuest Timing Analyzer to create and verify all timing constraints and exceptions with the procedures in Table 2–4.
Create the clocks in the fir_filter design and assign the proper clock ports with the procedures in Table 2–7. For more information about constraints supported by the TimeQuest Timing Analyzer, refer to the TimeQuest Timing Analyzer chapter in volume 3 of the Quartus II Handbook.
Table 2–9. Constraints that have been specified with the TimeQuest Timing Analyzer GUI or in the console are not automatically saved. If you inadvertently overwrite any of your constraints later in the design flow, use this initial SDC file to restore all of your constraints.
Table 2–10. The TimeQuest Timing Analyzer provides easy to use report generation commands that allow you to verify all timing requirements in the design. Table 2–10. Report SDC Command...
Page 12
Declare the paths from clk to clkx2 as false paths with the procedures in Table 2–13. When you complete this procedure, the TimeQuest Timing Analyzer indicates that the Clock Transfers report is outdated. Table 2–13. Declaring False Paths...
After you enter the set_false_path in the GUI, all generated report panels are labeled “Out of Date,” indicating that the report panels do not contain results that reflects the current state of constraints or exceptions in the TimeQuest Timing Analyzer. To update the report panels, you must regenerate all of the reports.
Step 12. Verify Timing in the TimeQuest Timing Analyzer To obtain detailed timing analysis data on specific paths, view timing analysis results in the TimeQuest Timing Analyzer. After a full place-and-route is performed, launch the TimeQuest Timing Analyzer as described in “Step 4: Launch the TimeQuest Timing Analyzer”.
Example 3–2 shows the content of the timequest_setup.tcl script. Use this script to specify the TimeQuest Timing Analyzer as the default timing analysis tool. The Classic Timing Analyzer is the default timing analyzer in the Quartus II software. Example 3–2. The timeqest_setup.tcl Script...
(Software Licensing) Email authorization@altera.com Note: (1) You can also contact your local Altera sales office or sales representative. Typographic Conventions The following table shows the typographic conventions that this document uses. Visual Cue Meaning Bold Type with Initial Capital Let-...