On Wed, Feb 11, 2009 at 9:13 PM, Tristan Gingold <[email protected]> wrote: > On Wed, Feb 11, 2009 at 05:15:59PM -0800, Peter LaDow wrote: >> I have some testbench code that communicates (via signals) in >> zero-time. For example, assume I have modules tbA and tbB. tbA sends >> data to tbB by doing: > > [...] > >> The idea is that I can exchange information between testbench blocks >> in zero-time (i.e. not advancing the simulation) for things like >> control and logging. I've paraphrased it above, but things aren't >> working. I'd like to visualize the problem. Gtkwave won't display >> anything because it seems to ignore the deltas. And using ghwdump, I >> get the signal alias (apparently) rather than the name, and vectors >> are split into individual aliases. >> >> So, is there any way to visualize these delta events so I can debug my >> problems? > > Delta events are not stored into vcd or ghw files. I once thought about > dumping > them to .ghw but then gtkwave must be enhanced to display them. > > The only way to display deltas is to use --trace-signals option.
Thanks for the tip. The --trace-signals gave me enough information to debug things. Pete -- -- "To love for the sake of being loved is human; to love for the sake of loving is Angelic." -- Alphonse de Lamartine _______________________________________________ Ghdl-discuss mailing list [email protected] https://mail.gna.org/listinfo/ghdl-discuss
