• 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 SKILL
  3. define arrayed contacts in techfile

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 144
  • Views 15053
  • 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

define arrayed contacts in techfile

Howel
Howel over 12 years ago

The DRC rules require different spacings for two single contacts and an arrayed contacts. For example, when there are only two V1 vias, the spacing is 0.21. If the vias form an 4x4 array, the spacing should be 0.25 instead.

In the technology file, we can create symbolic contacts which can be called when you press "o" ( or use menu "create Contacts..."). But the spacings can't change if rows and columns are > 4. Although the user can change the pitch manually, it's a little tedious.

So we want to change the definition of the symbolic contacts to make spacing change automatically. In the spacingRules (one subclass of physicalRules class) we defined "viaSpacing  "V1" list(4 0.25 0.25)". But it doesn't work. We can write skill codes to do this, but that seems overkill.

Dose anybody know a simple way to modify the technology file to make it?

Thanks,

Howel

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    Howel,

    Can you say which version of the tools you're using? It's quite important for this question. I'm guessing IC5141, but I don't want to spend a lot of time explaining it for one release only to find that actually you're using a different one...

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Howel
    Howel over 12 years ago

    Andrew,

    You're quite right; we are using IC5141_usr6. Maybe too old, but we can only use this one.

    Regards,

    Howel

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • sPoK
    sPoK over 12 years ago
    Hi Andrew,

    I was wandering the same thing but I couldn't find a proper constraint.

    minLargeViaArraySpacing is the closest I could find but I'm not using arrays and anyway this constraint is only valid for VSR.

    What I need is inceased via (cut) spacing from 0.3 to 0.35 for via matrix 6x6 and above to satisfy density rules.

    It would be very useful having this when using Create Via - Auto Via.

    Sort of a spacingtable:

    vialayer

    numXcut     numYcut     spacing

    0 0     0.3

    6     6     0.35    


    I'm using IC615 ISR16.

    Thanks,

    S
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • dmay
    dmay over 12 years ago
    You can do something like this. Our via layer is "via1". At 3 cuts, our spacing increases. Look at the documentation for "viaSpacing" because this constraint is very configurable.
      ( "foundry"       nil     spacings(     ( viaSpacing "via1" 'distance 15.0 'numCuts 2 0.35)          ( minSpacing                 "via1"    0.3 )

    Derek
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    And for Howel's IC5141 question, you probably need to be using cdsVia vias rather than the simple symbolic contacts (I didn't have a chance to test this, I'm afraid).

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • sPoK
    sPoK over 12 years ago

    Hi Derek,

    I remember experimenting with this constraint earlier, it has a limitation on number of adjacent via cuts, there's no point setting numcuts above 8 since every center via can be surrounded with max 8 vias so spacing is increased already at 3x3 via matrix which I don't want.

    Thanks,

    S. 

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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