• 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. Custom IC Design
  3. Error during ADE spectre simulation

Stats

  • Locked Locked
  • Replies 12
  • Subscribers 125
  • Views 21374
  • 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

Error during ADE spectre simulation

NorNand
NorNand over 5 years ago

Hello,

I am facing the problem below after running the simulation from ADE spectre,  I made simple CMOS inverter to demonstrate you this error. It looks like ADE is not able to read the model file, I am using the ams 0.35 um technology.

My cadence version is IC6.1.5 64 bit

Error found by spectre in `Test_bench_1':`I0', during hierarchy flattening.
ERROR (SFE-2001): "/home/opt/ams410/c35/cmos53.scs" 29: `I0.MN0': Problem in evaluating 
conditional expression for instantiation: Unknown parameter name `modn' found in expression.

ERROR (SFE-2001): "/home/opt/ams410/c35/cmos53.scs" 593: `I0.MP0': Problem in evaluating 
conditional expression for instantiation: Unknown parameter name `modp' found in expression.

Error found by spectre in `modn':`I0.MN0', in `Test_bench_1':`I0', during 
hierarchy flattening.
ERROR (SFE-1997): "/home/opt/ams410/c35/cmos53.scs" 33: I0.MN0.notvalid: parameter 
`errorif': Unknown parameter name `modn' found in expression.

Error found by spectre in `modp':`I0.MP0', in `Test_bench_1':`I0', during 
hierarchy flattening.
ERROR (SFE-1997): "/home/opt/ams410/c35/cmos53.scs" 597: I0.MP0.notvalid: parameter 
`errorif': Unknown parameter name `modp' found in expression.
--

