• 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. core size.

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 91
  • Views 14016
  • 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

core size.

gops
gops over 16 years ago
what is the criteria for selecting core utilization?? When i import a design into encounter , a core area comes by itself with a default core utilization.?On what basis the tool does this? How could i get an optimized value for my CORE AREA, CORE UTILIZATION?
  • Cancel
Parents
  • Kari
    Kari over 16 years ago

     It really depends on the technology, library, number of routing layers, etc. It can also depend on the timing and how much timing margin you want. For example, if you want to fix hold timing with 100ps extra margin, you will need more room for buffers. I typically start a block at about 65%. Sometimes we find we need a lower util, sometimes we find we can squeeze it tighter. It can also depend on how much of your design is std cells and how much is RAM or other IP.

     - Kari

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

     It really depends on the technology, library, number of routing layers, etc. It can also depend on the timing and how much timing margin you want. For example, if you want to fix hold timing with 100ps extra margin, you will need more room for buffers. I typically start a block at about 65%. Sometimes we find we need a lower util, sometimes we find we can squeeze it tighter. It can also depend on how much of your design is std cells and how much is RAM or other IP.

     - 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