Re: [myhdl-list] Verilator as a backend to myhdl?

[Terry C. <ter...@gm...>]

Hi myhdl gurus,

I finally managed to get the verilator model into python via boost.python
and got it working w/ myhdl. Here are my experiences with it:
1. I really enjoyed using myhdl. It is just such a joy to use compare to
verilog. Once the verilator model was in python getting the myhdl testbench
to work was almost effortless.
2. Unfortunately, just as Jan had predicted, the simulation time went up
drastically b/c python's in the loop. Especially when the testbench
environment started to get complicated with all sorts of dram backdoor
access and soft cpus set-up. I ran myhdl w/ Python cProfile and realized
that it was spending a good 60 to 70% of its times in python function
calls.

So, the python/myhdl as a top level driver idea is probably a no-go at this
point. I am toying with the idea of using a light-weight C threading system
and using Google Test as the unit testing environment.

The question now remains is whether anyone would be interested in the
verilator/myhdl makefile-based flow I have here. I could spend maybe 30mins
cleaning stuff up and removing all the proprietary RTL code and push it into
github or bitbucket. It is nothing amazing, but maybe someone might find it
interesting as a mechanism to get legacy verilog code to work w/ new (or
existing) myhdl code.

Regards,
Terry