J
Jim Granville
Guest
Bob Perlman wrote:
If the wdog fires due to clock failure, and your reset is only Sync,
guess what happens next ?
Maybe the FPGA core does not care, but the system design certainly does,
and if the FPGA cannot handle this, then downstream, logic must be added.
-jg
Correct, and you also need Async control, in such paths as Watchdog.On 9 Oct 2006 11:57:12 -0700, "KJ" <Kevin.Jennings@Unisys.com> wrote:
In any case, nobody has articulated yet the application that really
does require specified reset behaviour PRIOR to the clock starting thus
requiring use of the async reset (with the exception of the reset
signal synchronizer flip flop itself).
Uh, I did. Took me 20 minutes to type it up, too. I'm not exactly
sure what the disagreement is: if you have FFs controlling TriState
enables, you should initialize them asynchronously. Whether that's
done by an end-of-config reset or some other reset signal doesn't
really matter--you need the asynchronous reset.
And I didn't even get to the open-the-bomb-bay-doors and
throw-the-countermeasures-out-the-back-of-the-plane and
start-radiating-the-patient signals. Proper design etiquette demands
that they be initialized immediately, too. (Yes, those signals go
through other interlocks, but as soon as you rely on redundancy, it
ceases to exist.)
If the wdog fires due to clock failure, and your reset is only Sync,
guess what happens next ?
Maybe the FPGA core does not care, but the system design certainly does,
and if the FPGA cannot handle this, then downstream, logic must be added.
-jg