Re: [Gtkwave-users] vcd2fst bug or feature?

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

Thanks!

Yes , my dumper dumps signals only when they change. So uninitialized
signals are not dumped at #0.
GtkWave VCD renders them as X.  Synopsys tools render those signals grey.

I don't dump uninitialized signals because it is more efficient.

-Roman

пт, 24 янв. 2020 г. в 08:50, <by...@nc...>:

> Your dumper didn't dump X on those signals at time zero (for signals that
> didn't have non-X values at the end of time #0) like so:
>
> #0
> x!
> x"
> x#
> x%
>
> -Tony
>
> -----------------------------------------
> From: "Roman Popov"
> To: gtk...@li...
> Cc:
> Sent: Friday January 24 2020 12:11:07AM
> Subject: [Gtkwave-users] vcd2fst bug or feature?
>
> Hello,
> I'm using vcd2fst utility bundled with gtkwave to convert vcd to fst.
> I've noticed that 1-bit signals with unknown value become 0 after
> conversion.
>
> Is this a bug? Or FST does not support X-value for 1 bit signals?
>
> I've attached example input and output to email.
>
> [image: image.png]
>
>
> Thanks,
> Roman
> _______________________________________________
> Gtkwave-users mailing list
> Gtk...@li...
> https://lists.sourceforge.net/lists/listinfo/gtkwave-users
>