3

---

Setup for Automatic Extraction of Power Intent

---

To run in-design checks or to extract the power intent from a design, you need to provide inputs that are required by the tool for correct identification of design topology and define key set of rules. For example, you can define a setup that identifies all the power nets in your design, creates power domains, creates supply states, or redefines the severity of certain checks.

The Power Manager setup can be classified as:

• Common setup: This type of setup information is common to a set of designs. It includes technology, environment, data integrity checks, and so on. This setup information is stored in a CSF-searchable location and is applied when no design-specific information is found.
• Project-specific setup: This information consists of the project-specific setup and design- specific details. It includes all types of settings and it is automatically applied if available for a design. You can register and specify values in the Power Manager Setup form and save them in the setup file for a project to ensure that each command is implemented according to the project setup.

A setup file can be placed at one of the following three locations:

• Device-level information inside PDK Library in lpLibSetup.il
• Project-level common settings at the CAD level inside .cadence/dfII/vpm or some other CSF-compatible path in lpSetup.il
• User-defined settings that are defined in Power Manager Setup form through registration and saved in a setup template file

There are two options in the setup template to control the enabling of the project-level (CAD) settings in the final merged setup loaded for Power Manager.

• loadEnvironmentOptions:
  Controls whether the.cadence/dfII/vpm/lpSetup.il file is loaded automatically as a part of the final merged setup.
  • If set to true, the project-level settings are considered as a part of the final setup.
  • If set to nil, the project level settings are ignored for the final setup.
  • If this option is not specified in the Power Manager setup template, it is assumed to be true and is considered for the final setup.
• pushUnmodifiedEnvOptions:
  Controls the reading of the project-level (CAD) settings, at a later stage. For example, if there is any update in the project-level settings and the changes need to be applied in the final merged setup for the Power Manager.
  • If set to true, any changes done in the project-level settings are read and updated.
  • If set to nil, any changes done in the project-level settings are ignored in the final setup.

You can define these options in the setup if you want to read the project-level setup initially or always want to ensure that the user-defined setup is synchronized with the project-level (CAD) setup.

The final setup is the result of merging all the three setups, which can be verified by exporting in the file:

vpmExportPowerIntentSetup("random_computation_flat" "random_computation_top" "schematic" "lpSetup_export.il" ?filter "allSetupOptions" ?overwriteExisting t)

Currently, if there are common settings in the setup file, for example, supply nets are specified in CAD and user-defined setup, the user-defined setup has a higher precedence.

Related Topics

Registering Name-Based Supply Nets

Registering Regular Expressions-Based Supply Nets

Registering Libraries

Registering Device and Cell

Performing In-Design Checks

Registering Supply Set and Power Domain

Miscellaneous Settings

Setup File Template

Loading Power Intent Extraction Options from a File

Saving Power Intent Extraction Options to a File