Re: [myhdl-list] Clump'n and Lump'n
Brought to you by:
jandecaluwe
From: Christopher F. <chr...@gm...> - 2011-06-02 19:56:19
|
On 6/2/2011 1:41 PM, Uri Nix wrote: > Hi, > > In my experience SystemC+Boost is functionally equivalent to MyHDL for > system modelling, although the LA and PE for Python is an order of magnitude > easier. > Another significant advantage of Python is its cross platform portability > (Windows, Unix, Linux, etc), which saves the hassle of deployment and > managing different build chains. > > Cheers, > Uri Yes, I agree! Using the numerical packages in Python is much easier. To your point I can open a Python shell and do the following: >> from numpy import * >> X = random.rand(3,3) >> matrix(X) * matrix(X[1,:]).transpose() >> matrix([[ 0.53398746], [ 0.96773496], [ 1.01327792]]) #... expand to myhdl ... >> sX = Signal(matrix(X)) >> sY = Signal(matrix(X[1,:].transpose()) >> sX.next = sX * sY #... And easily incorporate into my design without much issue (the above is way too simple of an example). I can quite easily do complicated system modeling; mixing cycle and bit-accurate if needed. It has been awhile since I used SystemC (over 5 years?). I remember it being difficult (relative) and I am a pretty proficient C/C++ programmer. But it could have been that I gave up on SystemC when I started using MyHDL more :) Then I can create all my plots for analysis right in my simulation, I don't have to post-process simulation results. The only argument might be simulation speed. But I am usually done with my development and simulations and onto the next item, before I would have completed a C* implementation, making the simulation speeds a moot point. I have also found interface MyHDL with simulators to be easier than SystemC. I guess it is the Python *batteries-included*! Chris |