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.

Register Log in

critical path with DC

Status
Not open for further replies.
C

Clunixchit

Member level 1
Joined
Jul 15, 2007
Messages
35
Helped
0
Reputation
0
Reaction score
0
Trophy points
1,286
Activity points
1,488
Hai there

I've been using get_timings, then foreach timing, report_timing -from startpoint -to endpoint. Afterwards, the one with the least slack is the critical path.

However I've been told to rather use report_constraint to determine the critical path. I can't understand the reason behind this. I hope one could explain to me.

To me, if there aren't any violators in the design, it would be impossible to determine the critical path.
 

report_constraint is global command , which consider the whole design to decide which is violated on the specified constraints. other hand, get_timing path depends on your inputs like From and to paths. only these paths, timing is looked out to get Slack values.

report_constained command is easy to use than get_timing path.

report_qor is best command to get the worst slack in each clock domain path.

--Sam
 
  • Like
Reactions: njr@1

    N

    njr@1

    Points: 2
    Helpful Answer Positive Rating
Status
Not open for further replies.

Similar threads

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top