• 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 Design
  3. Replacing Via1 to Via2 per Bindkey in IC5.1

Stats

  • Locked Locked
  • Replies 11
  • Subscribers 126
  • Views 18163
  • 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

Replacing Via1 to Via2 per Bindkey in IC5.1

Laur9
Laur9 over 15 years ago

Hi,

is it possible to replace from Via1 to Via2 with the help of some skill function, in Virtuoso Layout IC5.1 ?

I would like to select an already placed  via and change his via typ without to open Contact Properties Form.I don't want to change the other properties of the via.

I have already tried to get , per skill, the properties of the selected instances but I found no way to change the via ( contact type to be exactly) type. I used this code to try to do the work but Virtuoso not allows to do this kind of replacement.

 cv = deGetCellView()

foreach(i cv~>instances
        when( i~>cellName == "via1"
                          i~>cellName = "via2"
                ))

I am wondering whether there is a better way to perform it. Thanks a lot in advance.

Thanks for your help,

Regards

 

Laurent

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 15 years ago

    Hi Laurent,

    Two things:

    1. Use geGetSelSet() to get the list of selected instances
    2. Change the via master by changing the ~>master attribute rather than the ~>cellName attribute

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • blankman
    blankman over 14 years ago

    Hi Andrew, I am also trying to initiate this (on IC5.1). However when I enter the code below I get........

    *Error* setSGq: dbSetq: Can not set attribute - cellName

     

    Am I missing something?

    Thanks,

    Brian

     

    geGetSelSet()~>master~>cellName='met2_met1_b

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

    Brian,

    No, you can't set the cellName in the master - the master is the cellView which has been instantiated, so changing the cellName would not make sense. What I meant was you need to do:

    foreach(fig geGetSelSet()
      when(fig~>objType=="inst"
        newMaster=dbOpenCellViewByType(fig~>libName "met2_met1_b" fig~>viewName)
        fig~>master=newMaster
        dbClose(newMaster)
      )
    )

    Something like that (not tested).

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • blankman
    blankman over 14 years ago

    Cheers Andrew, works a charm, appreciate the help

    Brian

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Adrian Nistor
    Adrian Nistor over 14 years ago

     Hello All,

    I understand that those vias were added like instances, not like vias (create -Via or dbCreateVia I think) 

    In this case, when a via created with Create - Via menu option, which is the best method to change it to another via type?

     

    Thank you,

    Best Regards,

    Adrian

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • blankman
    blankman over 14 years ago

    Andrew, could you help me with one last thing. Im trying to add bind keys to increment and decrement the amount of rows and columns in a selected contact cell.

     

    Im using...

    procedure(BSchangeVia2x1()
    foreach(fig geGetSelSet()
      when(fig~>objType=="inst"
          propValue = car(fig~>prop~>value)
          fig~>prop~>value=propValue+1
        )
        )
    )
    hiSetBindKey("Layout" "Alt<key>KP_Add" "BSchangeVia2x1()")

     

    However this increments both row and column values. Is there a way to increment only the row value and leave the column value as is?

    Brian.

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

    Brian,

    As this has been answered in your other question - /forums/p/19138/1275434.aspx#1275434  I won't answer it here as well.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Guruprasad S
    Guruprasad S over 10 years ago

    Hi ,

    Virtuoso version IC6.1.6-64b.500.11

    can any one write full skill to set BindKey


    to change via 1 to via x (x=2 , 3 ,4 ,5 ,6, 7 ,8)

    i have inserted via 1 in layout , now i want to change it to Via x using Bindkey .

    i referred  many examples and codes
    fig=geGetSelSet()

    fig~>master

    foreach(fig geGetSelSet()

    when(fig~>objType=="inst"

    newMaster=dbOpenCellViewByType(fig~>GURU "M4V3M3" fig~>layout)

    fig~>master=newMaster

    dbClose(newMaster)


    Error "

    fig~>master

    (nil)

    >

    master is unbound variable ..

               " inst"  not a valid function

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

    This won't work in IC61X, because vias are stored differently in OpenAccess. I'm sure there are numerous posts on this topic (given that I recall answering it multiple times). Try searching for dbCreateVia

    Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Guruprasad S
    Guruprasad S over 10 years ago

    Hi Andrew,

    I tried this code , and its working as i needed ,

    But whole vias in layout are getting converted ....

    procedure(viachange( )

    cvId= geGetEditCellView()

    vias=leSearchHierarchy(cvId cvId~>bBox 0 "via" list(list("via definition" "==" "^M3V3M4$")))

    leReplace(cvId vias list(list("via definition" "==" "M1V1M2")))

    )

    hiSetBindKey("Layout" "shift<key>1" "viachange()")

    i want to convert only selected vias ..

    • 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