• 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. How to change via level with skill in IC6

Stats

  • Locked Locked
  • Replies 31
  • Subscribers 148
  • Views 29584
  • 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

How to change via level with skill in IC6

Eric L14
Eric L14 over 14 years ago

 In IC6, I have a bindkey which change via level (via1 to via2) . Main part of the code is:

; Current selected via
viaToBeChanged=car(geGetSelSet())

; new via identifier
newVia=dbOpenCellViewByType( technName viaName "layout" nil "r")
if( newVia then
  viaToBeChanged~>master=newVia
)

Do you know how doing the same thing in IC6 ?

Thanks in advance

Eric

  • Cancel
  • kpai
    kpai over 14 years ago

    Thanks Andrew!    It works like a charm now.

    -Kathy =)

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Gurup
    Gurup over 13 years ago

    Hi Andrew,

      Is there anyway to change the existing via rows or column, by using viadefs parameter

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

    No. You can't do that (it doesn't make sense either).

    You can change the rows and columns of an existing via instance by using:

    viaInst~>cutRows=4
    viaInst~>cutColumns=6

    or you could use dbReplaceProp() or dbReplacePropList() to change them in one go.

    You'll find that you'll get a different viaHeader if you do this - it will bind that via to a different header.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Gurup
    Gurup over 13 years ago

    Thanks Andrew,I will try this.

    can you tell me what is difference between the objects and instances.

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

    Not sure I entirely understand the question, because it's like asking for the difference between fruit and apples.

    In both CDB and OpenAccess, various things are represented as "objects" in the database. For example, there are objects to represent shapes (e.g. rectangles, polygons, paths, ellipses etc), objects to represent instances, objects to represent nets, terminals, and so on and so on. Instances are a type of object. In CDB there was no specific object type for vias; vias were just instances. In OpenAccess however, instances are one type of object, and vias are another type - so there is now a specific object type for vias, thus separating them from ordinary instances (e.g. instances of devices, instances of other cellViews and so on).

    Hopefully that answers your question?

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Gurup
    Gurup over 13 years ago

    Thanks Andrew its working ..

    Please tell me the such similar command to change the via pitch, in one shot

    Andrew Beckett said:

    No. You can't do that (it doesn't make sense either).

    You can change the rows and columns of an existing via instance by using:

    viaInst~>cutRows=4
    viaInst~>cutColumns=6

    or you could use dbReplaceProp() or dbReplacePropList() to change them in one go.

    You'll find that you'll get a different viaHeader if you do this - it will bind that via to a different header.

    Andrew.


     

    --Thanks & Regards

     Guru

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Gurup
    Gurup over 13 years ago

     Thanks  Andrew,for your nice ans  :-)

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

    Guru,

    You can find this information out yourself very easily. Place a via, and change the properties to what you want. For example, I altered the via width and length, and spacings. Then I did:

    car(getGetSelSet())~>viaHeader~>overrideParams

    and I get:

    (("cutWidth" 0.16)
        ("cutHeight" 0.17)
        ("cutRows" 3)
        ("cutColumns" 2)
        ("cutSpacing"
        (0.3 0.2)
        )
    )

    From this I can see that the spacing is controlled by cutSpacing, and similarly for the width and length (there's no "pitch", but obviously that's the width plus the horizontal spacing).

    Then I can do

    viaInst~>cutSpacing=list(0.6 0.4)
    viaInst~>cutWidth=0.25

    or whatever. You can use the same approach to find out the parameter names - try changing it interactively, then query the database to find out the names used.

    Regards,

    Andrew.

     

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

    Dear Andrew,

    I am using your methododlogy to convert cdb instance vias to oa stdVias with dbCreateVia.

    The issue is that my pcells having conditional inclusions of vias do not work any longer. I must recreate them.

    Is there an easy way to update the pcell information with the new via objects?

    Regards,

     Antonios

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

     Antonios,

    I don't really understand your question.

    Andrew

    • 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