Stats

  • Locked Locked
  • Replies 3
  • Subscribers 61
  • Views 10178
  • 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

Cadence 6.1.3 libraries

StreamCX

I try to import ncvhdl but next error appeared in vhdlin.summary

And this is screen

/* [URL=http://img519.imageshack.us/my.php?image=screenshotz.png][IMG]img519.imageshack.us/.../URL] */

 TOOL:    ncvhdl    06.11-s016: Started on Mar 03, 2009 at 09:42:50 NOVT
ncvhdl
    -NOCOPYRIGHT
    -messages
    -smartorder
    -LOGFILE /tmp/vhdlin_anal.a2495
    -WORK cds.lib
    -ERROR 10
    -CDSLIB /tmp/ncvhdl_cdsliba2495
    /cds/ic61/tools.lnx86/dfII/samples/vhdlin/Test1//or_gate.a.vhd

ncvhdl_p: *F,WRKBAD: logical library name WORK is bound to a bad library name 'cds.lib'.
TOOL:    ncvhdl    06.11-s016: Exiting on Mar 03, 2009 at 09:42:50 NOVT  (total: 00:00:00)
WARNING (VHDLIN-226):


How can I solve this problem?

  • the file indicated in the -CDSLIB argument (/tmp/ncvhdl_cdsliba249) should have logical and physical path definitions.  eg...

     define mywork  ./some/path/to/mywork

     define otherlib  ./some/path/to/otherlib

     

    when doing your compile with ncvhdl, you can specify into which library the objects get compiled with the -WORK command line option.  The valid argument to -WORK is a logical library name that is defined in the CDSLIB referenced file.  So in the example provided above the valid arguments could be either mywork or otherlib.

    Hope that helps.

    Mickey

  •  Mickey

    Thank You.

    But I solve this problem by replacing cds.lib in work directory.

    This trouble was with my cds.lib. 

    I can not check your solution beacuse i am not in university now, where Cadence installed.

    But another question.

    How can I add all Cadence libraries to a library manager?

  • Hi,

    to include all Cadence libraries in your session you can include the cds.lib in

    <path to IC installation directory>/share/cdssetup/dfII/cds.lib 

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.