Stats

  • Locked Locked
  • Replies 2
  • Subscribers 92
  • Views 13415
  • 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

id problem cells with verifyGeometry

gundicad
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???

  • 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
     

  • 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.

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.