Re: [Gtkwave-users] RE : best trace format for kernel tracer

[<by...@nc...>]

Thanks.  Patch applied and checked into SVN.  It probably wasn't generally supported as until now the only real simulator generating those values was GHDL which uses the GHW format.  That is, I've only used those formats to store 01xz values even though the capability for more was built in.

-Tony


---- Matthieu CASTET <mat...@pa...> wrote: 
> Ok thanks.
> 
> One more question : lxt seems to support '0', '1', 'Z', 'X', 'H', 'U', 'W', 'L',
> '-' state [1]
> 
> Why there are not supported by gtkwave ?
> 
> I attach a patch that implement it (I don't know if I covered all the path).
> 
> 
> Matthieu
> 
> [1]
> http://6004.csail.mit.edu/6.371/cadtools/gtkwave/LXT_Explained.html
> 
> by...@nc... a écrit :
> > I just checked the appropriate fix into SVN for fst.c.
> > 
> > Note that vcd2fst doesn't support those as they're not a legitimate value in VCD and are gtkwave extensions. (I don't want to slow down vcd2fst unless I have to.)  For your external writer you should be ok.
> > 
> > -Tony
> > 
> > 
> > ---- Matthieu Castet <mat...@pa...> wrote: 
> >> Hi,
> >>
> >>> Try using FST.  Again, don't put spaces in signal names.
> >> Thanks for your reply.
> >>
> >> After some tests, it seems fst only support "xz01" bit state. [1]
> >>
> >> Only vcd format seems to support u and w state.
> >>
> >> Matthieu
> >>
> >> [1]
> >>
> >>                 case '0':   h_val = AN_0; break;
> >>                 case '1':   h_val = AN_1; break;
> >>                 case 'Z':
> >>                 case 'z':   h_val = AN_Z; break;
> >>                 default:    h_val = AN_X; break;
> >>
> >> ------------------------------------------------------------------------
> >>
> 
> 
> -- 
> Matthieu Castet
> Ingénieur Développement Logiciel
> Parrot SA
> 174 Quai de Jemmapes
> 75010 Paris, France
> 
> Tél: +33 (0) 1 48 03 74 78
> Fax: +33 (0) 1 48 03 06 66
> Email: mat...@pa...
> http://www.parrot.biz