04_传统时序的分析器TAN到基于SDC的Timequest时序的分析器转换.ppt

Switching to the TimeQuest Timing Analyzer Objectives Convert a design from using the Classic timing analyzer to using the TimeQuest timing analyzer Understand the differences between the two timing analysis engines Find sources for more information Prerequisites Agenda Introduction to switching Differences between the Classic and TimeQuest timing analyzers Analysis I/O timing constraints Reporting Converting a design to the TimeQuest analyzer References Introduction to Switching “Test drive” the TimeQuest tool with an existing project before switching SDC file required for constraints Conversion utility helps convert QSF assignments to SDC file Switch on a per-project basis Switching Options and Target Devices Default setting is to use Classic analyzer Exceptions Projects targetting Arria? GX devices Must use TimeQuest analyzer Cannot switch to Classic analyzer New projects targetting Cyclone? III and Stratix? III devices Default is TimeQuest analyzer Can switch to Classic analyzer Check Quartus II Handbook, Help, or newer device handbook for other exceptions Choosing Whether to Switch Switch if… You are familiar with SDC You have a design that is difficult to constrain with the Classic analyzer DDR Complex clocking structures You prefer TimeQuest analysis and interface Don’t switch if… Classic analyzer does everything you need Switching to the TimeQuest Timing Analyzer Analysis Differences Classic Analyzer Settings for Switching Change Classic Settings in GUI Cut Paths between Unrelated Clock Domains Classic analyzer default: ON Worst-case behavior (matches TimeQuest behavior): OFF Does not analyze paths between unrelated clock domains Cut Paths between Unrelated Clock Domains Classic analyzer does not analyze paths between unrelated clock domains by default May mask design problems Timing Constraint Check tool helps show those paths Turn setting OFF and constrain cross-clock domain paths Add cut or setup/hold relationship assignments TimeQuest Behavior: Cross-Dom