• 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. Hierarchical Top-Down CPF flow

Stats

  • Locked Locked
  • Replies 0
  • Subscribers 92
  • Views 13608
  • 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

Hierarchical Top-Down CPF flow

Schriek
Schriek over 7 years ago

Hi,

Using the hierarchical partitioning flow, I want to create an individual power domain for each partition, which can be turned off. 
I've been reading the Innovus user guide "Multiple Supply Voltage Top-Down Hierarchical Flow", but it is rather vague.

As specified I've used 'savePartition' to generate CPF files for each block and for the top-level design.
In the Block-Level CPF Generation chapter, the following is mentioned; "Creates the power domains referenced by the block-level CPF files", weird how it refers to block-level CPF while generating the block-level.

Secondly, in the Top-Level CPF Generation chapter, the following is mentioned "Defines each block-level boundary power domain information through create_power_domain -boundary_ports." generated from the chip-level CPF. However, the generated top-level do not contain these definitions.

Hence the question, how should the chip-level CPF be defined? Currently, I create power domains for each partition after 'definePartition' using read_power_intent/commit_power_intent followed by timing budgeting and partitioning. The block-level CPF generated for a partition contains only the default power-domain, which is not as expected since a different power-domain was specified for the partition (I.e. the partition does not have the right globalConnection)

Thanks.

  • Cancel

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