Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

PrimeTime vs. Design Compiler for static timing analysis

Status
Not open for further replies.

3wais

Member level 4
Joined
Sep 12, 2011
Messages
70
Helped
3
Reputation
6
Reaction score
3
Trophy points
1,288
Location
Alexandria,Egypt
Activity points
1,787
I'm new to static timing analysis, I have been reading Prime Time's user guide before actually using it. Most commands mentioned are shared with Design Compiler, and the user guide says that most shared commands are either identical or have slight differences.

my questions are why do I have to save the design in DC and read it again in PT to run the exact same commands? why not use the same reporting and analysis features in DC instead of PT? and why would anyone pay for a license for PT when he can use DC?
actually the most important question of all is: am I using Prime Time right? what I was reading was "Prime Time : Fundamentals User Guide" should I skip this and go for other advanced user guides?
 

Design compiler is a synthesis tool, with could report timing (and more...).
PrimeTime is at least STA tool.
 

The PT timing engine is more accurate than DC, so you can't rely on DC. The path coverage isn't also as high in DC.

Why PT isn't available inside ICC is a puzzle.
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top