• 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. Schematic and layout with multiple power pins

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 125
  • Views 19380
  • 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

Schematic and layout with multiple power pins

naveiitb
naveiitb over 10 years ago

Hi,

I am trying to design a chip which is going to have multiple power and gnd pins. These pins will be shorted in layout through the circuit, but I need to keep separate names for them in order to extract the layout and simulate the extracted netlist with the package parasitics. 

Is there a way to make the schematic aware of this? I cant possibly define multiple names (VDD1, VDD2,.. etc ) on the same power net. Also the layout extractor does not allow multiple names on the same net.

  • Cancel
Parents
  • ShawnLogan
    ShawnLogan over 10 years ago

    Dear Naveen,

    > However depending on the positions of there various gnd and vdd pads, and pins to which they are connected, the package parasitics will be different.

    I now understand your motivation. One possibility that I have used in similar situations is to define different nodes for each specific extracted view output pin (i.e., vdd_a, vdd_b, vdd_c...). Each node is connected to the global VDD plane through a metal resistor. Each resistor is a segment of the metal making up that particular segment leading to your VDD plane. For example, one metal resistor placed on the same level as your VDD plane extends to the corner pin, a second extends to a different corner. Schematically, your VDD connection is broken up into many different pins, but each pin will correspond to the specific node you want to connect the corresponding package model.

    I'm not knowledgeable enough to know of a different way to uniquely identify a particular layout location on an extracted view without defining a new pin for that location.

    Perhaps others have a better idea...

    Shawn

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • ShawnLogan
    ShawnLogan over 10 years ago

    Dear Naveen,

    > However depending on the positions of there various gnd and vdd pads, and pins to which they are connected, the package parasitics will be different.

    I now understand your motivation. One possibility that I have used in similar situations is to define different nodes for each specific extracted view output pin (i.e., vdd_a, vdd_b, vdd_c...). Each node is connected to the global VDD plane through a metal resistor. Each resistor is a segment of the metal making up that particular segment leading to your VDD plane. For example, one metal resistor placed on the same level as your VDD plane extends to the corner pin, a second extends to a different corner. Schematically, your VDD connection is broken up into many different pins, but each pin will correspond to the specific node you want to connect the corresponding package model.

    I'm not knowledgeable enough to know of a different way to uniquely identify a particular layout location on an extracted view without defining a new pin for that location.

    Perhaps others have a better idea...

    Shawn

    • 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