BY: Calvin Wong (cawong)
DATE: 2007-08-02 04:53
SUBJECT: Having trouble dumping a vcd file


Hello,

I tried the latest 18.0.0 release of ruby-vpi and it definately is a
lot more stable than 17.0.0 release. A lot of good features was added.

Now as the message title says, I have difficulty generating a vcd
file using the $dumpvars call. I edited the counter.v file and added
'initial $dumpvars' routine to it. I also modify the advance_time
method in the vpi.rb file to get the current time (using
vpi_get_time routine) and then add the aNumSteps to it to produce a
monotonically increasing time steps.

After the simulation is performed, I am left with a verilog.dump
file but only up to 1 time tick was logged.

I suspect that once the ruby execution is done, both the ruby
simulation and the verilog (using vcs) simulation is terminated.
When this happened , vcs does not have the time to flush out it's
vcd logging buffer. So ... my question is if there is a way to relay
control over to verilog so that the simulator can flush out the vcd
buffer prior to ending the simulation?


Calvin

Reply via email to