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- E( L( M, x5 t/ x# ?: O9 ?
assertion and at the de-assertion of the reset. The assertion is a non issue, the de-assertion is the7 ]3 u& h2 M: _) X: b1 G( W
issue. If the asynchronous reset is released at or near the active clock edge of a flip-flop, the
4 F! I0 T* x8 s; i/ Xoutput of the flip-flop could go metastable and thus the reset state of the ASIC could be lost.
- ^3 v: a7 G" R+ l( c# X" mAnother problem that an asynchronous reset can have, depending on its source, is spurious resets
% t, J! T0 \1 `% P. wdue to noise or glitches on the board or system reset. See section 8.0 for a possible solution to( u9 G$ J3 w! H# ]' C
reset glitches. If this is a real problem in a system, then one might think that using synchronous- g% k- W& o8 q2 G S% R
resets is the solution. A different but similar problem exists for synchronous resets if these4 |- O1 A( y0 ~
spurious reset pulses occur near a clock edge, the flip-flops can still go metastable (but this is
+ D3 O/ o7 y& ^% d: V$ b# r1 htrue of any data input that violates setup requirements). |
|