• 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. Custom IC Design
  3. connections to abstract not verified by Assura LVS - what...

Stats

  • Locked Locked
  • Replies 10
  • Subscribers 128
  • Views 5068
  • 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

connections to abstract not verified by Assura LVS - what's wrong?

TrevorB
TrevorB over 15 years ago

Hi,

We are using an IP block from our foundry in our chip.  The IP block is located below the top level of the hierarchy.  And, the IP block is presented as an empty layout block, containing only pins and boundary shapes.

Currently, as we run Assura LVS with the default options, our outside connections to the IP block's pins are not verified. We can swap connections - even leave connections open - but LVS does not complain!  That's no good...

What do I need to do differently to make Assura LVS verify our connections to the IP block's pins?

Thanks!

Trevor

  • Cancel
Parents
  • TrevorB
    TrevorB over 15 years ago

    Hi Quek,

    Thanks for your reply.  To answer your questions:

    1) I cannot find the IP block's cellName even mentioned in the design.erc file.

    2) The layout and schematic are both df2 - no GDS2.

    3) I found the following rules in my extract.rul file:

    ;; 
    ;; >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    ;; text layer
    ;;
    POLY1_pintext = textToPin( "PIN" type( "poly1"))
    MET1_pintext = textToPin( "PIN" type( "metal1"))
    MET2_pintext = textToPin( "PIN" type( "metal2"))
    MET3_pintext = textToPin( "PIN" type( "metal3"))
    MET4_pintext = textToPin( "PIN" type( "metal4"))
    PAD_pintext = textToPin( "PIN" type( "pad"))
    ;;
    ;; symbolic pins for macro LVS and RCX
    ;;
    POLY1_sympin = pinLayer( "POLY1" type( "pin"))
    MET1_sympin = pinLayer( "MET1" type( "pin"))
    MET2_sympin = pinLayer( "MET2" type( "pin"))
    MET3_sympin = pinLayer( "MET3" type( "pin"))
    MET4_sympin = pinLayer( "MET4" type( "pin"))

    ;;
    ;; >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    ;; pinPurpose layer (only drc)
    ;;
    POLY1_pinPurpose = layer( "POLY1" type( "pin"))
    MET1_pinPurpose = layer( "MET1" type( "pin"))
    MET2_pinPurpose = layer( "MET2" type( "pin"))
    MET3_pinPurpose = layer( "MET3" type( "pin"))
    MET4_pinPurpose = layer( "MET4" type( "pin"))
    PAD_pinPurpose = layer( "PAD" type( "pin"))

    Using this PDK, for general pin designation, we only have to label the drawing shapes using layer, "PIN", purpose, "<metal_layer>", as indicated above.  However, inside the IP block layout, the pin shape also exists as a df2 "terminal".  So, it should be covered both ways.

    4) The Assura version is:

    $ assura -W
    sub-version 3.2_USR2_HF11

    $ assura -V
    @(#)$CDS: assura version av3.2:Production:dfII5.1.41:5.10.41.500.6.130 06/29/2009 04:29 (logavt05) $

    5) I have read the section you described, plus the related one in the user's guide, and I have tried the following statements in my runs:

    Attempt #1: 

    blackBox("MY_IP_BLOCK_CELL_NAME")

    Attempt #2:

    blackBox("MY_IP_BLOCK_CELL_NAME" sch)
    blackBox("MY_IP_BLOCK_CELL_NAME" lay)

    Strangely, both runs complain about not being able to find the cell in the design hierarchy, although I clearly see the cellName being used in both designs. ... Incidentally, for testing purposes, I am running LVS at a lower level of the chip, in which the IP block exists as a top level cell.  I don't know if that makes a difference...

    Maybe the extract rules need some help, since neither I nor Assura can find the cell in Assura's schematic or layout netlist?

    Thanks!

    Trevor

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • TrevorB
    TrevorB over 15 years ago

    Hi Quek,

    Thanks for your reply.  To answer your questions:

    1) I cannot find the IP block's cellName even mentioned in the design.erc file.

    2) The layout and schematic are both df2 - no GDS2.

    3) I found the following rules in my extract.rul file:

    ;; 
    ;; >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    ;; text layer
    ;;
    POLY1_pintext = textToPin( "PIN" type( "poly1"))
    MET1_pintext = textToPin( "PIN" type( "metal1"))
    MET2_pintext = textToPin( "PIN" type( "metal2"))
    MET3_pintext = textToPin( "PIN" type( "metal3"))
    MET4_pintext = textToPin( "PIN" type( "metal4"))
    PAD_pintext = textToPin( "PIN" type( "pad"))
    ;;
    ;; symbolic pins for macro LVS and RCX
    ;;
    POLY1_sympin = pinLayer( "POLY1" type( "pin"))
    MET1_sympin = pinLayer( "MET1" type( "pin"))
    MET2_sympin = pinLayer( "MET2" type( "pin"))
    MET3_sympin = pinLayer( "MET3" type( "pin"))
    MET4_sympin = pinLayer( "MET4" type( "pin"))

    ;;
    ;; >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    ;; pinPurpose layer (only drc)
    ;;
    POLY1_pinPurpose = layer( "POLY1" type( "pin"))
    MET1_pinPurpose = layer( "MET1" type( "pin"))
    MET2_pinPurpose = layer( "MET2" type( "pin"))
    MET3_pinPurpose = layer( "MET3" type( "pin"))
    MET4_pinPurpose = layer( "MET4" type( "pin"))
    PAD_pinPurpose = layer( "PAD" type( "pin"))

    Using this PDK, for general pin designation, we only have to label the drawing shapes using layer, "PIN", purpose, "<metal_layer>", as indicated above.  However, inside the IP block layout, the pin shape also exists as a df2 "terminal".  So, it should be covered both ways.

    4) The Assura version is:

    $ assura -W
    sub-version 3.2_USR2_HF11

    $ assura -V
    @(#)$CDS: assura version av3.2:Production:dfII5.1.41:5.10.41.500.6.130 06/29/2009 04:29 (logavt05) $

    5) I have read the section you described, plus the related one in the user's guide, and I have tried the following statements in my runs:

    Attempt #1: 

    blackBox("MY_IP_BLOCK_CELL_NAME")

    Attempt #2:

    blackBox("MY_IP_BLOCK_CELL_NAME" sch)
    blackBox("MY_IP_BLOCK_CELL_NAME" lay)

    Strangely, both runs complain about not being able to find the cell in the design hierarchy, although I clearly see the cellName being used in both designs. ... Incidentally, for testing purposes, I am running LVS at a lower level of the chip, in which the IP block exists as a top level cell.  I don't know if that makes a difference...

    Maybe the extract rules need some help, since neither I nor Assura can find the cell in Assura's schematic or layout netlist?

    Thanks!

    Trevor

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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