• 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. Changing the number of stdVia arrays with different sizes...

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 142
  • Views 3474
  • 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

Changing the number of stdVia arrays with different sizes of vias in a limited area

dakuang01
dakuang01 over 1 year ago

Hi there,

I could use any help.

Let's say I have 2 or 3 different sizes of via arrays stacked.

For example,
1) Group1 : Via1/Via2/Via3 = 0.1umx0.1um
2) Group 2: Via4/Via5 = 0.2umx0.2um
3) Group 3 : Via6/Via7 = 0.5umx0.5um

The selected via arrays could vary like Via2 thru Via7, Via1 thru Via4, Via5 thru Via6, and more.

The original code I have below is very simple but has been very useful for me. However, it only worked for each separate group since cutHeight, Layer Enclosure, LayerOffset values are different per each group.

Now I would like to improve this to work all via groups at once and am trying dbCreateVia but it looked like stdVia dbID didn't work for d_viaDefId which means I have to get all via info from techGetTechFile or techFindViaDefByName.

I'm just wondering if there's any way to manipulate stdVia itself instead of using dbCreateVia. 

And I'm thinking to get the area of Via6 or Via7(Via4 or Via5 when no Via6/7) and put maximum via arrays in in the area. Can I get some advice on this?



Thanks,

Jenny

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 1 year ago

    Jenny,

    Your code (and a plea from me to everyone to post code as text rather than screenshots - if I had wanted to try it out, I would need to either type it in or use OCR to try to read the code from the image, then spend time fixing up the cases where OCR got it wrong and so on) is iterating over the list of cutColumns and simply setting t_newColumn to one greater than whichever was the last item in the selected set - then setting all the vias to have that number of columns.

    Rather than this, why not use:

    procedure(CCFincColumns()
      foreach(via geGetSelSet()
        when(via~>objType=="stdVia"
          via~>cutColumns=via~>cutColumns+1
        )
      )
      t
    )

    This iterates over each via, and increments the cutColumns for each via individually.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • dakuang01
    dakuang01 over 1 year ago in reply to Andrew Beckett

    Andrew,

    If I made you have inconvenience, I aplogize. I thought the code I asked would look very different from than the code so just put a screenshot. 
    Next time, I'll paste in text. 

    Yes, your code looks a lot better than mine.

    The question I have is I have to increase different numbers per each group of the vias since the via size is different. Sorry if my question was not clear.

    Jenny 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • dakuang01
    dakuang01 over 1 year ago

    I'm so sorry. I can't seem to find a way to change the format to coding style. :(

    This is the code I'm currently working on. I just learned dbReplaceProp function from one of the previous posts so am trying to make the code work with it.

    procedure( stdVia_column_plus()
    let((cv d_tfId l_Vx_4B l_Vx_2B l_viaOrder l_viaCount l_lowest_Mt l_highest_Mt l_origin l_bBox t_orient n_col n_row d_via l_via
    l_column t_newColumn)

    l_Vx_2B = l_Vx_4B = l_viaOrder = l_viaCount = l_lowest_Mt = l_highest_Mt = l_origin = l_bBox = l_via = nil
    d_tfId = d_via = nil
    t_orient = ""
    n_col = n_row = 1

    cv = geGetEditCellView()
    d_tfId = techGetTechFile(cv)

    l_paramName = '("cutLayer" "cutWidth" "cutHeight" "cutRows" "cutColumns" "cutSpacing" "layer1Enc" "layer2Enc"
    "layer1Offset" "layer2Offset" "originOffset" "imp1Enc" "imp2Enc" )
    l_viaOrder = list((1 "VM1_M2") (2 "VM2_M3") (3 "VM3_M4") (4 "VM4_M1_2B") (5 "VM1_2B_M2_2B") (6 "VM2_2B_M1_4B") (7 "VM1_4B_M2_4B"))
    l_viaCount = length(selectedSet())
    l_lowest_Mt = car(sortcar((selectedSet()~>viaHeader~>viaDefName) 'lessp))
    l_highest_Mt = last(sortcar((selectedSet()~>viaHeader~>viaDefName) 'lessp))

    l_Vx_4B = setof(a selectedSet() ((a~>viaHeader~>viaDefName == "VM2_2B_M1_4B")||(a~>viaHeader~>viaDefName =="VM1_4B_M2_4B")))
    l_Vx_2B = setof(a selectedSet() ((a~>viaHeader~>viaDefName == "VM4_M1_2B")||(a~>viaHeader~>viaDefName =="VM1_2B_M2_2B")))

    if((car(l_highest_Mt)-car(l_lowest_Mt)+1) != l_viaCount then
    printf("Warning: Check if there is any redundant or missing vias")
    else if((car(l_highest_Mt)-car(l_lowest_Mt)+1) == l_viaCount then
    ; When selected the correct number of vias from the highest metal down to the lowest, move onto the next codes
    if(l_Vx_4B != nil && length(l_Vx_4B)==2 then
    foreach(a l_Vx_4B
    when(a~>viaHeader~>viaDefName == "VM2_2B_M1_4B"
    dbDeleteObject(a)
    );when
    when(a~>viaHeader~>viaDefName == "VM1_4B_M2_4B"
    l_origin = a~>origin
    l_bBox = a~>bBox
    t_orient = a~>orient
    n_col = a~>cutColumns + 1
    n_row = a~>cutRows
    );when
    );foreach
    d_via = techFindViaDefByName(d_tfId "VM2_2B_M1_4B")
    l_via = append1(l_via dbCreateVia(cv d_via l_origin t_orient list(n_col n_row)))
    else if(l_Vx_4B != nil && length(l_Vx_4B)==1 then

    );endif
    );endif
    );endif
    );endif
    );let
    );procedure

    • 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