Stats

  • Locked Locked
  • Replies 9
  • Subscribers 125
  • Views 19237
  • 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

Running simulation on verilogAMS

Miguel V

Hi,

I have a coworker I've been trying to help to get verilogAMS to run and to be able to run a simulation.  At first verilogAMS wouldn't compile because it couldn't find the 64-bit version of ncvlog.  After looking at the paths in the wrapper, i added the path to the 64-bit version in IC (I know there is also one under MMSIM).  Anyways, this time it could find it, but it would not recognize "constants.vams" or other files unless I type the full path to it.  After using the full path, the verilogams view compiled producing a symbol.  

Now the problem is that my coworker is setting up a schematic with both veriloga and verilogams instances and then trying to run a simulation.  We kept getting errors and when I read a little more, I found out that we need to use the AMS simulation tool, not spectre.  We created a config view for the schematic and in ADE L, we set "ams" as the simulation tool.  After that we get the following warning and error message in the CIW:

     *WARNING* The Virtuoso Analog Design Environment (ADE) creates a user interface (UI) to match the features of the particular
     version of IUS you are using. The software could not find the 'feature file' in the IUS hierarchy that lists the features
     available in this version of IUS. You might be using a wrapper script around the simulator such that 'which ncsim' returns
     your wrapper script and not the simulator in the IUS hierarchy. For now, ADE will create a UI to match the latest version
     of the simulator. If you are using an older version and do not want to see the UI for features that are not available in
     that version, you can set the following variable according to the simulator version you are using:
     setenv AMS_FEATURE_FILE /home/pathForIUS/tools/affirma_ams/etc/files/amssim.dat

     *Error* strcat: argument #1 should be either a string or a symbol (type template = "S") - nil

I tried to look for this "amssim.dat" file in our install directory for cadence tools so that I can add it to the wrapper, but II'm not sure where it is exactly.  This is all new to me and I wish I could help my coworker more, so any help on how to setup and run a verilogAMS simulation would be helpful.

Thanks,

Miguel

Parents
  • Miguel V

    Also, after doing this, I can't exit out of cadence.  Every time I go to close cadence, I get the following error:

              hiDBoxOK(hiQuitDBox)
              t
              *Error* length: argument must be a list or an array - slotUnbound

    To get around this, I have to manually kill the virtuoso process.

  • Andrew Beckett
    in reply to Miguel V

    You need to have an INCISIVE (e.g. INCISIVE152) or XCELIUM (e.g. XCELIUM1710 or XCELIUM1803) release installed and in your UNIX path (<instDir>/bin in your path) to access the AMS simulator.

    Whilst there are parts of INCISIVE shipped with the IC stream to provide some supporting tools, these will not work as a simulator. You should not include them in your path. There is no need to specifically put 64bit paths in your path either - this is controlled via the $CDS_AUTO_64BIT env var (see the documentation for more details).

    Do not set the AMS_FEATURE_FILE either - this is a backup for specific situations (such as using wrapper scripts which hide where the actual installation is). Normally the feature file (which allows ADE to show forms that reflect the features available in the simulator version you're using) is found automatically based on what is in your path.

    Regards,

    Andrew.

  • Miguel V
    in reply to Andrew Beckett

    Hi Andrew,

    We do have INCISIV and made sure it's in our wrapper.  I made sure to set CDS_AUTO_64BIT to ALL in my .cshrc_local file and sourced it.  When I try to compile the verilogams view, I still get the following error:

    Can't find 64 bit executable "<cadence_inst_dir>/ic/06.16.120/tools/bin/64bit/ncvlog", exiting

    It keeps trying to look for ncvlog in that directory even though I have the path to the 32bit version included in the PATH and I assume with CDS_AUTO_64BIT it would look in the 64bit folder.  What else could I be missing?  Is there a particular environment variable I can set specifically for ncvlog?

Reply
  • Miguel V
    in reply to Andrew Beckett

    Hi Andrew,

    We do have INCISIV and made sure it's in our wrapper.  I made sure to set CDS_AUTO_64BIT to ALL in my .cshrc_local file and sourced it.  When I try to compile the verilogams view, I still get the following error:

    Can't find 64 bit executable "<cadence_inst_dir>/ic/06.16.120/tools/bin/64bit/ncvlog", exiting

    It keeps trying to look for ncvlog in that directory even though I have the path to the 32bit version included in the PATH and I assume with CDS_AUTO_64BIT it would look in the 64bit folder.  What else could I be missing?  Is there a particular environment variable I can set specifically for ncvlog?

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.