Hi Andre,
Do you mean that sometimes you add several times the same signal in the
waveform in order to be able to compare them with different signals ?
It also happened for me to do the same.
Currently what the code does is looking for every signal in the design
and then look if it exists or not in the tree of the signals to be
displayed. The order of the signal paths in the wave option file has no
impact as the signals are displayed in the order they are read from the
design. And no, dupplication of signals isn't possible with this
approach. So to have this feature I need first to change the approach :
read each signal from the tree and compare it with the design. This way,
duplication of signals will be possible. I believe this feature deserves
to be in my TODO list.
Jonas
Le 25. 07. 16 à 20:52, Andre a écrit :
Hi Jonas,
Something occurs to me with respect to the duplication of signals.
One of the things that I have done before is to copy a signal and then
place the copy of the signal along side that of another, for example a
clock while sitting next to an AHB Bus set.
So removing a duplicate signal may not have been a mistake but a
deliberate action.
Best Regards
Andre'
------------------------------------------------------------------------
*From:* Ghdl-discuss <ghdl-discuss-boun...@gna.org> on behalf of
ghdl-discuss-requ...@gna.org <ghdl-discuss-requ...@gna.org>
*Sent:* 25 July 2016 10:00
*To:* ghdl-discuss@gna.org
*Subject:* Ghdl-discuss Digest, Vol 128, Issue 24
Send Ghdl-discuss mailing list submissions to
ghdl-discuss@gna.org
To subscribe or unsubscribe via the World Wide Web, visit
https://mail.gna.org/listinfo/ghdl-discuss
Ghdl-discuss -- GHDL discuss list - News Info Page
<https://mail.gna.org/listinfo/ghdl-discuss>
mail.gna.org
To see the collection of prior postings to the list, visit the
Ghdl-discuss Archives. Using Ghdl-discuss: To post a message to all
the list members ...
or, via email, send a message with subject or body 'help' to
ghdl-discuss-requ...@gna.org
You can reach the person managing the list at
ghdl-discuss-ow...@gna.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Ghdl-discuss digest..."
Today's Topics:
1. Re: Signal selection in wave (Rene Doss)
----------------------------------------------------------------------
Message: 1
Date: Sun, 24 Jul 2016 15:26:23 +0200
From: Rene Doss <d...@gmx.de>
To: GHDL discuss list <ghdl-discuss@gna.org>
Subject: Re: [Ghdl-discuss] Signal selection in wave
Message-ID: <5794c1ff.1050...@gmx.de>
Content-Type: text/plain; charset=utf-8
>>Tell me if you have any suggestion.
yes I have something, but I do not know if this the correct discussion
round.
I say something what I have seen for long time. This information is from
my deeper brain.
Gtkwave has included shared memory functions. (I think it is only
possible under linux)
If ghdl can store the signal in a shared memory the current signals can
be refreshed by gtkwave directly into the screen. This is interacting
process. The use can follow the simulation online.
Rene
Am 23.07.2016 um 11:21 schrieb Jonas Baggett:
> Hello,
>
> I made a roadmap for the signal selection feature :
>
> Version 1.0 :
> - Finishing code review with Tristan
> - Add signal selection support for other format than ghw
> - Add a help description in Simulation_and_runtime.rst and
> grt-options.adb
> - Should I add a wave option file example in doc/ too ?
>
> Version 1.1 :
> - Create an option that works like --disp-tree but prints the design
> tree in
> the wave option file format (could be in 1.0 too).
> - Simple wildcards (/top/sub1/*, /top/sub*/*)
> - Double wildcards (/top/**, top/sub*/**))
> Remark : *** is no more needed since ** will have it's behavior and
> the old
> behavior of ** can be achieve with */** (top/*/**) which makes more
> clear that
> we aren't displaying any signals in the first level of /top
>
> Version 1.2 :
> - Simple regexp (top/sub[1-3]/sig[a-z])
> - Negation (! top/sub2/sigk)
>
> Version 1.3 :
> - Selecting element in an array (/top/sub3/my_array(5))
> - Selecting element in a record (/top/sub3/my_record.field)
>
> Version 1.4
> - Selection of port and architecture signals
> (top/sub1/arch/*:port and top/sub1/arch/*:architecture)
>
> Tell me if you have any suggestion.
>
> Jonas
>
> _______________________________________________
> Ghdl-discuss mailing list
> Ghdl-discuss@gna.org
> https://mail.gna.org/listinfo/ghdl-discuss
------------------------------
Subject: Digest Footer
_______________________________________________
Ghdl-discuss mailing list
Ghdl-discuss@gna.org
https://mail.gna.org/listinfo/ghdl-discuss
------------------------------
End of Ghdl-discuss Digest, Vol 128, Issue 24
*********************************************
_______________________________________________
Ghdl-discuss mailing list
Ghdl-discuss@gna.org
https://mail.gna.org/listinfo/ghdl-discuss
_______________________________________________
Ghdl-discuss mailing list
Ghdl-discuss@gna.org
https://mail.gna.org/listinfo/ghdl-discuss
