• 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 very much Quek. Actually, once the cell is copied, it's just as easy to delete the two pins from the spectre view, though I have used the netSet property before in other situations.

    The reason that a three-terminal symbol is useful is that models for discrete DMOS devices generally are three-terminal. Having a three-terminal symbol available in a standard spectre library allows the user simply to instantiate the three-terminal symbol and populate the model field with the name of the model provided by the DMOS manufacturer. (It is assumed that the models library has already been added to the user's model path.)   

     I'd like to request that a three terminal symbol be added to analogLib if possible. Cadence could call it "nmos3" to fit with the "nmos" and "nmos4" devices already there. I think it would get used, maybe more than the other two cells because most companies use their own libraries or use libraries from fab PDKs for design, either of which includes symbols compatible with bsim models.  On the other hand, it's easy to create a copy, so not really that important.

    Thanks again Quek.

    Jack

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

    Thanks very much Quek. Actually, once the cell is copied, it's just as easy to delete the two pins from the spectre view, though I have used the netSet property before in other situations.

    The reason that a three-terminal symbol is useful is that models for discrete DMOS devices generally are three-terminal. Having a three-terminal symbol available in a standard spectre library allows the user simply to instantiate the three-terminal symbol and populate the model field with the name of the model provided by the DMOS manufacturer. (It is assumed that the models library has already been added to the user's model path.)   

     I'd like to request that a three terminal symbol be added to analogLib if possible. Cadence could call it "nmos3" to fit with the "nmos" and "nmos4" devices already there. I think it would get used, maybe more than the other two cells because most companies use their own libraries or use libraries from fab PDKs for design, either of which includes symbols compatible with bsim models.  On the other hand, it's easy to create a copy, so not really that important.

    Thanks again Quek.

    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