Re: [Gtkwave-users] Comparing waveforms

[Roman P. <ri...@gm...>]

Thank you,
I can confirm, events work fine now with VCD export.

I've experimented little bit, and it looks like truncation is sort of a
feature.
I've attached 2 examples to email.
in1.vcd and in2.vcd are input files,  and out1.vcd and out2.vcd are outputs
generated by VCD export.

In my opinion this optimization looks quite confusing. It would probably be
much more clear if both output waves started at #0.

Thanks,
Roman


чт, 23 янв. 2020 г. в 19:23, <by...@nc...>:

> Events type should now dump properly with what I checked into svn (r1550).
>
> https://sourceforge.net/p/gtkwave/code/1550/
>
> I don't know about the truncation at start of sim.  I'd need you to email
> me some waves with instructions on which signals have the problem.
>
> Thanks,
> -Tony
>
> -----------------------------------------
> From: "Roman Popov"
> To: gtk...@li...
> Cc:
> Sent: Thursday January 23 2020 11:10:37AM
> Subject: Re: [Gtkwave-users] Comparing waveforms
>
> Thanks, sounds like a great idea!
>
> However, it seems like Export -> Write VCD does not work.
>
> For example, I select some signals as on this picture:
>
> [image: image.png]
>
> Then Export->Write VCD.  When I open exported file I got:
> [image: image.png]
>
> So it looks like data is truncated at start of simulation.  And event
> signal is always 1.
>
> - Roman
>
> ср, 22 янв. 2020 г. в 18:59, <by...@nc...>:
>
>> Probably you can use this: <https://github.com/veripool/vcddiff>
>> https://github.com/veripool/vcddiff
>>
>> I haven't tried it, but you could probably bring up the signals you want,
>> then Export -> Write VCD As.  After that, run them through that vcddiff
>> tool.
>>
>> -Tony
>>
>> -----------------------------------------
>> From: "Roman Popov"
>> To: gtk...@li...
>> Cc:
>> Sent: Wednesday January 22 2020 9:49:11PM
>> Subject: [Gtkwave-users] Comparing waveforms
>>
>> Hi,
>> What is the best way to compare two waveforms? For example, if I have two
>> waveforms with same design tree before and after some patching.  And I want
>> to find out what signal values changed.
>>
>> I can use TwinWave for manual inspection, but usually it is very time
>> consuming. Is there a better, more automated way?
>>
>> -Roman
>> _______________________________________________
>> Gtkwave-users mailing list
>> Gtk...@li...
>> <https://lists.sourceforge.net/lists/listinfo/gtkwave-users>
>> https://lists.sourceforge.net/lists/listinfo/gtkwave-users
>>
> _______________________________________________
> Gtkwave-users mailing list
> Gtk...@li...
> https://lists.sourceforge.net/lists/listinfo/gtkwave-users
>