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.

data required time in PT report timing

Status
Not open for further replies.

raviram80

Member level 3
Joined
Jun 8, 2009
Messages
65
Helped
1
Reputation
2
Reaction score
1
Trophy points
1,288
Activity points
1,750
This is urgent.

Can you please let me know how data required time is calculated in the report_timing command that comes at the end. I understand how data_arrival time is calculated.

I see

In the data_arrival time section I see

clock CLK' (rise edge) 800.00 800.00
clock network delay (propagated) 3503.00 * 4303.00

In the data_required section I see the following


clock CLK' (rise edge) 800.00 800.00
clock network delay (propagated) 5111.00 * 5911.00

How is this clock network delay calculated and how is this different from clock network delay in the data arrival time section


I also see clock reconvergence pessimism and clock uncertainity as well.

Please reply at the earliest.

Regards,

Ravi
 

hi ravi,
looking at ur report,
both clocks are starting at the same time, that means this is for hold analysis, and the delay for capture clock is more so my guess is correct.
both propoaged delays will be diff, as for launch path tool will take the shortest path and for the capture path it will take the longer path, so the delays will be different,
usually opposite for setup analysis.
 

add the option "-path full_clock_expanded" to your "report_timing" command. You will see the full clock paths going to both launch and capture endpoints.
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top