• 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 SKILL
  3. Cadence and Ams Netlist Generation in batch-mode

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 145
  • Views 17036
  • 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

Cadence and Ams Netlist Generation in batch-mode

yayla
yayla over 13 years ago
I am working functional model of a chip now and I need to generate ams netlist from Cadence and I include our own functional module for each component. Hence, I generating netlist from Top Level to Bottom Level using Cadence ADE OSS Netlister. We want to automatically generate all netlist from top level to bottom level using script like perl so we need generated ams netlist from xterm. Do you know how to generate ams netlist using terminal rather than usind ADE environment? . Also, could you provide me some documents that explaining how to run cadence in batch-mode?

 Or do you have any other suggestions to do this job?

Thanks,

 yayla

p.s. I have another post in functional verification part of forum. Could you also tell me how to delete that?
  • Cancel
  • yayla
    yayla over 13 years ago
    I am working functional model of a chip now and I need to generate ams netlist from Cadence and I include our own functional module for each component. Hence, I generating netlist from Top Level to Bottom Level using Cadence ADE OSS Netlister. We want to automatically generate all netlist from top level to bottom level so we need generated ams netlist from xterm. Do you know how to generate ams netlist using terminal rather than usind ADE environment? . Also, could you provide me some documents that explaining how to run cadence in batch-mode?

     Or do you have any other suggestions to do this job?

    Thanks,

     yayla
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • yayla
    yayla over 13 years ago

     I have searched before sending this post:

    To generate a netlist, http://www.cadence.com/Community/forums/p/17473/1245475.aspx which is createNetlist() in oceanscript. However, since I am using ams, I think I need to use config info addition to view name in "design(libname cellname viewname)". Otherwise, ams gives warning stating that I should use config. Also, in config I have specific view as stop lists that I have to use for netlisting and I don't have how to use that as stop list for netlisting. For ams netlisting, I am using OSS so probably I need to add some lines for that one also. Finally, I think I need to use amsdesigner() command for ams netlisting but I don't know how to combine all these information unfortunately.

    Hopefully, this helps to make my problem more clear. I will appreciate if you can help me.

     

    Thanks,

    yayla

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • tpylant
    tpylant over 13 years ago
    The command-line executable for the OSS-based netlister is called "runams".

    You can get more detailed responses by posting to the IC Design forum which covers AMS.

    Tim
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • yayla
    yayla over 13 years ago

     Thanks Tim. As you said, I have already opened a new thread in Custom Skill part.

    yayla

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • DevilScorpion
    DevilScorpion over 13 years ago

    Hi, Yayla,

       To be able to do that. You have to use icfb replay command. Steps to flow:

    1. Generate ams netlist once from ADE and save ocean script.

    2. Modify ocean script so that it could generate netlist:

         For example:

            simulator( 'ams )
            solver( 'APS )
            design(  "VFS_AMS_PHY180_sims" "aeq_ac_sim" "config_ams")
            ocnAmsSetOSSNetlister()
            createNetlist()
             .......

    3. Exit icfb. And restart icfb again and reload in this oceanscript.ocn

    4. Keep the CDS.log file.

    5. icfb -nograph -replay CDS.log

     

     

    The netlist could be generated without GUI.

     

    Thanks!

     

    PC 

       

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

    Yayla,

    There is also the UNIX "runams" command (type the command with no arguments, and it will tell you how to use it). This is available in IC5141 (probably in hotfixes from within the last  couple of years), and in IC614 and IC615 (it appeared in an IC613 hotfix too).

    I'll merge your other post in with this one (I see somebody suggested runams there too)

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • yayla
    yayla over 13 years ago

    Hi Andrew,

    Thanks for your response and cleaning up my second thread.  Do you know how to reach Cadence Unix shell (which is under Library manager) from general unix terminal since runams command only works at Cadence Unix shell? I have a Perl script cleaning Cadence netlist and including my functional module. If I can run Cadence AMS Netlist in batch mode, I can include that option into my Perl Script.

     thanks,

    yayla

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 13 years ago
    There's nothing special about that window - it's just an xterm launched from virtuoso - similar to system("xterm &") in the CIW. The only difference is that it will have the environment variables inherited from the virtuoso process.

    You should be able to run runams from a normal Unix terminal if the path is set up right. Maybe though in your environment you either have a wrapper around icfb/virtuoso which starts it, or a different command to start it. This wrapper might then be setting the path and other necessary env vars before launching icfb/virtuoso ?

    Regards,

    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