Function name: Cannot find viaDef viaDef1.

Problem: viaDef is not found in the technology database.

Solution: Make sure the name of the viaDef corresponds to an existing via or viaDef.

Function name: Cannot open cdsVia lib/cell/view.

Problem: The tool tried to open the cellview that corresponds to the cdsVia, but failed.

Solution: Make sure the cdsVia cellview is properly created.

Function name: Could not create viaspec.

Problem: Could not create a viaSpec for the prViaRule.

Solution: Check the minimum width (wMin) and maximum width (wMax) parameters for the layers to see if they are in the correct format.

Function name: direction direction1 is not stored on layer layer1 in the database; preferred direction direction2 is used.

Problem: The direction specified in prViaRule and prGenViaRule is compared with the direction stored in the technology database. When they differ, this warning is issued.

Solution: Verify whether there is a conflicting definition for direction in the technology file or technology database.

Function name: Failed to get the viaParams from the prGenViaRule parameters.

Problem: Could not get the stdViaDef parameters from the prViaRule values.

Solution: Check the parameters for prViaRule to see if they are in the correct format.

Function name: Failed to update the parameters of viaDef viaDef1.

Problem: When the function tried to update the existing viaDef parameters with the prViaRule values, the operation failed.

Solution: Check the parameters for the prViaRule to see if they are in the correct format.

Function name: Failed to update the parameters of viaDef viaSpec1.

Problem: When the function tried to update the existing viaSpec parameters with the prViaRule or prGenViaRule values, the operation failed.

Solution: Check the parameters for the prViaRule to see if they are in the correct format.

Function name: Invalid spacing type for layer.

Problem: The data type for the spacing of the routing layer in the prNonDefaultRule must be floating point.

Solution: Check the data type for the spacing of the routing layer.

Function name: Invalid stackViaParams for isStackable.

Problem: The data type for the stackable value of the via layers in the prNonDefaultRule must be Boolean.

Solution: Check the data type for the stackable value of the via layers and make sure it is Boolean.

Function name: Invalid via name via1.

Problem: The specified viaDef name does not represent a valid prVia.

Solution: Check the name of the viaDef and make sure it is a valid prVia.

Function name: Invalid width type for layer.

Problem: The data type for the width of the routing layer in the prNonDefaultRule must be floating point.

Solution: Check the data type for the width of the routing layer.

Function name: Layer layer1 is not a valid routing layer.

Problem: A valid prRouting layer is a physical layer that has a mask number and a function that is not of the type “other” (unknown).

Solution: Make sure that the layer has all required attributes set.

Function name: Not a valid Enclosure or Direction value.

Problem: The data type for the layer direction or overHang is not correct.

Solution: Check the format of the layer direction and overHang.

Function name: Not a valid lowerPt value.

Problem: The lowerPt is not valid because it has either an incorrect data type or an incorrect length.

Solution: Check the format of the lowerPt in the prGenViaRule.

Function name: Not a valid xPitch and yPitch value.

Problem: The xPitch or yPitch does not have a valid data type.

Solution: Check the data type for the xPitch and yPitch parameters in the prGenViaRule.

Function name: metalOverHang and overHang are not stored in the database.

Problem: The rule names metalOverHang and overHang are derived from layer enclosure and direction. OpenAccess does not provide direct attributes.

Solution: No action required.

Function name: The stackable via value of value1 and value2 is not compatible with the existing value.

Problem: The value for spacing or the stackable via in the prNonDefaultRule is different than the value in the physicalRules section or the value in the prStackVias section.

Solution: Check the stackable and minSpacing values defined for the spacingRules in the physicalRules and prStackVias sections. Make sure the values are the same as in the prNonDefaultRule section.

Function name: viaDef creation for ruleContact device only supports two adjacent routing layers.

Problem: ruleContact device defines more than two layers and more than one via layer. Only layer0, layer1, and the via10 layer are used to create a viaDef.

Solution: No action required.

Function name: viaDef viaDef1 is not a valid prVia.

Problem: A valid prVia is defined as:

• Contained in the technology library.
• Has a cell name and view name that correspond to a valid cellview.
• At least one of the layers in the cellview is a valid routing layer, which implies that the LEFDefaultRouteSpec exists. The other layer could be either a valid routing layer or a valid masterslice layer.

Solution: Verify whether the viaDef corresponds to a via that satisfies the conditions above.

Convert prRules: No device found in the technology database.

Problem: There is no device (via) found in the technology database. Conversion of prRules to routeSpec is likely to fail because cut layers are usually found in vias.

Solution: Your technology file or technology database might be incomplete. Update the file or database to include via definitions or define cut layers.

Convert prRules: No routing layer found in the technology database.

Problem: prRules are defined in the technology database, but routing layers are not specified.

Solution: Routing layers are required for prRule conversion. You need to add the routing layers to the prRoutingLayer rule.

Convert prRules: No valid cut layer found between routing layer layer1 and layer2.

Problem: There must be a cut (via) layer between two routing layers. The tool could not find a cut layer from either the existing devices or the viaLayer rule.

Solution: Verify whether the routing layers are properly defined and whether a via exists that contains both routing layers. Or, you can create a viaLayer rule for the two routing layers.

Convert prRules: prRule layer mask numbers must be fully specified.

Problem: In the technology database, some layers have mask numbers assigned, while other layers do not. For layers with no mask number, the tool could not automatically assign a mask number.

Solution: Assign mask numbers for all routing layers, masterslice layers, and cut layers.

Not valid via layer pair.

Problem: Could not find the stackable via layers specified by the prNonDefaultRule.

Solution: Check the stackable via layers specified in the prNonDefaultRule.