• 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. Help on creating via at specified points

Stats

  • Locked Locked
  • Replies 10
  • Subscribers 143
  • Views 15868
  • 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

Help on creating via at specified points

venuuuuu
venuuuuu over 13 years ago

 hi all,

       First i planned to draw the prBoundary where i want to place the contacts. When I run this code  the contact's are placed at where mid point prBoundary layer in layout. But previous values of rows and columns are created at latest prBoundary.

 My code is below. What is the problem. Is there any code to getspecified contact at specified location.

 cv = geGetEditCellView()
lpp= list("prBoundary" "drawing")
shapes = setof(y cv~>shapes y~>lpp==lpp)
;x=layerselect
x=car(shapes)
y1=yCoord( upperRight(x~>bBox))
y2=yCoord( lowerLeft(x~>bBox))
x1=xCoord( upperRight(x~>bBox))
x2=xCoord( lowerLeft(x~>bBox))
dx=x1-x2
dy=y1-y2
mx=x2+(x1-x2)/2
my=y2+(y1-y2)/2
no.columns=round((dx-.2)/.4)
no.rows=round((dy-0.2)/.4)
leHiCreateContact()
hiRegTimer("le0ContactForm->rows->value = no.rows" 1)
hiRegTimer("le0ContactForm->columns->value =no.columns" 1)
hiRegTimer("hiiToggleEnterForm(le0ContactForm)" 1)
mx:my
cancelEnterFun()

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 13 years ago

    I did give some ideas in my previous post.

    Here's a bit more detail though (I did a quick experiment). If you look at <IC5141instDir>/tools/dfII/samples/techfile/sample2003.tf it shows a couple of cdsViaDevice definitions (e.g. the one for M1_M2).

    If you define a via like this, you can then do:

    inst=car(geGetSelSet())
    inst~>layer1XEnclosure=0.3
    inst~>layer1YEnclosure=0.5
    inst~>layer1Direction="btrl"

    the direction can be any combination of the letters b (bottom), t (top), l (left), r (right) which indicates which sides the enclosure should be applied on. There are also the layer2 equivalent properties.

    I think that does exactly what you want.

    Note that the sample2003.tf tech file contains some OA-specific entries which will cause warnings if you load it (e.g the standardViaDefs and customViaDefs), but you can certainly borrow the ideas from this.

    cdsViaDevice is documented in the documentation too - just search for cdsViaDevice. In particular you can see this in the doc/ascitechfile/ascitechfile.pdf and doc/vlehelp/vlehelp.pdf

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 13 years ago

    I did give some ideas in my previous post.

    Here's a bit more detail though (I did a quick experiment). If you look at <IC5141instDir>/tools/dfII/samples/techfile/sample2003.tf it shows a couple of cdsViaDevice definitions (e.g. the one for M1_M2).

    If you define a via like this, you can then do:

    inst=car(geGetSelSet())
    inst~>layer1XEnclosure=0.3
    inst~>layer1YEnclosure=0.5
    inst~>layer1Direction="btrl"

    the direction can be any combination of the letters b (bottom), t (top), l (left), r (right) which indicates which sides the enclosure should be applied on. There are also the layer2 equivalent properties.

    I think that does exactly what you want.

    Note that the sample2003.tf tech file contains some OA-specific entries which will cause warnings if you load it (e.g the standardViaDefs and customViaDefs), but you can certainly borrow the ideas from this.

    cdsViaDevice is documented in the documentation too - just search for cdsViaDevice. In particular you can see this in the doc/ascitechfile/ascitechfile.pdf and doc/vlehelp/vlehelp.pdf

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information