Errors exist in rules file...

Discussion in 'Cadence' started by Michael Förtsch, Jan 26, 2005.

  1. Hello,

    usually I try to solve Cadence problems with groups.google.com or with
    sourcelink.cadence.com, but I haven't found anything about this:

    Cadence 5.0.32.57 is running on a Ultra-250 with Solaris 5.8. We are use
    a design kit from XFAB. If I start a DRC I get the following message:

    error: Drc allows only one input layer for 'width' check.
    2050. drc(geomGetEdge(hv_ng0 butting ndiff) geomGetEdge(hv_ng0
    butting nwtrms) (width < 4.0) " W6P1 : Minimum GATE length = 4.0 ")
    Errors exist in the rules file ".../TECH_XB06/divaDRC.rul".

    If I manually delete the "geomGetEdge(hv_ng0 butting nwtrms)" part of
    rules file, the DRC runs without an error message. At first, this looks
    like a design kit problem rather than a Cadence problem. But exactly the
    same rules file works without problems together with an older Cadence
    version (Cadence 4.4.6.100.66m on Solaris 5.7)

    If I try to generate the extracted view from a layout I get the
    following message:

    *WARNING* Errors exist in rules file so this program cannot continue.

    There is no hint what errors exist. Since the divaDRC.rul has exactly
    the same content then divaEXT.rul, I also deleted "geomGetEdge(hv_ng0
    butting nwtrms)", but this has no effect.

    Is there solution or a workaround for this problem?

    Best regards,
    Michael.
     
    Michael Förtsch, Jan 26, 2005
    #1
  2. Michael Förtsch

    Marc Heise Guest

    Hi Michael,

    in 4.4.6. you did not get the error message because the second geomGetEdge was
    just ignored without a complain from the software. This changed with newer
    releases (latest 4.4.6 too). Now it's complaining, like you would expect from
    the tool if the rule is wrong.
    I know XFAB is aware of it and changed the ruleset. Just ask them for a kit
    working with 5.0.

    If you want to fix it yourself, put a "geomOr" around the two "geomGetEdge"
    commands.

    Most design kits from foundries are bound to software releases. So before
    upgrading the release you should speak with the foundry about the kit.

    Regards,
    Marc
     
    Marc Heise, Jan 26, 2005
    #2
  3. Michael Förtsch

    G Vandevalk Guest

    Since I don't have the derivation for hv_ng0 or nwtrms, I can only
    speculate.

    The rule you likely want to use is "ovlp". The rule "width" only takes
    facing edges from a
    single input polygon. ovlp takes facing edges of different polygons.
    What the rule implies is that you want specific edges of this polygon.


    It may be ok just to replace width with ovlp but ...
    IFF (i.e. if and only if ) the structures are well formed (i.e. non-related
    internal active gate
    edges cannot see each other, then a simple ovlp check will work.
    (If not you may need to tweek with opp ... ugly)

    YMMV ... Gerry
     
    G Vandevalk, Jan 26, 2005
    #3
  4. Thank you, now it runs.

    Michael.
     
    Michael Förtsch, Jan 26, 2005
    #4
Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.