Stats

  • Locked Locked
  • Replies 5
  • Subscribers 66
  • Views 14170
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Issue while using already compiled libraries in IUS-8.2

Shunty

Hi All,

I am stucked at one situation while using IUS-8.2. I have some compiled libraries of vhdl in one INCA_libs folder.

Now In my System Verilog environment, I want to use those already compiled libraries of VHDL.

So I want to use the  INCA_libs folder. what i did is,

While running my environment using irun, i used -cdslib switch to use those libraries.

irun -cdslib <PATH_TO_DESIGN_LIB_CDS_LIB>  -f <VE.f>

Where,  PATH_TO_DESIGN_LIB_CDS_LIB is a cds.lib file of the already compiled INCA_libs of design.

VE.f contains my Verification Environment related file.


Is this a correct way to do this? If not then please suggest correct one.

 

There is one strange problem occurs while using this command,

When the packages  are imported inside the VE files shows this error,

import imp_1::*;
           |
ncvlog: *E,MULTPK (test.sv,7|11): Multiple (2) packages named "imp_1" were found in the searched libraries:
                -> found verilog_package worklib.imp_1:sv (VST)
                -> found verilog_package worklib.imp_1:sv (VST).
import imp_1::*;

 

To debug this,
When I opened cds.lib of my design's INCA_libs, last 2 statements were something like this,

DEFINE worklib worklib
DEFINE Mux worklib

When I removed the last statement which was for mapping purpose, The above error of importing the package got resolved.

But I did not get the successful loading of libraries because simulator gave me an error when I created an instace of  Mux entity.

 

Anyone has any idea about this?

 

-Shunty

 

 

 

 

 

Parents

  • laohan,

    Explaining the actions of the library system in IUS can be pretty complex. It has to be all things to all people, so there's a lot of ins-and-outs that are probably too much for a posting on a web forum. That being said however, he's why changing your filename ended up with a duplicate package.

    IUS stores its compiled objects with 3 attributes that identify it, library, objectname and view. By default, irun takes the view name from the suffix of the source file it is compiling. So a package called mypackage from a file mypackagefile.pkg would be compiled into work.mypackage:pkg. If you change the filename to mypackagefile.sv, you get a new object added to the database, work.mypackage:sv. You can control this explicitly by using the -view option on irun, but as you've found it is easier to remove the INCA_libs and start again.

Reply

  • laohan,

    Explaining the actions of the library system in IUS can be pretty complex. It has to be all things to all people, so there's a lot of ins-and-outs that are probably too much for a posting on a web forum. That being said however, he's why changing your filename ended up with a duplicate package.

    IUS stores its compiled objects with 3 attributes that identify it, library, objectname and view. By default, irun takes the view name from the suffix of the source file it is compiling. So a package called mypackage from a file mypackagefile.pkg would be compiled into work.mypackage:pkg. If you change the filename to mypackagefile.sv, you get a new object added to the database, work.mypackage:sv. You can control this explicitly by using the -view option on irun, but as you've found it is easier to remove the INCA_libs and start again.

Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.