Stats

  • Locked Locked
  • Replies 4
  • Subscribers 124
  • Views 16828
  • 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

VerilogA parsing problem

StanleyN
When I check and save a verilogA file from cadence library, cadence always checks the syntax of the VerilogA file.

But now if I do it, I got the following error
 

WARNING : There is some issue in invoking spectre command for parsing the text file  <path to verilogA file>
         Make sure that the setting is proper

Error: Failed syntax check for veriloga text of cell <cellname>

What setting should I change?

Thanks for your help
Parents
  • Andrew Beckett

    You probably don't have spectre in your UNIX path before you start virtuoso. If you type "which spectre" from the UNIX command line, it needs to find spectre. This would be solved by adding <MMSIMinstDIr>/tools/bin to your $path variable (in csh) or $PATH variable (in sh/bash/ksh).

    Regards,

    Andrew.

  • subramanya007
    in reply to Andrew Beckett

    I have the same issue, but spectre is on my unix path. Typing "which spectre" gives the path of the spectre command line being used. What else could be causing this?

  • Andrew Beckett
    in reply to subramanya007

    I did some checks, and this can happen if rather than having spectre from a Cadence MMSIM or SPECTRE installation in your path, you have a wrapper script called "spectre" in your path. So if "which spectre" doesn't give a path like <SPECTREinstDir>/bin/spectre or <SPECTREinstDir>/tools/bin/spectre (where <SPECTREinstDir> is the root of one of our installations) you may have this problem.

    What the code actually checks is whether the "feature" information can be found. We have a number of things in the IC environment which are adapted depending on the capabilities of the MMSIM/SPECTRE installation you have in your path. With a direct path to the spectre installation, this can be found, but if a wrapper script is in the way, it can't...

    The workaround (and you should only do this if you are using a wrapper) is to set the SPECTRE_FEATURE_FILE UNIX environment variable before starting virtuoso:

    setenv SPECTRE_FEATURE_FILE /export/home/apps/SPECTRE171_isr/tools/spectre/etc/files/features.dat

    or

    export SPECTRE_FEATURE_FILE=/export/home/apps/SPECTRE171_isr/tools/spectre/etc/files/features.dat

    (of course, the /export/home/apps?SPECTRE171_isr bit will depend on where your SPECTRE/MMSIM installation is located, and whether you use setenv or export will depend on whether you're using csh or ksh/bash).

    Regards,

    Andrew.

  • subramanya007
    in reply to Andrew Beckett

    Great! That worked. You are awesome.

Reply
  • subramanya007
    in reply to Andrew Beckett

    Great! That worked. You are awesome.

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.