Home > Community > Forums > Digital Implementation > id problem cells with verifyGeometry

Email

* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

 id problem cells with verifyGeometry 

Last post Thu, Sep 5 2013 5:12 AM by gundicad. 2 replies.
Started by gundicad 29 Aug 2013 10:36 AM. Topic has 2 replies and 449 views
Page 1 of 1 (3 items)
Sort Posts:
  • Thu, Aug 29 2013 10:36 AM

    • gundicad
    • Not Ranked
    • Joined on Thu, Aug 22 2013
    • Colorado Springs, CO
    • Posts 2
    • Points 25
    id problem cells with verifyGeometry Reply
    Hi I am looking for a way to id std cells that create  drcs. You may have a few cells in the library that exhibit bad behavior  they may contain a blockage that creates spacing violations to metal two power stripes for instance...would be nice to be able to use violation markers to ID these cells and form a list of these problem cells....does anyone in the community think that this would be nice to have and share? Is there any Tcl that does it? selectCell by specified drc violation type of function???
    • Post Points: 20
  • Wed, Sep 4 2013 7:56 AM

    • fitz
    • Top 150 Contributor
    • Joined on Wed, Aug 4 2010
    • Kanata, Ontario
    • Posts 56
    • Points 745
    Re: id problem cells with verifyGeometry Reply

    Good idea, in the most simplistic terms  you want the violation browser to report based on cell type rather than instance name.
    But researching remaining nanoRoute violations will only tell you when your library is problematic not when it is sub-optimal.

    For example,
    One of your cells has an output pin that is only accessible from the north direction in M1 stub and a single cut via.
    If nanoRoute completes cleanly ( and by default it will try very hard for a very long time to succeed ) you would never know there is an sub-optimal cell.
    Optimal standard cell libraries will only help routability  which can dramatically improve  run times for routeDesign and optDesign -postRoute -SI.

    I cannot think of a simple testcase that would check,  all pins, in all cell orientations, from all directions, for multi cut vias and M1 stub access.
    You could possibly use your current layout and back off the repair effort level and sort through the lower metal level errors.
    Your best bet maybe to write a custom DRC rule deck to check standard cell optimization .

    Most of the online documentation I have found has to to with routing rules & guidelines.
    Has anyone found any Cadence documentation / software for optimal standard cell library layout?

    Shawn
     

    • Post Points: 20
  • Thu, Sep 5 2013 5:12 AM

    • gundicad
    • Not Ranked
    • Joined on Thu, Aug 22 2013
    • Colorado Springs, CO
    • Posts 2
    • Points 25
    Re: id problem cells with verifyGeometry Reply
    The solution I used was to parse the verifyGeometry drc file which actually lists the cell instances. From that you can derive the master cell list....Seems like it would be an easy feature to add since the tool lists the instances.
    • Post Points: 5
Page 1 of 1 (3 items)
Sort Posts:
Started by gundicad at 29 Aug 2013 10:36 AM. Topic has 2 replies.