|
|
| Line 1: |
Line 1: |
| The operation of most digital circuit systems, such as computer systems, is synchronized by a "clock" that dictates the sequence and pacing of the devices on the circuit. Ideally, the input to each element has reached its final value before the next clock movement occurs so that the behavior of the whole circuit can be predicted exactly. The maximum speed at which a system can run must account for the variance that occurs between the various elements of a circuit due to differences in physical composition, temperature, and path length.
| | I am Ginger from Hjalteby. I am learning to play the Mandolin. Other hobbies are Bus spotting.<br><br>Feel free to surf to my blog post ... FIFA 15 coin hack [[http://www.nifvet.com/ziyaretcidefteri.html more information]] |
| | |
| In a [[synchronous circuit]], clock skew (T<sub>Skew</sub>) is the difference in the arrival time between ''two sequentially-adjacent registers''. Given two sequentially-adjacent registers R<sub>''i''</sub> and R<sub>''j''</sub> with clock arrival times at register clock pins as T<sub>C''i''</sub> and T<sub>C''j''</sub> respectively, then clock skew can be defined as: {{math|T<sub>Skew ''i, j''</sub> {{=}} T<sub>C''i''</sub> - T<sub>C''j''</sub>}}
| |
| | |
| Clock skew can be positive or negative. If the clock signals are in complete synchronicity, then the clock skew observed at these registers is zero.
| |
| | |
| ==In circuit design==
| |
| In circuit designs, '''clock skew''' (sometimes '''timing skew''') is a phenomenon in [[synchronous circuit]]s in which the clock signal (sent from the [[clock circuit]]) arrives at different components at different times. This can be caused by many different things, such as wire-interconnect length, temperature variations, variation in intermediate devices, [[capacitive coupling]], material imperfections, and differences in input capacitance on the clock inputs of devices using the clock. As the clock rate of a circuit increases, timing becomes more critical and less variation can be tolerated if the circuit is to function properly.
| |
| | |
| There are two types of clock skew: '''negative skew''' and '''positive skew'''. Positive skew occurs when the transmitting register receives the clock earlier than the receiving register. Negative skew is the opposite: the receiving register gets the clock earlier than the sending register.
| |
| | |
| ===Harmful skew===
| |
| | |
| Two types of violation can be caused by clock skew. One problem is caused when the clock travels slower than the path from one register to another - allowing data to penetrate two registers in the same clock tick, or maybe destroying the integrity of the latched data. This is called a '''hold violation''' because the previous data is not held long enough at the destination flip-flop to be properly clocked through. Another problem is caused if the destination flip-flop receives the clock tick earlier than the source flip-flop - the data signal has that much less time to reach the destination flip-flop before the next clock tick. If it fails to do so, a '''setup violation''' occurs, so-called because the new data was not set up and stable before the next clock tick arrived. A hold violation is more serious than a setup violation because it cannot be fixed by increasing the clock period. Positive skew and negative skew cannot negatively impact setup and hold timing constraints respectively (see inequalities below).
| |
| | |
| ===Beneficial skew===
| |
| Clock skew can also benefit a circuit by increasing the clock period locally at which the circuit will operate correctly. For each source register and destination register connected by a path, the following inequalities must hold:
| |
| # <math> T \ge reg + path_{max} + S - (s_d - s_s) </math>
| |
| # <math> (s_d - s_s) \le reg + path_{min} - H </math>
| |
| | |
| where
| |
| *''T'' is the clock period,
| |
| *''reg'' is the source register's clock to Q delay,
| |
| *<math>path_{max}</math> is the path with the longest delay from source to destination,
| |
| *''S'' is the [[setup time]] of the destination register
| |
| *<math>(s_d - s_s)</math> represents the clock skew from the source to the destination registers,
| |
| *<math>path_{min}</math> is the path with the shortest delay from source to destination,
| |
| *''H'' is the hold time of the destination register,
| |
| *<math>s_d</math> is the clock skew to the destination register, and
| |
| *<math>s_s</math> is the clock skew to the source register.
| |
| | |
| Positive clock skews are good for fixing setup violations, but can cause hold violations.
| |
| | |
| ===Optimal skew===
| |
| If the clock arrival times at individual registers are viewed as variables to be adjusted in order to minimize the clock period while satisfying the above inequalities for every path through the circuit, then the result is a [[Linear Programming]] problem.<ref>Fishburn, J.P. “Clock Skew Optimization”, in ''IEEE Trans. On Computers'', Vol. 39, No. 7, July 1990.</ref> In this linear program, zero clock skew is merely a feasible point - the solution to the linear program generally gives a clock period that is less than what is achieved by zero skew. In addition, safety margins greater than or equal to the zero skew case can be guaranteed by setting setup and hold times appropriately in the linear program.
| |
| | |
| Due to the simple form of this linear program, an easily programmed algorithm is available for arriving at a solution.<ref>Maheshwari, N., and Sapatnekar, S.S., ''Timing Analysis and Optimization of Sequential Circuits'', Kluwer, 1999.</ref>
| |
| | |
| Most CAD systems for VLSI and FPGA design contain facilities for optimizing clock skews.
| |
| | |
| === Confusion between clock skew and clock jitter ===
| |
| | |
| In addition to clock skew due to static differences in the clock latency from the clock source to each clocked register, no clock signal is perfectly periodic, so that the clock period or clock cycle time varies even at a single component, and this variation is known as clock [[Jitter]]. At a particular point in a clock distribution network, jitter is the only contributor to the clock timing uncertainty.
| |
| | |
| As an approximation, it is often useful to discuss the total clock timing uncertainty between two registers as the sum of spatial clock skew (the spatial differences in clock latency from the clock source), and clock jitter (meaning the non-periodicity of the clock at a particular point in the network). Unfortunately, spatial clock skew varies in time from one cycle to the next due to local time-dependent variations in the power supply, local temperature, and noise coupling to other signals.
| |
| | |
| Thus, in the usual case of sending and receiving registers at different locations, there is no clear way to separate the total clock timing uncertainty into spatial skew and jitter. Thus some authors use the term clock skew to describe the sum of spatial clock skew and clock jitter. This of course means that the clock skew between two points varies from cycle to cycle, which is a complexity that is rarely mentioned. Many other authors use the term clock skew only for the spatial variation of clock times, and use the term clock jitter to represent the rest of the total clock timing uncertainty. This of course means that the clock jitter must be different at each component, which again is rarely discussed.
| |
| | |
| Fortunately, in many cases, spatial clock skew remains fairly constant from cycle to cycle, so that the rest of the total clock timing uncertainty can be well approximated by a single common clock jitter value.
| |
| | |
| The Optimal Skew discussion above, for example refers only to the static component of the spatial clock skew.
| |
| | |
| ==On a network==
| |
| | |
| On a network such as the internet, '''clock skew''' describes the difference in time shown by the clocks at the different nodes on the network. It is usually an unavoidable phenomenon (at least if one looks at milli-second resolutions), but clock skew of tens of minutes or more is also quite common. Network operations that require time stamps which are comparable across hosts can be affected by clock skew. A number of protocols (e.g. [[Network Time Protocol]]) have been designed to reduce clock skew, and produce more stable functions. Some applications (such as game servers) may also use their own synchronization mechanism to avoid reliability problems due to clock skew.
| |
| | |
| == Interfaces==
| |
| Clock skew is the reason why at fast speeds or long distances, serial interfaces (e.g. [[Serial Attached SCSI]] or [[USB]]) are preferred over parallel interfaces (e.g. parallel [[SCSI]]).
| |
| | |
| ==See also==
| |
| | |
| * [[Clock drift]]
| |
| * [[Jitter]]
| |
| | |
| ==References==
| |
| | |
| * Friedman, E.G., ed., ''Clock Distribution Networks in VLSI Circuits and Systems'', IEEE Press, 1995.
| |
| | |
| * Tam, S., Limaye, D.L., and Desai, U.N., "Clock Generation and Distribution for the 130-nm Itanium 2 Processor with 6-MB On-Die L3 Cache", in ''IEEE Journal of Solid-State Circuits'', Vol. 39, No. 4, April 2004.
| |
| <references/>
| |
| | |
| == Further reading ==
| |
| | |
| [[Category:Electronics]]
| |
| [[Category:Clock signal]]
| |
I am Ginger from Hjalteby. I am learning to play the Mandolin. Other hobbies are Bus spotting.
Feel free to surf to my blog post ... FIFA 15 coin hack [more information]