TA的每日心情 | 擦汗 2020-1-14 15:59 |
|---|
签到天数: 1 天 [LV.1]初来乍到
|
2#

楼主 |
发表于 2007-12-18 21:50
|
只看该作者
The biggest problem with asynchronous resets is that they are asynchronous, both at the
4 U8 Q' N9 B0 p* I; E; @ ^assertion and at the de-assertion of the reset. The assertion is a non issue, the de-assertion is the* x% ?3 j4 Z7 I: e7 \: P9 Z
issue. If the asynchronous reset is released at or near the active clock edge of a flip-flop, the# F5 j+ w5 J5 ?
output of the flip-flop could go metastable and thus the reset state of the ASIC could be lost.
' ?% H% R; k$ Z* x1 O3 EAnother problem that an asynchronous reset can have, depending on its source, is spurious resets
+ W# g: x: [* W& X& o$ Y Ndue to noise or glitches on the board or system reset. See section 8.0 for a possible solution to, S, a2 f% y$ C. ~; ]+ ^: x
reset glitches. If this is a real problem in a system, then one might think that using synchronous* T9 b E! L+ r8 z2 c+ m4 d
resets is the solution. A different but similar problem exists for synchronous resets if these
( _# R; A; F1 O% M/ X: Rspurious reset pulses occur near a clock edge, the flip-flops can still go metastable (but this is+ K% Z* F- p) p( l! a9 `
true of any data input that violates setup requirements). |
|