gtk wave -two how to questions

[pini]

Please help on two issue regaridng GTKWave Analyzer v1.3.20 (w)
1999-2002 BSI for windows.
1. Is it possible to re-load waves i.e. I have an open session and
would like to re-load new VCD without exiting GTKWave.
2. Is there an option in GTKWave rc file, gtkwave.ini, to specify the
location of the GTKwave window. It would be nice if it always opens at
the same window location.

Many Thanks,
PK

 

[Allan Herriman]

On 13 Nov 2003 01:01:03 -0800, bknpk@hotmail.com (pini) wrote:

Please help on two issue regaridng GTKWave Analyzer v1.3.20 (w)
1999-2002 BSI for windows.
1. Is it possible to re-load waves i.e. I have an open session and
would like to re-load new VCD without exiting GTKWave.

No.

2. Is there an option in GTKWave rc file, gtkwave.ini, to specify the
location of the GTKwave window. It would be nice if it always opens at
the same window location.

I don't believe so.

[ Download a demo of Aldec or Modelsim and check out their waveform
viewer features, then weep. ]

Regards,
Allan

 

[pini]

I am familiar with MTI and ALDEC wave viewers. The former is great.
They are not, however, given for free as GTKwave.

Allan Herriman <allan.herriman.hates.spam@ctam.com.au.invalid> wrote in message news:<a3s6rvk25kqu0v6nnkdl5idr2qsuf44s34@4ax.com>...

On 13 Nov 2003 01:01:03 -0800, bknpk@hotmail.com (pini) wrote:

Please help on two issue regaridng GTKWave Analyzer v1.3.20 (w)
1999-2002 BSI for windows.
1. Is it possible to re-load waves i.e. I have an open session and
would like to re-load new VCD without exiting GTKWave.

No.

2. Is there an option in GTKWave rc file, gtkwave.ini, to specify the
location of the GTKwave window. It would be nice if it always opens at
the same window location.

I don't believe so.

[ Download a demo of Aldec or Modelsim and check out their waveform
viewer features, then weep. ]

Regards,
Allan

 

[Yoram Stern]

Wrong.
You can load Xilinx WebPack that includes modelsim-XE.
It is free.

bknpk@hotmail.com (pini) wrote in message news:<ca9059d7.0311130542.35eb420@posting.google.com>...

I am familiar with MTI and ALDEC wave viewers. The former is great.
They are not, however, given for free as GTKwave.

Allan Herriman <allan.herriman.hates.spam@ctam.com.au.invalid> wrote in message news:<a3s6rvk25kqu0v6nnkdl5idr2qsuf44s34@4ax.com>...
On 13 Nov 2003 01:01:03 -0800, bknpk@hotmail.com (pini) wrote:

Please help on two issue regaridng GTKWave Analyzer v1.3.20 (w)
1999-2002 BSI for windows.
1. Is it possible to re-load waves i.e. I have an open session and
would like to re-load new VCD without exiting GTKWave.

No.

2. Is there an option in GTKWave rc file, gtkwave.ini, to specify the
location of the GTKwave window. It would be nice if it always opens at
the same window location.

I don't believe so.

[ Download a demo of Aldec or Modelsim and check out their waveform
viewer features, then weep. ]

Regards,
Allan

 

[Anthony J Bybell]

Allan Herriman <allan.herriman.hates.spam@ctam.com.au.invalid> wrote in message news:<a3s6rvk25kqu0v6nnkdl5idr2qsuf44s34@4ax.com>...

On 13 Nov 2003 01:01:03 -0800, bknpk@hotmail.com (pini) wrote:

Please help on two issue regaridng GTKWave Analyzer v1.3.20 (w)
1999-2002 BSI for windows.
1. Is it possible to re-load waves i.e. I have an open session and
would like to re-load new VCD without exiting GTKWave.

No.

Correct. It wouldn't be hard for me to add this feature as I wrapped
all the malloc/free calls. Basically, I'd have to ditch malloc/free
and use my own allocate from heap routines as you probably wouldn't
want to sit around waiting for lots of free() ops to finish when you
start the new trace. So it's doable but I never felt the compulsion
to, well, "do it".

2. Is there an option in GTKWave rc file, gtkwave.ini, to specify the
location of the GTKwave window. It would be nice if it always opens at
the same window location.

I don't believe so.

I'll have to add this though keep in mind that window managers can
ignore anything I tell them to do. Depending on your window manager,
for example, you can add a line in your .fvwm2rc (or whatever) which
says where to place the viewer window. So if you're using a fairly
good WM, you can already do this.

[ Download a demo of Aldec or Modelsim and check out their waveform
viewer features, then weep. ]

As far as commercial viewers go, SignalScan's probably my all-time
favorite...mostly because it has a pretty rich feature set and doesn't
have the GUI update lag which I've seen in some viewers.

I'll check out Aldec sometime: I've never used it. Thanks for
pointing it out.

Regards,
-t

 

[Allan Herriman]

On 13 Nov 2003 11:30:32 -0800, bybell@rocketmail.com (Anthony J
Bybell) wrote:

