Re: [myhdl-list] migrating from myHDL-0.5.1 to myHDL_0.6

[Günter D. <dan...@we...>]

Sami Al Dalahmah wrote:

...

> By the way does anyone have
> good experience in Icarus (maybe it is somehow unrelated to myHDL but it can
> be useful)? I ran into the issue when you have a python script using the
> function "os.system(*command*)" to run Icarus for compiling and simulating
> then GTKwave for showing the wave diagram, sometimes when you have a syntax
> error python just do not realize this and continue the script. Do you if
> Icarus can return a value that can be tested for errors that can help my
> script? Actually I asked the same question in the Icarus Wiki and they
> pointed to a Perl test suite that I can learn from, this requires investing
> time to learn Perl then translate it to Python, which is an option I like to
> make one my last ones.
> 
> Sorry for the long email and thank you for your time reading it.
> 

I thought there was a discussion about that last year or so on the
Icarus mailing list, but the only post I found was this from 2007:

http://www.nabble.com/gEDA-dev:-Icarus-Verilog-return-codes--td8653647.html

However, if I understand you right then you want to know when the
simulation failed, which might not be covered by that return code.

As Newell mentioned in another post, one way to solve that is not to use
os.system() but for example os.popen() instead. There you can read the
output of the application and in the test bench you can write some text
that can be search for in the calling python script.

Cheers,

Guenter