Modelsim Viewer License Problem

0126
Modelsim Viewer License Problem 3,6/5 9733 reviews

I have installed student edition. I am getting this fatal error. Please help me out. # // ModelSim PE Student Edition 6.4c Dec 8 2008 # // # // Copyright 1991-2008 Mentor Graphics Corporation # // All Rights Reserved. # // # // THIS WORK CONTAINS TRADE SECRET AND # // PROPRIETARY INFORMATION WHICH IS THE PROPERTY # // OF MENTOR GRAPHICS CORPORATION OR ITS LICENSORS # // AND IS SUBJECT TO LICENSE TERMS. # // # # // NOT FOR CORPORATE OR PRODUCTION USE. # // THE ModelSim PE Student Edition IS NOT A SUPPORTED PRODUCT.

# // FOR HIGHER EDUCATION PURPOSES ONLY # // # vsim work.counter work.testcounter #. FATAL ERROR: ModelSim PE Student Edition licensing failure due to one or more problems with the license key such as: # - it is not found # - it has expired # - it is not for this user # - it is not for this computer # - it is not for this version of ModelSim PE Student Edition.

Modelsim Viewer License Problem For Windows 10

# # Please go to and download an updated copy of the ModelSim PE Student Edition. # Error loading design anildesh 20:32.

License

Log -r /. vunitrun dataset save sim sim.wlf quit -sim dataset open sim sim.wlf How can we make it easier to use?

Method 1 We could automate this by adding a -gui=view flag to run a test case and open the.wlf with a viewer license afterwards (Maybe even support GTKWave). The problem is how to specify what to log, we could add a flag for that or a flag to point out a.do file. Method 2 We could wrap the three last TCL commands of this method to save a dataset and re-open it without a simulation license as a pre-loaded TCL procedure just like vunitload and vunitrun. It could be named vunitview What do you think about the above? Any method you prefer? Hi, I think I have a similar issue as Bjorn had. 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:. compile files with modelsim / TCL script.

run TCLscript to show the saved waveform. visually inspect waveform & output files (mostly images). add more signals, save wave.do, rerun simulation, stare at the waveform again 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. 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. Should I open a new issue, or is it OK to continue this discussion here? I reread your suggested methods 1 & 2, and I think I understood them this time.

I have two problems with them:. they don't filter the signals that are logged into the.wlf. I would have to enter some additional commands manually into the modelsim command line interface, instead of just using 'up-arrow + enter' to recompile and show the waveform as the simulation is running (we have some very long simulations) This makes the approaches inferior to just having a modelsim TCL file that automates everything.

This entry was posted on 26.01.2020.