• 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. How to set default simulator and simulation library in IC5141...

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 126
  • Views 17796
  • 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

How to set default simulator and simulation library in IC5141?

enzochi
enzochi over 14 years ago

How to setup the default simulator and simulation libraryin IC5141? That I don't have to setup it any time when I create a new test bench for my new cells?

 

Thanks

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 14 years ago

    The default simulator in the Analog Design Environment (if that's what you're talking about) is set via a .cdsenv setting:

     asimenv.startup simulator       string  "spectre"

    or in your .cdsinit :

     envSetVal("asimenv.startup" "simulator" 'string  "spectre")

    I don't know what you mean by setting the default simulation library though. You'll need to expand upon what you're trying to achieve here.

    Regards,

    Andrew.  

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • enzochi
    enzochi over 14 years ago
    Hi Andrew: The simulation setup is what I need. thanks. It is the first time I use this tool. What I mean the library setup is: when I open Virtuoso Analog Design Environment, at the Setup -> Model Libraries. Where I can locate my library files. I just want it to be set as the simulator I used, without do it every time when I build a new testbench. Thanks.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 14 years ago

    This is done with the:

     spectre.envOpts modelFiles      string  ""

    cdsenv setting. Or you can use the envSetVal() SKILL equivalent (you can guess the syntax from my previous post).

    The string itself would be in this form:  "/path/file1.scs /path/file2.scs /path/file3.scs;section3"

    See http://support.cadence.com/wps/mypoc/cos?uri=deeplinkmin:ViewSolution;solutionNumber=1839602  and http://support.cadence.com/wps/mypoc/cos?uri=deeplinkmin:ViewSolution;solutionNumber=11210060 for more details.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Manatee
    Manatee over 12 years ago

    I added the line

     asimenv.startup simulator       string  "spectre"

    to my .cdsenv, then launched icfb but when I open ADE the default simulator is still eldoD. 

    If I check from CIW

      envGetDefVal("asimenv.startup" "simulator")

    it says "spectre"

    but 

     envGetVal("asimenv.startup" "simulator")

    says "eldoD"

     

    What can I do without entering in the CIW envSetVal("asimenv.startup" "simulator" 'string "spectre")?

     I wouldn't change my .cdsinit because I have read-only privileges on that file 

        

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    The problem is that the .cdsenv (e.g. from your home dir) gets read before the .cdsinit - and most likely the Mentor customization loaded from your .cdsinit is changing the default simulator to eldoD. So you probably need to be able to modify the .cdsinit (maybe the readonly .cdsinit has SKILL code in it to load a user file instead?).

    You could revert to "icfb -nocdsinit -restore myInit" and then have myInit contain:

    load(".cdsinit") ; get the path right
    envSetVal("asimenv.startup" "simulator" 'string "spectre")

    and then create yourself an alias or wrapper script to avoid having to type the long icfb.

    Andrew.

    • 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