| 
                 
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 ! Q( q3 w3 x3 W& E+ aassertion and at the de-assertion of the reset. The assertion is a non issue, the de-assertion is the- d' K1 [8 a! @' u
 issue. If the asynchronous reset is released at or near the active clock edge of a flip-flop, the6 G) O3 z4 a+ N# ?8 N
 output of the flip-flop could go metastable and thus the reset state of the ASIC could be lost.$ E0 X1 [& ^4 e& q" I
 Another problem that an asynchronous reset can have, depending on its source, is spurious resets
 ! m. t8 e+ h' s4 s) A7 d, i1 jdue to noise or glitches on the board or system reset. See section 8.0 for a possible solution to- a7 E/ R! o2 M1 @
 reset glitches. If this is a real problem in a system, then one might think that using synchronous& ~9 Q7 w" r) K3 w
 resets is the solution. A different but similar problem exists for synchronous resets if these4 J+ z3 M" g1 x
 spurious reset pulses occur near a clock edge, the flip-flops can still go metastable (but this is; X: H& H! c& [: a* y& g
 true of any data input that violates setup requirements).
 | 
 |