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.

timing budget ...... what does it mean

Status
Not open for further replies.

verilog_always

Member level 2
Joined
Dec 27, 2006
Messages
43
Helped
3
Reputation
6
Reaction score
1
Trophy points
1,288
Activity points
1,552
what is the timing budget and how it is related to registered outputs ?
 

Timing Budget:
It consists of two words
Timing and Budget

Timing means To ascertain or record the time, duration, or rate of;
Budget means a plan which defines your expenditurre.

So a Timing budget is the account of timing requirements or timing parameters of a system. It is dependent on many factors like hod time, maximum operating frequency of the system.
 

Timing budget refers to what portion of the clock period remains after you account for all the system delays. What are these delays? Things like setup and hold times, propagation delays, routing delays, combinational logic delays, clock skew, etc.

For example, let us say that you want to run at 200MHZ clock, or 5nS period. If you add up all the maximum delays and the total delay in the signal path is less than 5nS, you will meet your timing budget. If the total delays are greater than 5nS, then you will fail your timing budget and you must increase your clock period or risk clocking failures in the system.
FPGA design tools know the worst case numbers for these delays and use this info when placing and routing the design as long as you inform the tools of your clock period. The FPGA tools will try to optimize the design so that all paths make the timing budget. Any paths that fail the timing budget will be in the error report.

Robust designs always try to have some timing budget left over. The reason is that clock jitter is really hard to estimate and a system with zero timing budget can fail at unpredictable times due to clock jitter.

While FPGA design tools can move the logic around to minimize the routing delays. It can also duplicate logic functions that drive loads that are on opposite sides of the chip. The FPGA design tools cannot do much for large combinatoral delays between flops. This is where pipelining comes in and helps you make your timing budget.
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top