Thank you in advance
  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 5 years ago

    You probably will need to contact the providers of the models (AMS) - I suspect you're probably not including an important model file which defines these parameters...

    Andrew.

    • Cancel
    • Vote Up +2 Vote Down
    • Cancel
  • NorNand
    NorNand over 5 years ago in reply to Andrew Beckett

    Thank you Andrew for your reply,

    This error I got is just after we reinstalled cadence in a new server, 

    I was not responsible for installing cadence but I copied the technology files from my old account to my account in the new server,

    besides that, I copied the following files as it is without any change

    1- .amsdlnit

    2- .amsenv

    3- .bashrc

    4- .cdsenv

    5- .cdsinit

    6- cds.lib

    7- cdsLibMgr.il

    Do you think I need to modify the up files?

    I do appreciate your help 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • NorNand
    NorNand over 5 years ago in reply to Andrew Beckett

    Thank you Andrew for your reply,

    This error I got is just after we reinstalled cadence in a new server, 

    I was not responsible for installing cadence but I copied the technology files from my old account to my account in the new server,

    besides that, I copied the following files as it is without any change

    1- .amsdlnit

    2- .amsenv

    3- .bashrc

    4- .cdsenv

    5- .cdsinit

    6- cds.lib

    7- cdsLibMgr.il

    Do you think I need to modify the up files?

    I do appreciate your help 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to NorNand

    I have no idea what triggered the problem, but my guess is that the model files passed to spectre are missing a file. It's unlikely to be the software itself. You're probably missing a file in the Setup->Model Libraries or Setup->Simulation Files in ADE which defines these parameters (and that's why they are undefined). Without being able to see the technology you're using, I can't say precisely what is wrong, because it will be specific to that technology. That's why I suggested contacting AMS, since it's their PDK. Maybe the documentation for the PDK would make it clear?

    Andrew.

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
  • NorNand
    NorNand over 5 years ago in reply to Andrew Beckett

    Thank you Andrew for your suggestions,

    I have contacted the PDK company, they fixed the issue for me, there was some missing files of the model which I then included. Now models are defined correctly and can run simulation using ADEL.

    My new problem arised when running the ADEXL or ADE GXL, for example, to run the Montecarlo from ADEXL , the enviroment is working perfectly so I can do my setting, the problem when I run the simulation it will not run, 

    The log file is not reporting an error not giving me any message, 

    is there any setting of ADEXL/ADE GXL that I might to investigate ?

    Thank you very much

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • NorNand
    NorNand over 5 years ago in reply to NorNand

    Dear Andrew,

    after waiting for a longer time I could receive these messages 

    I have seen similar problem and a reply from you like to solve it by 100

    First you might want to start by putting:

        adexl.icrpStartup  binaryName string "virtuoso -nocdsinit"

    into your ~/.cdsenv file. Alternatively in the CIW (before starting ADE XL), do:

        envSetVal("adexl.icrpStartup" "binaryName" 'string "virtuoso -nocdsinit")

    (you could also put this in your .cdsinit)

    I tried the above solution but still, nothing changed. 

    I also noticed one tab called "Job Monitor", from ADEXL Tools, when I click on it nothing is coming

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ShawnLogan
    ShawnLogan over 5 years ago in reply to NorNand

    Dear NorNand,

    NorNand said:

    I tried the above solution but still, nothing changed. 

    I also noticed one tab called "Job Monitor", from ADEXL Tools, when I click on it nothing is coming

    What are your job setup timeouts set to? The error suggests the failure was caused by the timeout period of 300 in your job setup file as I've highlighted in the log you provided.

    1. Is your job  timeout set to 300?

    2. Have you tried leaving it blank? Leaving it blank tells ADE-XL to wait indefinitely and not terminate the job or job submission.

    As an example of the timeouts in one's ADE-XL job policy, please see the attached configuration which I use for many Monte-carlo simulations.

    Shawn

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to ShawnLogan

    300 for the start timeout is normally enough unless you're submitting via a queueing system and it's full and so jobs don't start. 

    The thing I'd check first is whether you can run (in a terminal window) "virtuoso -nograph" . If that doesn't work, then you'll need to fix that first.

    Then try entering these, and then starting the job (do this before starting ADE XL - probably works during, but best to be sure):

    envSetVal("adexl.icrpStartup" "showJobStderr" 'boolean t)
    envSetVal("adexl.icrpStartup" "showJobStdout" 'boolean t)

    It will then print any errors or output in the CIW as the jobs are attempted to be started.

    If that doesn't help, contact customer support.

    Regards,

    Andrew

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
  • NorNand
    NorNand over 5 years ago in reply to Andrew Beckett

    Dear Andrew, 

    thank you for your answer

    I am now getting this message 

    Hope you could suggest me

    Thanks

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to NorNand

    I assume that the same error occurs if you type "virtuoso -nograph" in a terminal window?

    Can you show the contents of the vnc log file that it mentions in the message above? (I'm guessing any one of them will do - they probably all fail in the same way).

    Andrew.

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
  • NorNand
    NorNand over 5 years ago in reply to Andrew Beckett

    Dear Andrew,

    Thank you again for your reply 

    Yes, exactly I am getting the same warning message when I run in terminal " virtuoso no-graph".

    all the files fail in the same way as you mentioned,

    here is the content of one of the vnc files:

    /opt/cadence/IC616/tools.lnx86/bin/cdsXvncd: /opt/cadence/IC616/tools.lnx86/lib/vnclibs/libgcc_s.so.1: version `GCC_4.2.0' not found (required by /opt/cadence/IC616/tools.lnx86/lib/libstdc++.so.6)

    Thank you once again

    Regards

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to NorNand

    My guess is that you may be using an unsupported OS platform, as that's the only time I've seen reports of this error before.

    You might be able to solve it by doing (as the owner of the IC616 installation):

    mv /opt/cadence/IC616/tools.lnx86/lib/vnclibs /opt/cadence/IC616/tools.lnx86/lib/vnclibs_moved

    Regards,

    Andrew.

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
  • NorNand
    NorNand over 5 years ago in reply to Andrew Beckett

    Deae Andrew 

    Thank you very much for your answer,

    Your suggestions helped me a lot to figure out the problem.

    Now my problem is solved,

    I also found out that the font folder was missing the necessary font format ( dbi75, dbi 100 and dbi basic), so after copying these files the error was cleared

    Thank you once again

    Regards

    • 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