Stats

  • Locked Locked
  • Replies 1
  • Subscribers 142
  • Views 12811
  • 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

tracking down markers from cell verifier for all cells in a design

knuhcrek

Greetings all,

I'm an old hand at SKILL but all my experience has all been on the PCB side (Concept/Allegro) - this IC stuff has got me a bit bewildered.

Manually running Cell verifier against a particular cell ( or more precisely the layout view of a cell)  reports some shorts and some violations of weak connections and flags these with markers in the display. 

Question: assuming I can build up a list of library objects and within those lists of cells and within those lists of views, how should I go about building up a list of markers? The overall goal here is to collect a list of all markers in a design . Do markers have their own objType? How are they tied to what they mark? In the Allegro world designs have DRCs and a DRC is its own instance of objType 'drc' and has a property that ties it to the dbids of the offending objects.

Any suggestions/hints/pointers/constructive criticisms and especially examples are all welcome.

TIA,

Chris Walters

(back from the netherregions)

Parents

  • Hi Chris,

    If you are using IC61x or ICADV12x then you can use the Annotation Browser to help you view, visit and clear the markers, and in the database markers are their own type of object which are attached or reference the objects they mark.  If you get the cellview id (e.g. cv = geGetEditCellView()) then you should be able to see them in SKILL using something like cv~>markers. Unless you really need to write your own code, I would look first at what the Annotation Browser provides for viewing markers; they can be grouped into types on separate tabs, e.g. DRC markers on one, Constraint issues in another and so on.  There are controls for visibility for particular markers which can be controlled individually or by sub group (e.g. say you have 10 errors of type "abc" you can visit them individually, or turn on/off the entire set). You can modify the color of markers in the same way.

    Hopefully this is enough to help you get started?

    Regards,

    Lawrence.

Reply

  • Hi Chris,

    If you are using IC61x or ICADV12x then you can use the Annotation Browser to help you view, visit and clear the markers, and in the database markers are their own type of object which are attached or reference the objects they mark.  If you get the cellview id (e.g. cv = geGetEditCellView()) then you should be able to see them in SKILL using something like cv~>markers. Unless you really need to write your own code, I would look first at what the Annotation Browser provides for viewing markers; they can be grouped into types on separate tabs, e.g. DRC markers on one, Constraint issues in another and so on.  There are controls for visibility for particular markers which can be controlled individually or by sub group (e.g. say you have 10 errors of type "abc" you can visit them individually, or turn on/off the entire set). You can modify the color of markers in the same way.

    Hopefully this is enough to help you get started?

    Regards,

    Lawrence.

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.