• 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. Digital Implementation
  3. power stripes

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 94
  • Views 18532
  • 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

power stripes

gops
gops over 16 years ago
Somebody please tell me about , how to choose power stripe width, their spacing and also what all metals can i use for creating a power stripe.
  • Cancel
Parents
  • Kari
    Kari over 16 years ago

     Hi Gops,

     The width, spacing, and layer of your power stripes really depends on your design. You want enough power routing so that you don't have too big an IR-drop, but not so much that there's no room left for signal routing. You'll need more striping for a wire-bond design than you will for flip-chip. It can depend on how dense your design is, the frequency, how many total metal layers, etc. 

     Here are a few basic guidelines though: your std cell rails will mostly likely be on metal1, but we do see std cell libraries that have rails on metal2. These rails are often referred to as followpins. So that layer is pretty much decided for you, based on your library. You probably don't want to use the next layer (2 or 3) for stripes, because you would likely be blocking routing access to your std cell pins. We typically start stripes on metal4 and have stripes on every layer from 4 up. We have found that thinner, more frequent stripes are better than thicker, less frequent stripes for routability. If your design is easy to route, a typical strategy is to have thick, frequent stripes on the top 2 layers, so that almost all of the top 2 layers is pwr/gnd. But not all designs can afford that. As for width and spacing, you want to pick numbers that are divisible by the routing pitch, so that your stripes are centered on routing tracks and do not "waste" the tracks on either side by being off-center. 

    The best thing is to do an IR-drop analysis as early as possible to make sure you have enough power (don't forget to analyze VSS as well as VDD).

    - Kari

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Kari
    Kari over 16 years ago

     Hi Gops,

     The width, spacing, and layer of your power stripes really depends on your design. You want enough power routing so that you don't have too big an IR-drop, but not so much that there's no room left for signal routing. You'll need more striping for a wire-bond design than you will for flip-chip. It can depend on how dense your design is, the frequency, how many total metal layers, etc. 

     Here are a few basic guidelines though: your std cell rails will mostly likely be on metal1, but we do see std cell libraries that have rails on metal2. These rails are often referred to as followpins. So that layer is pretty much decided for you, based on your library. You probably don't want to use the next layer (2 or 3) for stripes, because you would likely be blocking routing access to your std cell pins. We typically start stripes on metal4 and have stripes on every layer from 4 up. We have found that thinner, more frequent stripes are better than thicker, less frequent stripes for routability. If your design is easy to route, a typical strategy is to have thick, frequent stripes on the top 2 layers, so that almost all of the top 2 layers is pwr/gnd. But not all designs can afford that. As for width and spacing, you want to pick numbers that are divisible by the routing pitch, so that your stripes are centered on routing tracks and do not "waste" the tracks on either side by being off-center. 

    The best thing is to do an IR-drop analysis as early as possible to make sure you have enough power (don't forget to analyze VSS as well as VDD).

    - Kari

    • 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