• 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 add drain/source area & perimeter "ad as pd ps" of...

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 4986
  • 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 add drain/source area & perimeter "ad as pd ps" of MOSFET in creating Spectre netlist in Analog Design Environment?

Paulux
Paulux over 14 years ago

Hello,

 May I ask how to add drain/source area & perimeter "ad as pd ps" of MOSFET in creating Spectre netlist in Analog Design Environment? (i.e. e.g. x1 (d g s sub) nmos w=2u l=2u ad=5p as=5p pd=5u ps=5u). Since I only have one NMOS & PMOS instances with symbol, hspice & spectre views only and their CDF can only generate x1 (d g s sub) nmos w=2u l=2u. I can only find the parameters for calculating "ad as pd ps" from the design rule document and do not have any PDK file. Would you please help to show how to add these "ad as pd ps" in details or step-by-step?

If I post this message to wrong forum, could you please kindly help to move to proper forum and let me know?

Thank you very much for your help & kindness.

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 14 years ago

    You could have additional (non-readable, non-editable) parameters in the CDF which define the constants, and then refer to them with iPar(). They could be editable, but it would be a pain to have to keep editing them per-instance though.

    There are lots of ways you could handle this - but effectively people normally have a PDK to contain any technology specific mapping - even if it's a PDK you create yourself - rather than having a device which works for any foundry.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 14 years ago

    You could have additional (non-readable, non-editable) parameters in the CDF which define the constants, and then refer to them with iPar(). They could be editable, but it would be a pain to have to keep editing them per-instance though.

    There are lots of ways you could handle this - but effectively people normally have a PDK to contain any technology specific mapping - even if it's a PDK you create yourself - rather than having a device which works for any foundry.

    Andrew.

    • 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