Please help on two issue regaridng GTKWave Analyzer v1.3.20 (w)
1999-2002 BSI for windows.

Is GTKWave 1.3 still being maintained?

If so, I have a few feature suggestions:

1. "Cursor Snap" which would snap a cursor to the nearest waveform
transition (within a programmable number of pixels) when clicking with
the mouse in the waveform area.
(This avoids the infuriating need to zoom in to ps or fs resolution
just to be able to find exactly when a signal makes a transition.)
The Aldec viewer does this particularly well.

2. Move to next transition and Move to previous transition hotkeys
(and toolbar buttons). This will move the cursor to a transition on a
selected signal (to the left or right, respectively).

Regards,
Allan.

 

[Anthony J Bybell]

bknpk@hotmail.com (pini) wrote in message news:<ca9059d7.0311130003.4e70d656@posting.google.com>...

2. Is there an option in GTKWave rc file, gtkwave.ini, to specify the
location of the GTKwave window. It would be nice if it always opens at
the same window location.

I just added this feature to the unix version 1.3.32 via the following
two parms:

initial_window_xpos 50
initial_window_ypos 50

....where the number is the x/y coordinate of the window's upper left
corner. I'll get around to updating the native windows port sometime
soon as I've been putting off porting the latest unix version to win32
for a while (the old windows versions can't read LXT2 files which is a
problem).

later,
-t

 

[Anthony J Bybell]

Allan Herriman <allan.herriman.hates.spam@ctam.com.au.invalid> wrote in message news:<hf98rvsp0jcpfs0s245ef2fsbpotua6kof@4ax.com>...

On 13 Nov 2003 11:30:32 -0800, bybell@rocketmail.com (Anthony J
Bybell) wrote:

Please help on two issue regaridng GTKWave Analyzer v1.3.20 (w)
1999-2002 BSI for windows.

Is GTKWave 1.3 still being maintained?

Yep. Points below noted. I'll mess with implementing them when I get
back from vacation--those are some good ideas.

Tony

If so, I have a few feature suggestions:

1. "Cursor Snap" which would snap a cursor to the nearest waveform
transition (within a programmable number of pixels) when clicking with
the mouse in the waveform area.
(This avoids the infuriating need to zoom in to ps or fs resolution
just to be able to find exactly when a signal makes a transition.)
The Aldec viewer does this particularly well.

2. Move to next transition and Move to previous transition hotkeys
(and toolbar buttons). This will move the cursor to a transition on a
selected signal (to the left or right, respectively).

Regards,
Allan.

 

[Stephen Williams]

Allan Herriman wrote:

On 13 Nov 2003 11:30:32 -0800, bybell@rocketmail.com (Anthony J
Bybell) wrote:


Please help on two issue regaridng GTKWave Analyzer v1.3.20 (w)
1999-2002 BSI for windows.


Is GTKWave 1.3 still being maintained?

If so, I have a few feature suggestions:

1. "Cursor Snap" which would snap a cursor to the nearest waveform
transition (within a programmable number of pixels) when clicking with
the mouse in the waveform area.
(This avoids the infuriating need to zoom in to ps or fs resolution
just to be able to find exactly when a signal makes a transition.)
The Aldec viewer does this particularly well.

2. Move to next transition and Move to previous transition hotkeys
(and toolbar buttons). This will move the cursor to a transition on a
selected signal (to the left or right, respectively).

Don't forget a Windows re-port of the latest version
(Yeah, I know. Very painful.)
--
Steve Williams "The woods are lovely, dark and deep.
steve at icarus.com But I have promises to keep,
http://www.icarus.com and lines to code before I sleep,
http://www.picturel.com And lines to code before I sleep."

 

[Anthony J Bybell]

Stephen Williams <spamtrap@icarus.com> wrote in message news:<1661a$3fb579f2$40695902$30855@msgid.meganewsservers.com>...

Don't forget a Windows re-port of the latest version
(Yeah, I know. Very painful.)

Yeah, I know, I know...time to make the donuts. =) I haven't
forgotten...I've been so busy with work-related stuff that I need to
find time to sit down and re-port the latest revs to Win32. The key
thing is motivating myself to do it as I never use the Windows port.

The only painful part will be converting the old LXT1 reader over
because it heavily uses unixy mmap() stuff and file descriptors for
the linear LXT initialization. I do have such stuff in there for the
regular LXT initialization for Win32 but I want to avoid a rat's nest
of #ifdef statements. Probably what I'll do is isolate everything
into compatibility functions which do functional mapping to
OS-specific calls.

Fortunately, LXT2 will be plug 'n play for Win32 so what I might do is
simply keep 1.3.20's old LXT reader and bring along the rest of the
new code as I haven't had any Win32 users ask for linear LXT
compatibility. It'd provide the fastest interim release and I'd be
able to provide full unix<->Win32 compatibility later.

And let's not forget that one of these days I'd like to add LXT2 to
GTKWave-2.x. ...that's going to entail a little brain surgery there in
the savefile loader and trace import routines.

