HI All,
As Richedelman mentioned, below method will work for while using the precompiled libraries for uvm_reg-*(eg: uvm_reg-1.1),which where used when we are using the uvm register model in ovm.I given the way to use the pre-compiled libraries for register model.
In modelsim.ini local file provied the variable like mtiUvmReg = $MODEL_TECH/…/uvm_reg-1.1
Provied this variable in the LibrarySearchPath = mtiAvm mtiOvm mtiUvm mtiUvmReg mtiUPF
****other wise you will get the error like as below mentioned by Richedelmen.
thanks to Richedelman ,i used this way to fix my uvm_reg package issue.
i hope this will help …
thanks
Given below is the post replied by Richedelman,this is for reference in my post*******
Re: Compiling UVM Express examples with ModelSim 10.1b
Hi Joern,
We highly recommend that people use the built-in UVM - the SystemVerilog and the DPI-C code are both pre-compiled, and Questa will pre-load it for you. UVM Express has the same recommendation - use the built-in UVM.
I ran Questa 10.1b (win32) and ModelSim 10.1b (linux) using UVM Express 0.7, compiling and running the examples. Each time, the built-in UVM was automatically used. I didn’t need to download the Accellera source code.
In the default modelsim.ini file from 10.1b, the LibrarySearchPath is defined as:
LibrarySearchPath = mtiAvm mtiOvm mtiUvm mtiUPF
If I change this line (removing the mtiUvm setting):
LibrarySearchPath = mtiAvm mtiOvm mtiUPF
then I get an error:
** Error: …/abc_pkg/abc_pkg.sv(22): Could not find the package (uvm_pkg). Design read will continue, but expect a cascade of errors after this failure. Furthermore if you experience a vopt-7 error immediately before this error then please check the package names or the library search paths on the command line.
Could it be possible that you are using a modelsim.ini file that does not have mtiUvm in the search path?
Can you share the error messages you saw?
Best regards,
rich