|
PrimeTime 2: Debugging Constraints
OVERVIEW
This workshop addresses the most time-consuming part of static timing
analysis: debugging constraints. The workshop provides a method to identify
potential timing problems, identify the cause, and determine the effects
of these problems. Armed with this information, students will now be
able to confirm that constraints are correct or, if incorrect, will
have sufficient information to correct the problem.
Incorrect STA constraints must be identified because they obscure real
timing violations and can cause two problems: either the real violations
are missed and not reported; or violations are reported that are not
real, making it difficult to find the real violations hidden among them.
OBJECTIVES
At the end of this workshop the student should be able to:
- Pinpoint the cause and determine the effects of check_timing and
report_analysis_coverage warnings
- Execute eight PrimeTime commands and a custom procedure to trace
from the warning to the cause and explore objects in that path
- Systematically debug scripts to eliminate obvious problems using
PrimeTime
- Independently and fully utilize check_timing and report_analysis_coverage
to flag remaining constraint problems
- Identify key pieces of a timing report for debugging final constraint
problems
AUDIENCE PROFILE
Design or Verification engineers who perform STA using PrimeTime.
PREREQUISITES
To benefit the most from the material presented in this workshop, you
should:
- Have taken PrimeTime 1
OR
- Possess equivalent knowledge with PrimeTime including:
- Script writing using Tcl
- Reading and linking a design
- Writing block constraints
- Generating and interpreting timing reports using report_timing and
report_constraint commands
COURSE OUTLINE
Unit 1: Tools of the Trade
- Lab 1 A Guided Tour of the Tools of the Trade
- Lab 2 Choose the Correct Command and Apply It
Unit 2:
Complete Qualification of PrimeTime Inputs
- Lab 3 Find and Debug Potential Constraint Problems
SYNOPSYS TOOLS USED
|