Re: [myhdl-list] debugging Cosimulation with Icarus Verilog

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

Günter Dannoritzer wrote:
> Jan Decaluwe wrote:
>> Excellent, looks like we're getting somewhere here!
> 
> Some update on the Icarus Verilog bug report #2048463 concerning the
> cbValueChange issues. The bug is fixed in the git repository, however,
> the difference in the call back behavior at time 0 remains. In the bug
> tracker there is some explanation about this behavior:
> 
> http://sourceforge.net/tracker/index.php?func=detail&aid=2048463&group_id=149850&atid=775997
> 
> I also posted a question about this on comp.lang.verilog and got a reply
> from someone at Cadence. The Icarus Verilog developer Steve Williams
> replied now to that subject as well. Will see what comes out of that
> discussion.
> 
> Here is a link to the comp.lang.Verilog discussion:
> 
> http://groups.google.com/group/comp.lang.verilog/browse_frm/thread/58628e26e5294c58#
> 
> I will look into adjusting the current myhdl.c for Icarus to work with
> the t0 behavior.

Maybe with the bug fix you can use the assignment that was commented out,
and perhaps that fixes it?

   // icarus stops on the following line but shouldn't
   // cb_data_s.value = &value_s;
   cb_data_s.value = NULL;

-- 
Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com
Kaboutermansstraat 97, B-3000 Leuven, Belgium
     From Python to silicon:
     http://myhdl.jandecaluwe.com