• 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. Die Size Estimation

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 90
  • Views 16365
  • 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

Die Size Estimation

archive
archive over 17 years ago

What are the criterias to follow while estimatin DIE size? Did there any standard procedure for DIE size calculation. Best Regards Sandeep


Originally posted in cdnusers.org by sandeepv
  • Cancel
Parents
  • archive
    archive over 17 years ago

    Hi Sandeep,

    Sanjay's advice for die size sounds good to me. Most of the designs I have worked on were I/O-limited, so the die size was already defined by that. But when working on hierarchical blocks, depending on the technology and number of metal layers, we usually try to start the designs around 55 or 60% std cell util. The goal is to not exceed about 75% when the design is complete (clock trees added, design optimized, hold buffers added, etc.) Sometimes you can go higher, depending on pin density, complexity of the design, etc (which all relate to routing congestion). We just start with these numbers, then adjust up or down after some experimenting. This is where the quickness of trialroute and extractRc come in very handy! If something looks promising, we go on to nanoroute and QRC just to be sure things will still look ok.

    As for power stripe widths, these are usually back-of-the-envelope calculations. If you have a wirebond design, you can probably work up a spreadsheet that has the total expected power of the design, the widths and spacings of the stripes, voltage, design size, resistivity of the layers, and calculate a voltage drop. Then keep adjusting the width and spacing numbers until you get an acceptable drop, and start with that. Maybe add a fudge factor somewhere just to err on the conservative side. For flip chips, the calculations are not so easy, but you need much less striping in a flip-chip anyway since power comes down from bumps all over the core. So pick something to start with and do an IR analysis as early as possible.

    Hope that helps,

    - Kari

    - Kari


    Originally posted in cdnusers.org by Kari
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 17 years ago

    Hi Sandeep,

    Sanjay's advice for die size sounds good to me. Most of the designs I have worked on were I/O-limited, so the die size was already defined by that. But when working on hierarchical blocks, depending on the technology and number of metal layers, we usually try to start the designs around 55 or 60% std cell util. The goal is to not exceed about 75% when the design is complete (clock trees added, design optimized, hold buffers added, etc.) Sometimes you can go higher, depending on pin density, complexity of the design, etc (which all relate to routing congestion). We just start with these numbers, then adjust up or down after some experimenting. This is where the quickness of trialroute and extractRc come in very handy! If something looks promising, we go on to nanoroute and QRC just to be sure things will still look ok.

    As for power stripe widths, these are usually back-of-the-envelope calculations. If you have a wirebond design, you can probably work up a spreadsheet that has the total expected power of the design, the widths and spacings of the stripes, voltage, design size, resistivity of the layers, and calculate a voltage drop. Then keep adjusting the width and spacing numbers until you get an acceptable drop, and start with that. Maybe add a fudge factor somewhere just to err on the conservative side. For flip chips, the calculations are not so easy, but you need much less striping in a flip-chip anyway since power comes down from bumps all over the core. So pick something to start with and do an IR analysis as early as possible.

    Hope that helps,

    - Kari

    - Kari


    Originally posted in cdnusers.org by 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