Modelsim Viewer License Problem

Modelsim Viewer License Problem Average ratng: 4,6/5 4677 reviews

Hi,

Welcome to the Licensing and Installation community. With community members and Mentor Graphics technical experts we hope to quickly resolve your installation and licensing problems. HTML View all. Search the licensing and installation community. Modelsim License Server 4 months ago. Server license supports ModelSim viewer 2014.100. The details of this issue are provided in this link: Vulnerability Note VU#485744 - Flexera Software.

Modelsim license cost

I think I have a similar issue as Bjorn had.

Modelsim 10.6

I am working on a project where I have a bunch of Modelsim projects for simulation of our new IP (written in VHDL), and I have a window of opportunity to refactor it to use something more automatic for build & test.

Our current workflow is:

  1. compile files with modelsim / TCL script
  2. run TCLscript to show the saved waveform
  3. visually inspect waveform & output files (mostly images)
  4. add more signals, save wave.do, rerun simulation, stare at the waveform again
License

I used OSVVM before, and wrote a couple of automatic tests, and it worked ok with scripting everything with TCL & occasionally visually inspecting the waveform.

That being said, I hate TCL and would very much like to replace it with Python, especially if there is a prospect of integrating some unit tests for our code.

Modelsim For Windows 10

I tried Vunit before, but my issue is that I didn't figure out a smart way to save the waveform so I can rerun testcases while looking at the same signals of interest, instead of having to add them again manually.

I would like to use Vunit to add some automatic tests, but I need to support the old way of doing things in Modelsim (10.5b) because full test automation is just not feasible at this point. But I would like to set up a full regression test suite as soon as possible.

I know python & git so I might be able to help if you point me in the right direction.

P.S.
Should I open a new issue, or is it OK to continue this discussion here?