Re: [myhdl-list] Reset functionality "synthesis"

[Jan D. <ja...@ja...>]

On 07/06/2012 05:00 AM, Christopher Felton wrote:


>    From my understanding (and what I agree with) is that the
> /@always_seq/ requires a reset.  If you don't want a reset
> you will need to use the /@always(clock.posedge)/.  If you
> use the /@always_seq/ it requires a reset.

That's not quite right.

The @always_seq decorator needs a reset *argument*, that is
correct. However it can be 'None' to indicate explicitly that
you don't want a reset:

@always_seq(clock.posedge, reset=None)
...

A reviewer will have no doubt what the intention is.
In the case of a traditional always block, he may think
you have delayed the reset coding (e.g. because it's
boring) and forgotten about it.

-- 
Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com
     Python as a HDL: http://www.myhdl.org
     VHDL development, the modern way: http://www.sigasi.com
     World-class digital design: http://www.easics.com