• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Functional Verification
  3. IUS CDSLIB setting on different version

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 65
  • Views 13990
  • 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

IUS CDSLIB setting on different version

ShawnLogan
ShawnLogan over 17 years ago

Hi all:
  
   I have some question about the IUS enviroment setting.I simulate a design RTL in IUS5.4 or
IUS5.5.when setting enviroment,I use the default CDSLIB and HDLVAR.Then use the comand
"ncvlog -message -f filelist.f" to compile the design.The compile pass without errors.But next setp use the command "ncelab -message -access +RWC worklib.inp_tb" to elaborate the deign,occur these errores as follow:
  
   ncelab: 05.50-p004: (c) Copyright 1995-2005 Cadence Design Systems, Inc.
ncelab: *E,DLMKDF: Unable to add default DEFINE std       /cad/cadence/IUS55-linux/tools/inca/files/STD.
ncelab: *E,DLMKDF: Unable to add default DEFINE synopsys  /cad/cadence/IUS55-linux/tools/inca/files/SYNOPSYS.
ncelab: *E,DLMKDF: Unable to add default DEFINE ieee      /cad/cadence/IUS55-linux/tools/inca/files/IEEE.
ncelab: *E,DLMKDF: Unable to add default DEFINE ambit     /cad/cadence/IUS55-linux/tools/inca/files/AMBIT.
ncelab: *E,DLMKDF: Unable to add default DEFINE vital_memory /cad/cadence/IUS55-linux/tools/inca/files/VITAL_MEMORY.
ncelab: *E,DLMKDF: Unable to add default DEFINE ncutils /cad/cadence/IUS55-linux/tools/inca/files/NCUTILS.
ncelab: *E,DLMKDF: Unable to add default DEFINE cds_assertions /cad/cadence/IUS55-linux/tools/inca/files/CDS_ASSERTIONS.
ncelab: *F,DLINIT: Failed to initialize library system interface.

  But I don't use the default CDSLIB,creat the file cdslib and hdlvar,as follow:
     file cdslib:
 
#INCLUDE $VENVHOME/tools/inca/files/cds.lib
## CENTRAL NC WORK DIRECTORIES #####
##################################################################
#DEFINE design_lib       $DB_DIR/design_lib
##################################################################

#DEFINE ieee $CDS_DIR/tools/inca/files/IEEE.src
#DEFINE std $CDS_DIR/tools/inca/files/STD.src
#DEFINE synopsys $CDS_DIR/tools/inca/files/SYNOPSYS.src

DEFINE tech_lib  $DB_DIR/tech_lib
DEFINE rtl_work  $DB_DIR/rtl_work
DEFINE rtl_work_linux $DB_DIR/rtl_work_linux

  use the below command "ncvlog -message -work rtl_work -f vlist"
 and "ncelab -message -access +RWC rtl_work.inp_tb".There are not error.

   I want to know :
         the IUS version 5.4 or 5.5 which must use the created CDSLIB ?
  
   Then I do the same simulation using IUS6.11, and use the defualt CDSLIB.
 It is OK, don't occur error on elaborating.
   Does the IUS6.11 automaticly load the std\IEEE\synopsys,etc LIB?

   Thanks!


Originally posted in cdnusers.org by shawn-1
  • Cancel
  • archive
    archive over 17 years ago

    Are you using the -cdslib argument to ncvlog to point to your cds.lib file?

    Tim


    Originally posted in cdnusers.org by tpylant
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    Hi Tim:

    Because I use the default cds.lib in the version 5.4 or 5.6 of IUS,I don't specify another cdslib,and it need not respecify.So
    it need not use the -cdslib argument to ncvlog.But when redefine the cds.lib,I need use the -cdslib argument to ncvlog,and the compile and elaberate is OK.Then why not use the default cds.lib in the version 5.4 or 5.6 of IUS?Howerver I use the version 5.8 or 6.1 of IUS,and don't specify the cds.lb,only use the default cds.lb,the compile and elaberate is OK, and not occur the error.

    thanks a lot !

    shawn lieu


    Originally posted in cdnusers.org by shawn-1
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information