Troubleshoot Configure Physical Hierarchy

You can face following issues while configuring physical hierarchy:

• Schematic Properties Not Present in physConfig
• NLP Expressions Cannot be Converted to the New Schema
• Global or Inherited Nets Beyond Physical Leaf Cells are not Detected

Schematic Properties Not Present in physConfig

A schematic instance contained in a cell must have its master translated first in order for the properties to be converted correctly. The dfIIoa20222 translator attempts to ensure that this always happens, however, it is not guaranteed. If the properties for a particular schematic instance do not appear in the physical configuration view, Cadence recommends that you translate your data to OpenAccess 2.2 first and then perform the conversion to use the IC 6.1 Layout XL schema as a separate step.

NLP Expressions Cannot be Converted to the New Schema

The conversion commands cannot convert the following schematic properties if they are defined as an NLP expression on a cell.

• lxRemoveDevice
• lxRounding
• lxStopList
• lxUseCell
• lxViewList

When the system encounters this situation it issues the following message.

Cannot convert the 'oldPropName' property with value 'nlpExpr' on instance 'instName' in logical cellview 'libName/cellName/viewName' because NLP expressions are not supported. Use the Configure Physical Hierarchy window to specify explicitly the newOptionName either on a per cell or a per instance basis.

newOptionName is the name of the relevant field in the Configure Physical Hierarchy window’s Cells or Instances table or the name of the relevant option field in the Attributes pane. The mapping between oldPropName and newOptionName in the message is as follows.

oldPropName	newOptionName
lxRemoveDevice	Remove device option
lxRounding	Rounding option
lxStopList	Inherited Stop List
lxUseCell	Physical Cell
lxViewList	Inherited View List

Global or Inherited Nets Beyond Physical Leaf Cells are not Detected

In older releases, Configure Physical Hierarchy always elaborated the entire logical design hierarchy beyond the nodes which mapped to physical leaf cells. Now, the software stops the elaboration when it reaches a logical node that maps to a physical view with one of the view names specified in the Physical stop view list field.

This lets you use the physical stop view list to limit the logical elaboration for large hierarchical designs that would otherwise take a long time to open or might not open at all in Layout XL. However, it also means that global or inherited nets below the leaf instance in the schematic are not considered during the elaboration.

If your design relies on such nets, Cadence recommends that you switch off this environment and re-elaborate your design. To do this:

1. In the CIW, type
   

   envSetVal("layoutXL" "cphStopLogicalElabAtPhysLeaf" 'boolean nil)

2. Force a full re-elaboration by changing the Logical switch view list in the Global Bindings pane in the Configure Physical Hierarchy window.

Related Topics

Physical Hierarchy Configuration

Return to top