search

IObundle / iob-cache

Verilog Configurable Cache
MIT License
167 stars 32 forks source link

Do not close an open gtkwave automatically #132

Closed codingUniv closed 2 years ago

codingUniv commented 2 years ago

I suggest not to close an open gtkwave automatically when running a new simulation. There might be situations when parallel debug sessions are required (different VCD files, different rtl, etc.)

jjts commented 2 years ago

Closing and reopening is done to reload the vcd file. It is possible to manually reload the vcd without closing gtkwave, so both options are possible without thinking of other situations. If gtkwave is closed we must also be careful to manually save the current waveforms to display in the .gtkw file. So either option are possible.

As for other situations, they need to be clearly identified as we are not worried about potential scenarios but only about the scenarios that exist now.

jjts commented 2 years ago

Ok for the other comments.

codingUniv commented 2 years ago

All indicated options are interesting. In addition, we might need to have parallel debug sessions, for example: analyze the waveforms of a given RTL while running a simulation of another RTL in parallel. The current settings will let the second simulation end by closing the first gtkwave session in order to open a new one. This might be challenging for a user who should not stop the ongoing debug.

jjts commented 2 years ago

What is there is good enough

What we really need is the readme and docs

jjts commented 2 years ago

Please settle in a mode and documented in the readme. Right now my only interest is that there's a way to visualize waveforms even if not the best

jjts commented 2 years ago

After that I will close the issue