I'll have time soon...as they say in George RR Martin's A Song of Ice
and Fire series, "Winter Is Coming". =)

Tony

p.s.: Are there any viewers out there which can correlate simulator
logfiles to what's going on in the wave viewer window? One "neat"
future I've been thinking about for a while is that a special text
viewer window comes up where simout text scrolls along with/is marked
similar to the wave window.

 

[Anthony J Bybell]

Allan Herriman <allan.herriman.hates.spam@ctam.com.au.invalid> wrote in message news:<hf98rvsp0jcpfs0s245ef2fsbpotua6kof@4ax.com>...

Is GTKWave 1.3 still being maintained?

If so, I have a few feature suggestions:

1. "Cursor Snap" which would snap a cursor to the nearest waveform
transition (within a programmable number of pixels) when clicking with
the mouse in the waveform area.
(This avoids the infuriating need to zoom in to ps or fs resolution
just to be able to find exactly when a signal makes a transition.)
The Aldec viewer does this particularly well.

I implemented it this evening...uploaded it to metalab.unc.edu but
it'll probably take a couple of days to get online (I can't ssh into
linux-workshop for some reason lately so it isn't there).

Use the cursor_snap parameter in your .gtkwaverc file for versions
1.3.33 and higher like this:

cursor_snap 8

....which says to snap the marker to the nearest waveform transition
which is 8 pixels or closer (any value > 0 is legal and activates
this) to your pointer. That's a pretty neat ergonomic feature. Thanks
for the suggestion.

[This can easily be added to Manchester's 2.x series; cut and paste
the cook_markertime() function in wavewindow.c and its related
calls/variables. In addition, button_motion_common() has to receive
the y-coordinate of the pointer.]

2. Move to next transition and Move to previous transition hotkeys
(and toolbar buttons). This will move the cursor to a transition on a
selected signal (to the left or right, respectively).

Regards,
Allan.

I'm going to have to be lazy on this one for now and not implement it
for the time being, however this functionality does exist buried away
in the pattern search menu:

1) Highlight your signal
2) Search->Pattern Search
3) Select "Any Edge"
4) Fwd/Bkwd buttons will traverse the transitions on that signal.
Click "Mark" if you want to lay down timelines where all the
transitions are. I often use this to make clock gridlines in a
design--handy for cyclesim users like me.

Regards,
Tony

 

[Allan Herriman]

On 21 Nov 2003 20:20:46 -0800, bybell@rocketmail.com (Anthony J
Bybell) wrote:

Allan Herriman <allan.herriman.hates.spam@ctam.com.au.invalid> wrote in message news:<hf98rvsp0jcpfs0s245ef2fsbpotua6kof@4ax.com>...

Is GTKWave 1.3 still being maintained?

If so, I have a few feature suggestions:

1. "Cursor Snap" which would snap a cursor to the nearest waveform
transition (within a programmable number of pixels) when clicking with
the mouse in the waveform area.
(This avoids the infuriating need to zoom in to ps or fs resolution
just to be able to find exactly when a signal makes a transition.)
The Aldec viewer does this particularly well.

I implemented it this evening...uploaded it to metalab.unc.edu but
it'll probably take a couple of days to get online (I can't ssh into
linux-workshop for some reason lately so it isn't there).

Thanks Tony.

Do you have a URL where I can download it in the meantime? I looked
around the metalab.unc.edu site but could only find 1.3.32.

Regards,
Allan.

 

[Anthony J Bybell]

Allan Herriman <allan.herriman.hates.spam@ctam.com.au.invalid> wrote in message news:<qcpurv0va1gp7h5jo6jtr93mjgj0v1e2pq@4ax.com>...

Do you have a URL where I can download it in the meantime? I looked
around the metalab.unc.edu site but could only find 1.3.32.

Don't have a URL because the server I typically upload to moved to a
different physical machine and the sysadmin didn't migrate my shell
access. He has ftp locked down to users' home directories and my
website is on a different mountpoint which means I can't upload it
either...

Note: 1.3.34 is the latest. Fixes for compiles for FreeBSD (what, no
getopt_long?!?) in anticipation of doing the win32 port and there was
a problem with the cursor snap in some cases when the left hand side
of the screen wasn't at time zero.

The fix for anyone unfortunate enough to snag 1.3.33:

xlft = (lft + t->shift - tims.start) * pxns;
xrgh = (rgh + t->shift - tims.start) * pxns;

....these equations were missing tims.start in the original. Whoops.


(*) It "should" be available on metalab the next couple of days. If
not, I can email the tarball to you; the rocketmail email address is a
real one so send me a quick note if that's what you want. Most likely
I'll have ssh access the instant metalab puts the files online.

Later,
Tony

 

[Enes Erdin]

Sorry to revive such an old discussion but I think this is the perfect place for putting my question. As the developer is here.

Is there a way for saving the wave format (for each signal) and reload it for the next (day) simulation in GTKWave. Like the ModelSim's do file format in a fashion like:

add wave -color #AABBFF -hexadecimal sim:uut/BUS

Thanks.