Troubleshoot Pin Issues
You can face the following issues while using the Pins step in the abstract generation process.
| ABS-12002 | |
|
Cell name: No terminals have been created. Use the Map text labels to pins option in the Map tab of the Pins step to define cell pins. See Text Labels-to-Pins Mapping. |
|
| ABS-12004 | |
|
Cell name: The abstract generator could not generate pins because the Map text labels to pins field did not contain valid values. You can proceed with the Extract step. However, to generate pins in the abstract view, specify valid values in the Map text labels to pins field and rerun the Pins step. See Text Labels-to-Pins Mapping. |
|
| ABS-12006 | |
|
Cell name: No pin will be created for the text label 'label' at (x,y) because no overlapping geometry exists for this text label. The abstract generator creates pins corresponding to geometries that overlap the text labels specified in the Map text labels to pins field on the Map tab. Therefore, while updating this field with pin mapping specification, ensure that geometries exist below the text labels specified. You can also check to ensure that the GDSII layout data has been imported into the abstract generator on correct layers. |
|
|
Abstract Generator creates pins corresponding to geometries that overlap the text labels specified in the Map text labels to pins field of the Pins step. This error message is generated when Abstract Generator does not find any shape overlapping the text label specified in the Map text labels to pins field. |
|
| ABS-12007 | |
|
Cell name: A pin has already been created on the net name, which conflicts with the label name at (x,y). Ensure that the Map text labels to pins field on the Map tab has been set correctly. You can also check to ensure that the GDSII layout data has been imported into the abstract generator on correct layers. |
|
|
A pin has already been created with the same name on the same layer. |
|
| ABS-12008 | |
|
Cell name: No value has been specified in the Map text labels to pins field on the Map tab for the bin name. Therefore, the default value defaultvalue will be used for mapping text labels to pins. |
|
|
Unless there are already terminals present, the Map text labels to pins specification is required to generate a valid pins view. If you do not specify this, Abstract Generator automatically determines a suitable default value before processing. |
|
| ABS-12009 | |
|
The Map text labels to pins field has been left blank and the abstract generator is unable to determine a default text pin mapping for the bin name because the cell layout does not contain text labels intersecting any geometry. The abstract generator tries to calculate a default value by examining the layers with text labels and then finding the metal layers that have shapes that intersect any of the text labels. If the abstract generator finds a shape under a text label on a metal layer, it sets the Map text labels to pins option to map those text labels to that metal layer. In the current situation, the abstract generator cannot find any metal shapes under the text labels. |
|
| ABS-12010 | |
|
Cell name: The prBoundary cannot be calculated even though the prBoundary creation has been enabled on the Boundary tab. This is because no layers have been specified in the Using geometry on layers field on the Boundary tab. Specify the appropriate layers for prBoundary creation. See Setting PR Boundary Creation Options in Standalone Abstract Generation. |
|
| ABS-12011 | |
|
Cell name: No prBoundary has been created even though the prBoundary creation has been enabled on the Boundary tab. This is because no geometry exists on the layers specified in the Using geometry on layers field on the Boundary tab. Specify the appropriate layers for prBoundary creation. See Setting PR Boundary Creation Options in Standalone Abstract Generation. |
|
| ABS-12012 | |
|
Cell name: Multiple prBoundaries have been created based on the value specified in the Using geometry on layers field on the Boundary tab. Update this value so that a single prBoundary is created. |
|
|
Correct the value in the Using geometry on layers field to enable Abstract Generator to create a single PR boundary. |
|
| ABS-12013 | |
|
Cell name: the calculation of the prBoundary failed even though the prBoundary creation has been enabled on the Boundary tab. Ensure that the layers on which the calculation is to be based are specified in the Using geometry on layers field on the Boundary tab. The specified layers should lead to the creation of a single prBoundary. Additionally, ensure that geometry exists on the specified layers. See Setting PR Boundary Creation Options in Standalone Abstract Generation. See also |
|
| ABS-12015 | |
|
Cell name: the prBoundary does not enclose all cellview geometries. This is because not all layers with geometry for calculating prBoundary have been specified in the Using geometry on layers field on the Boundary tab. Ensure that all the required layers have been specified in this field. See Setting PR Boundary Creation Options in Standalone Abstract Generation. |
|
| ABS-12016 | |
|
The Create boundary option on the Boundary tab has been set to off, but no prBoundary exists in cell. Set the Create boundary option to either 'always' or 'as needed'. |
|
|
The Create boundary option should be set to off only if a prBoundary already exists in a cell. This message is displayed if no boundary exists and there is no request to create one. |
|
|
For information about creating place-and-route boundaries and specifying the layers to be used in the necessary calculations, see Boundary Tab. |
|
| ABS-12019 | |
|
Cell name: database could not create pin named pin name. Verify the permissions on the design and ensure that write permission exists. |
|
|
The database is unable to create a pin with the specified name. This is because the write permissions on the design does not exist. |
|
| ABS-12020 | |
|
Cell name: database could not create net named net name. Verify the permissions on the design and ensure that write permission exists. |
|
|
The database is unable to create a net with the specified name. This is because the write permissions on the design does not exist. |
|
| ABS-12022 | |
|
Cell name: the existing terminal terminalname was ignored based on the Exclude existing terminals field on the Map tab. However, no equivalent terminal was created based on the option specified in the Map text labels to pins field. |
|
|
This warning is issued when the terminals specified in the Exclude existing terminals field on the Map tab are not created back from the equivalent text labels existing in the layout. |
|
| ABS-12023 | |
|
Cell name: the pin name has shape on an invalid user layer numbered number in the technology file. The pin will be deleted from the layout. |
|
|
This warning is issued during the Pins step when Abstract Generator comes across a pin that exists on an invalid technology layer. Abstract Generator deletes such pins from the layout after issuing this warning. |
|
| ABS-12024 | |
|
Cell name: no pin shape will be created on the layer name because the layer does not have pin purpose defined in the technology file. |
|
|
This error message is issued when Abstract Generator attempts to add pin shapes on a layer that does not have a purpose defined in the technology file. Abstract Generator might attempt to create pins in the following ways:
|
|
|
|
| ABS-12025 | |
|
Cell name: Terminals name and name are must join terminals but have been mapped to different terminal types. terminalname has been specified as type terminal and terminalname has been specified as type terminal. Check the regular expressions specified on the Map tab. |
|
| ABS-12027 | |
|
Cell name: the existing terminal name specified in the Exclude existing pins on layers field does not have any pin shape. This terminal will be deleted. The equivalent terminal will be created based on the value specified in the Map text labels to pins field on the Map tab. |
|
|
This warning message is issued when a terminal on the layer specified in the Exclude existing pins on layers field does not have a pin. |
|
Related Topics
Specifying Pin Mappings for Abstract Generation
Return to top