• 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. cds_generic nmos extracting as 4-terminal

Stats

  • Locked Locked
  • Replies 9
  • Subscribers 126
  • Views 18875
  • 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

cds_generic nmos extracting as 4-terminal

jmoriarty
jmoriarty over 12 years ago

Using IC6.1.5-64b.500.9.  

Instantiating "nmos" (not "nmos4") symbol view from "cds_generic" library in which the model field is populated with "mod".  It extracts as  follows:

M6 (0 0 0 0) mod

The symbol view has only 3 terminals, and there are only 3 terminals in the pin list. There appears to be an error in the "spectre" view, which shows 4 terminals.  Only fix is to copy "symbol" and "spectre" views to an editable library and delete a terminal from the "spectre" view.  If this is indeed an error, can it be corrected in the next release?  If there is already an open ticket I appologize for not finding it.

 Thanks.

  • Cancel
Parents
  • jmoriarty
    jmoriarty over 12 years ago

    Thanks much Andrew.  The three-terminal models are provided by _discrete_ power DMOS manufacturers.  For example, IR, Vishay Siliconix, and Fairchild all provide three-terminal models, and I would guess that most of the rest do as well.  Of course, the models were intended for use by PCB-level designers who wouldn't be Virtuoso customers, but it is common for _IC_ designers to perform simulations using the external models to better predict how a power controller IC design will perform with actual, commercially available transistors.  Again, not a big deal to copy the analogLib component and edit it, but it just seemed like an opportunity to use the standard library transistor symbols provided by Cadence, for which I have never, ever had a need before.  As I mentioned, most IC designers work from other libraries so I'm guessing that the "nmos" and "nmos4" cells are used by a very small segment of your customer base.  If you provided a three-terminal cell, it might get some use from your power conversion customers, along with any other users whose ICs work with discrete transistors.  Those combined comprise a small, but not insignificant segment of the IC tool market.

     Thanks again Andrew.  Your posts serve as an educational resource to us all.

     Jack

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • jmoriarty
    jmoriarty over 12 years ago

    Thanks much Andrew.  The three-terminal models are provided by _discrete_ power DMOS manufacturers.  For example, IR, Vishay Siliconix, and Fairchild all provide three-terminal models, and I would guess that most of the rest do as well.  Of course, the models were intended for use by PCB-level designers who wouldn't be Virtuoso customers, but it is common for _IC_ designers to perform simulations using the external models to better predict how a power controller IC design will perform with actual, commercially available transistors.  Again, not a big deal to copy the analogLib component and edit it, but it just seemed like an opportunity to use the standard library transistor symbols provided by Cadence, for which I have never, ever had a need before.  As I mentioned, most IC designers work from other libraries so I'm guessing that the "nmos" and "nmos4" cells are used by a very small segment of your customer base.  If you provided a three-terminal cell, it might get some use from your power conversion customers, along with any other users whose ICs work with discrete transistors.  Those combined comprise a small, but not insignificant segment of the IC tool market.

     Thanks again Andrew.  Your posts serve as an educational resource to us all.

     Jack

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information