Help needed in creating URM using SV

Jalli,

When using the SystemVerliog utilities in IPCM, the simplest way is to use the included *.args files. These will provide all the necessary command line options, including the VPI library you're missing. Use the apropriate file based on your compile flow:

[The following is taken from the IPCM utiltilities guide - section 2.1.1]

For irun:
% irun -f $IPCM_HOME/util_lib/urm_util/sv/irun.args ...

For ncvlog/ncelab/ncsim flow:
% ncvlog -f $IPCM_HOME/util_lib/urm_util/sv/ncvlog.args ...
% ncelab -f $IPCM_HOME/util_lib/urm_util/sv/ncelab.args ...
% ncsim -f $IPCM_HOME/util_lib/urm_util/sv/ncsim.args ...

For ncverilog:
% ncverilog -f $IPCM_HOME/util_lib/urm_util/sv/ncverilog.args \
+tcl+"@source $IPCM_HOME/util_lib/urm_util/sv/urm_util.tcl ...

Regards,

Zeev.

Hi Zeev,

Thanks a lot for Ur info. but I wanna know one more thing!

What shud i do if I'm not using IPCM methodology. I'm just using system verilog and I want to include vpi lib ?

Regards,
Jalli

Hi Jalli.

You did originally say that you're using URM!
URM is just a single component of IPCM, and I think Zeev meant to say URM, not IPCM in his reply.

The libraries Zeev told you to use are specific to URM, so you're not pulling any extra bloat-ware ;-)
In fact the URM module-based library is a very small amount of code, so it really doesn't hurt to compile it into your env.

To answer your exact question, if you're only using pure SV language and not IPCM (URM?) then you won't need this VPI library because you aren't using the URM functions!

Hi Zeev & Steve,

Ok...I think I need to be clear of what exactly I'm looking for.

I'm using URM methodology and creating specific components in SV language but i'm not using IPCM libraries or thier components.
Also, since I'm using SV language and to support few already existing features I'm using two files i.e., "urm_defines.svh" and "urm_util_pkg.sv" files. So, when I include these files and compile using ncverilog in demo.sh I get these three warnings.

I actually tried loading VPI library as Zeev suggested but failed in those attempts. And I couldn't find out where exactly I was wrong. So, please help me in this regards.

Thanks in advance,
Regards,
Jalli

Hi Jalli.

Is there any particular reason why you're not using the URM library functions?
If you're worried about portability, note that the URM library is open source (i.e. you can see the code and compile it on other platforms).

I assume that you just want access to the various constants and enum types that URM defines.
In this case, I'd still suggest that you compile the whole URM library as Zeev showed you. This would help ensure that if you integrate a URM component from another team or vendor then it'll compile smoothly alongside your code.

If you really cannot live with compiling all the URM files, and you are absolutely certain that you'll never ever need to integrate any other UVCs, then I suggest you look at the urm_util_pkg.sv and copy out the definitions that you require. Put them into a new file of your own, and just compile that.

We really can't emphasise enough thought, that where customers do selectively apply bits of URM (and eRM before it), they tend to get into problems later on as their environments get bigger, or when they try to make legacy components fit with newer components later on...
Always try to think about reuse and how your decisions may come back to haunt you later!