2.3.1. Recommended Initial SDC Constraints 2.3.2. SDC File Precedence 2.3.3. Iterative Constraint Modification 2.3.4. Creating Clocks and Clock Constraints 2.3.5. Creating I/O Constraints 2.3.6. Creating Delay and Skew Constraints 2.3.7. Creating Timing Exceptions 2.3.8. Example Circuit and SDC File
220.127.116.11.1. Default Multicycle Analysis 18.104.22.168.2. End Multicycle Setup = 2 and End Multicycle Hold = 0 22.214.171.124.3. End Multicycle Setup = 2 and End Multicycle Hold = 1 126.96.36.199.4. Same Frequency Clocks with Destination Clock Offset 188.8.131.52.5. Destination Clock Frequency is a Multiple of the Source Clock Frequency 184.108.40.206.6. Destination Clock Frequency is a Multiple of the Source Clock Frequency with an Offset 220.127.116.11.7. Source Clock Frequency is a Multiple of the Destination Clock Frequency 18.104.22.168.8. Source Clock Frequency is a Multiple of the Destination Clock Frequency with an Offset
22.214.171.124. Create Timing Netlist
You can configure or load the timing netlist that the Timing Analyzer uses to calculate path delay data.
You must generate the timing netlist before running timing analysis. You can use the Create Timing Netlist dialog box or the Create Timing Netlist command in the Tasks pane. Create Timing Netlist also generates Advanced I/O Timing reports if you turn on Enable Advanced I/O Timing in the Timing Analyzer page of the Settings dialog box.
Note: The Compiler creates the timing netlist during compilation. The timing netlist does not reflect any configuration changes that occur after the device enters user mode, such as dynamic transceiver reconfiguration. This applies to all device families except transceivers on Intel® Arria® 10 devices with the Multiple Reconfiguration Profiles feature.
The following diagram shows how the Timing Analyzer interprets and classifies timing netlist data for a sample design.
Figure 56. How Timing Analyzer Interprets the Timing Netlist
Did you find the information on this page useful?