You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are some discussions in the web about FF with and without reset capability to summarize:
If the initial value of the fabric is important or a state diagram needed to be used, then it is advisable to use a flip-flop (FF) with reset capability.
If initial value is not important or reset capability unneeded for less area == less logic == less delay == faster operation == higher operating frequency, FF without reset could be used.
If FPGA fabric will be created for general purpose using FF with reset capability make more sense to me.
I want to ask since in your example FF without reset capability used, is it practical to have FF without reset capability inside of the CLB?
The text was updated successfully, but these errors were encountered:
Hi,
In classic soft logic example FF declared without reset.
There are some discussions in the web about FF with and without reset capability to summarize:
If the initial value of the fabric is important or a state diagram needed to be used, then it is advisable to use a flip-flop (FF) with reset capability.
If initial value is not important or reset capability unneeded for less area == less logic == less delay == faster operation == higher operating frequency, FF without reset could be used.
If FPGA fabric will be created for general purpose using FF with reset capability make more sense to me.
I want to ask since in your example FF without reset capability used, is it practical to have FF without reset capability inside of the CLB?
The text was updated successfully, but these errors were encountered: