• 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. How to define double vias in rules file for VCAR

Stats

  • Locked Locked
  • Replies 12
  • Subscribers 126
  • Views 19093
  • 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 define double vias in rules file for VCAR

PSRK
PSRK over 13 years ago

 Hi,

 I'm using the below constraint in the vcar rules file  before exporting. The VCAR is placing single via while routing.

    list( '("tsmc18rf" "M2_M1" "symbolic") t)

But I dont know the rule to keep double contact/via in the router .Please help me.

 

Thanks,

Siva

  • Cancel
  • craigth
    craigth over 13 years ago

    Siva,

    What release of Virtuoso and VCAR are you using?

    What do you mean by “vcar rules file”? Do you mean the .do file? 

    In parallel to a response to the questions above, reference the following VCAR commands in the IC615 Virtuoso Chip Assembly User Reference Manual. These commands allow you to specify and control multiple vias during routing.
    • use_via http://support.cadence.com/wps/PA_DocumentViewer/pubs/iccraft/iccraft6.1.5/cmd_circuit/use_via_descriptor.htm 
    • use_array
    •  enforce_use_array_rule http://support.cadence.com/wps/PA_DocumentViewer/pubs/iccraft/iccraft6.1.5/cmd_sw/enforce_use_array_rule_key_set.htm
    You can also reference some good information in the IC615 Virtuoso Chip Assembly User Guide  
    •  Via Arrays and Via Images       http://support.cadence.com/wps/PA_DocumentViewer/pubs/iccausr/iccausr6.1.5/chap7.html#98914 
    • Choosing to use Via Arrays or Via Images       http://support.cadence.com/wps/PA_DocumentViewer/pubs/iccausr/iccausr6.1.5/chap7.html#829052  
    • Via Adjacency Rules for Via Arrays      http://support.cadence.com/wps/PA_DocumentViewer/pubs/iccausr/iccausr6.1.5/chap7.html#828997

    If you mean the oa techFile and/or constraint definition as the “vcar rules file” you should reference the following sections in the Virtuoso Chip Assembly User Reference Manual

    • OpenAccess  http://support.cadence.com/wps/PA_DocumentViewer/pubs/iccraft/iccraft6.1.5/toc/iccraftTOC5.html 
    • Mapping Constraints to Virtuoso Chip Assembly Router  http://support.cadence.com/wps/PA_DocumentViewer/pubs/iccraft/iccraft6.1.5/oa/mapping_constraints_to_vcar.htm 
                oaViaDefArrayValue      use_via class rule (from nondefault routing constraint)  

     

    Regards,   

     

    Craig T.

     

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

    Siva,

     Sorry about the formatting. Below is a reformatted version of my response.

    Siva,

    What release of Virtuoso and VCAR are you using?

    What do you mean by “vcar rules file”? Do you mean the .do file? 

    In parallel to a response to the questions above, reference the following VCAR commands in the IC615 Virtuoso Chip Assembly User Reference Manual. These commands allow you to specify and control multiple vias during routing.

    • use_via http://support.cadence.com/wps/PA_DocumentViewer/pubs/iccraft/iccraft6.1.5/cmd_circuit/use_via_descriptor.htm 
    • use_array
    • enforce_use_array_rule http://support.cadence.com/wps/PA_DocumentViewer/pubs/iccraft/iccraft6.1.5/cmd_sw/enforce_use_array_rule_key_set.htm

    You can also reference some good information in the IC615 Virtuoso Chip Assembly User Guide  

    •  Via Arrays and Via Images       http://support.cadence.com/wps/PA_DocumentViewer/pubs/iccausr/iccausr6.1.5/chap7.html#98914 
    • Choosing to use Via Arrays or Via Images       http://support.cadence.com/wps/PA_DocumentViewer/pubs/iccausr/iccausr6.1.5/chap7.html#829052  
    • Via Adjacency Rules for Via Arrays      http://support.cadence.com/wps/PA_DocumentViewer/pubs/iccausr/iccausr6.1.5/chap7.html#828997

    If you mean the oa techFile and/or constraint definition as the “vcar rules file” you should reference the following sections in the Virtuoso Chip Assembly User Reference Manual

    • OpenAccess  http://support.cadence.com/wps/PA_DocumentViewer/pubs/iccraft/iccraft6.1.5/toc/iccraftTOC5.html 
    • Mapping Constraints to Virtuoso Chip Assembly Router  http://support.cadence.com/wps/PA_DocumentViewer/pubs/iccraft/iccraft6.1.5/oa/mapping_constraints_to_vcar.htm 

                oaViaDefArrayValue      use_via class rule (from nondefault routing constraint)  

     

    Regards,   

     

    Craig T.

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

     HI Craig...

     I didn't mean the do file. We do specify a rules file in "export to router" window. I check the box "Use rules file" and the rules file in which I define the Minimum widths minimum spacings and the vias to be used. For example, I have attached the rules file. please look into it.

     Thanks,

    Siva

    • icc_1h2v3off_rules.txt
    • View
    • Hide
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • PSRK
    PSRK over 13 years ago

     Hi Craig,

    I referred to the use_via and use_array commands from the links that you have posted. My issue is solved now. I added these lines to my do file.

    select all nets
    define (group group1 (selected))
    circuit group group1 (use_via (use_array M2_M1 1 2))

    ##Standard Routing Command
    route 25
    clean 2
    route 50 16
    clean 4

    I was wrong with the rules file. Thanks for your response.

     

    Thanks,

    Siva

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Peter123
    Peter123 over 13 years ago
    Hi Siva,

    I'm facing the same issue as you now,

    I can't find the box "Use rules file" in my IC6.1.5 startup form.

    can you pls show me how is your form look like?

    Snapshot below is my starup form.

    Thanks,

    peter
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • PSRK
    PSRK over 13 years ago

    Peter,

    I don't see your attachment. Did you attach it properly?

    Thanks,
    Siva

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

    Attached is my export to router form. click on the exporttoroute.png image.

     

    Thanks,
    Siva

    • export2router.png
    • View
    • Hide
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 13 years ago

    In IC615, because it is working directly on the OA database, it will use the technology rules directly from OA - and hence there's no option to specify a rules file. The thing that Siva was describing before is implemented with a "do" file, and you still have the ability to specify one of those.

    Andrew

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

     Hi Siva,

     For some reason, i can't upload my snapshot. 

    Your form is like IC5.1.X version, which i used to have.

    But, I'm in IC6.1.5 now; the form looks totally diff.

     Thanks,

    -peter-

     

     

     

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

     Hi Andrew,

    Since there is no rules file in OA database,what should i do in order to use the command "use_via"?

    Thanks,

    -Peter-

     

    • 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