Re: [myhdl-list] What MyHDL is not

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

On 04/24/2012 05:20 AM, Bob Cunningham wrote:

> This may, in fact, be an ideal entry point for a MyHDL tutorial:
> Start with a "black box" module, a written description of its
> interface and intended behavior, then write the testbench.  Leverage
> Python skills the reader may already possess.  (It will also ensure
> the entire toolchain has been properly installed.)  Later lessons
> could introduce MyHDL primitives, then have the reader use a good
> testbench to find and fix the error in a flawed circuit (where the
> fix would require use the primitives just introduced).

http://myhdl.org/doku.php/cookbook:stopwatch

> Test first, design second.  It would also teach the reader to become
> good at reading circuit descriptions before writing them.  Both
> pedagogically and practically, this seems to me to be a very sound
> approach, one I'd be very interested in pursuing!  And MyHDL may be
> the first HDL to make this approach practical.  I think I see an
> O'Reilly book here somewhere...

http://www.myhdl.org/doku.php/why#you_would_like_to_do_algorithm_development_and_implementation_in_the_same_environment

http://www.myhdl.org/doc/current/manual/unittest.html



-- 
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