Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 3572
  • 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

VHDL-AMS std and ieee libraries not found/empty

pepijndevos

I'm trying to set up a VHDL-AMS simulation, so I made a new cell, selected the vhdlamstext type, and copied some example from the web. But when I hit the save and compile button, I first got the following NOLSTD error:

https://www.edaboard.com/showthread.php?27832-Simulating-a-VHDL-design-in-ldv5-1

So I added said file to my cds.lib and tried again. But now I'm getting this:

ncvhdl_p: *F,DLUNNE: Can't find STANDARD at /cadappl/ictools/cadence_ic/6.1.7.721/tools/inca/files/STD.

If I go over to the Library Browser, it indeed shows that the library is completely empty. Properties show it has the following files attached.

In the file system I've also found a STD.src folder. Is there a way to recompile the library properly? Supposedly this folder includes precompiled versions, but looks like not really.

Parents
  • Andrew Beckett

    Normally you'd include the IEEE libraries from the XCELIUM (or older INCISIVE) release stream that you're using. So normally something like:

    SOFTINCLUDE $(inst_root_with:tools/bin/xrun)/tools/inca/files/cds.lib

    (you might change xrun for irun if using INCISIVE).

    If the release is installed properly, it will have been configured at the time of installation, which means the libraries would have been compiled with that version of INCISIVE/XCELIUM. If taking them from the IC stream, then you are dependent upon them having been compiled with the same digital simulator version you're using right now.

    That article you found is ancient and is not great advice (even in 2004), as $CDS_INST_DIR is a env var that is not really used any more because it was ambiguous as to which release stream was being talked about. Originally (back in 1995 time frame) all tools were in one stream (there were fewer tools from Cadence then) and so referring to a single installation made some sense (although that was pre-inca, so even then things had changed by 2004).

    Andrew.

Reply
  • Andrew Beckett

    Normally you'd include the IEEE libraries from the XCELIUM (or older INCISIVE) release stream that you're using. So normally something like:

    SOFTINCLUDE $(inst_root_with:tools/bin/xrun)/tools/inca/files/cds.lib

    (you might change xrun for irun if using INCISIVE).

    If the release is installed properly, it will have been configured at the time of installation, which means the libraries would have been compiled with that version of INCISIVE/XCELIUM. If taking them from the IC stream, then you are dependent upon them having been compiled with the same digital simulator version you're using right now.

    That article you found is ancient and is not great advice (even in 2004), as $CDS_INST_DIR is a env var that is not really used any more because it was ambiguous as to which release stream was being talked about. Originally (back in 1995 time frame) all tools were in one stream (there were fewer tools from Cadence then) and so referring to a single installation made some sense (although that was pre-inca, so even then things had changed by 2004).

    Andrew.

Children
  • pepijndevos
    in reply to Andrew Beckett

    Thank you for setting me on the right track! I had to use irun, because my university apparently runs INCISIVE. I also had to link to the vhdlams version, as you yourself wrote elsewhere: https://community.cadence.com/cadence_technology_forums/f/mixed-signal-design/28153/issue-in-vhdl-ams-compilation/1330030#1330030 I will try to add this information to the university wiki.

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.