Re: [myhdl-list] Decorator Question

[Christopher L. <loz...@fr...>]

On 5/4/11 12:17 AM, Jan Decaluwe wrote:
> http://www.myhdl.org/doc/current/manual/modeling.html#rtl-modeling

Thank you.  I missed that page.


On 5/4/11 12:55 AM, Ben wrote:
> Let me also point you to another advise from Jan D. to you dating from 
> March 31:
> http://sourceforge.net/mailarchive/message.php?msg_id=27287048
>
> On Thu, Mar 31, 2011 at 11:13, Jan Decaluwe<ja...@ja...>  wrote:
>> To avoid disappointments, it may be wise to start by
>> reading an introductory text to digital electronics
>> and synthesis first. Starting with MyHDL before this
>> is probably not the right approach, because it assumes
>> implicit knowledge, especially about limitations :-)
>> (Until someone writes the book "Introduction to
>> digital design using MyHDL" of course :-))

Thank you for the reminder.  Excellent advice for me personally if my 
focus were to build something.   Of course I never did it.   And more to 
the point that is not what the newbies want to do.  They just want MyHDL 
to be an easy way to do stuff.  So we need to make that easy to happen.  
As I go along and stumble on these problems, I am happy to fix them.  So 
I updated the MyHDL.org website to say:

http://myhdl.org/doku.php/meps:mep-100


    Background

Decorators are just a way to simplify the python code. There are three 
types of Decorators. @always indicates a module which is driven by a 
clock signal or by a reset. @always_comb indicates a module which is 
driven by changes in the inputs. @instance, is just used for convenience 
in test scripts, since test scripts need to participate in the 
simulation framework. Onto the software description of decorators.






-- 
Regards
Christopher Lozinski

Check out my iPhone apps TextFaster and EmailFaster
http://textfaster.com

Expect a paradigm shift.
http://MyHDL.org