Cadence® system design and verification solutions, integrated under our System Development Suite, provide the simulation, acceleration, emulation, and management capabilities.
System Development Suite Related Products A-Z
Cadence® digital design and signoff solutions provide a fast path to design closure and better predictability, helping you meet your power, performance, and area (PPA) targets.
Full-Flow Digital Solution Related Products A-Z
Cadence® custom, analog, and RF design solutions can help you save time by automating many routine tasks, from block-level and mixed-signal simulation to routing and library characterization.
Overview Related Products A-Z
Driving efficiency and accuracy in advanced packaging, system planning, and multi-fabric interoperability, Cadence® package implementation products deliver the automation and accuracy.
Cadence® PCB design solutions enable shorter, more predictable design cycles with greater integration of component design and system-level simulation for a constraint-driven flow.
An open IP platform for you to customize your app-driven SoC design.
Comprehensive solutions and methodologies.
Helping you meet your broader business goals.
A global customer support infrastructure with around-the-clock help.
24/7 Support - Cadence Online Support
Locate the latest software updates, service request, technical documentation, solutions and more in your personalized environment.
Cadence offers various software services for download. This page describes our offerings, including the Allegro FREE Physical Viewer.
Get the most out of your investment in Cadence technologies through a wide range of training offerings.
This course combines our Allegro PCB Editor Basic Techniques, followed by Allegro PCB Editor Intermediate Techniques.
Virtuoso Analog Design Environment Verifier 16.7
Learn learn to perform requirements-driven analog verification using the Virtuoso ADE Verifier tool.
Exchange ideas, news, technical information, and best practices.
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.
It's not all about the technlogy. Here we exchange ideas on the Cadence Academic Network and other subjects of general interest.
Cadence is a leading provider of system design tools, software, IP, and services.
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.
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
Craig Thompson Sr. Technical Leader Technical Field Operations, North America-Central Region 866.225.3138
Sorry about the formatting. Below is a reformatted version of my response.
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.
You can also reference some good information in the IC615 Virtuoso Chip Assembly User Guide
oaViaDefArrayValue use_via class rule (from nondefault routing constraint)
In reply to Craig Thompson:
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.
In reply to PSRK:
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 50 16
I was wrong with the rules file. Thanks for your response.
In reply to Peter123:
I don't see your attachment. Did you attach it properly?
Attached is my export to router form. click on the exporttoroute.png image.
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.
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.
In reply to Andrew Beckett:
Since there is no rules file in OA database,what should i do in order to use the command "use_via"?
You don't Have to worry about the rules file. Anyways, you can still use the commands in my earlier comments in your do file. or you can just type in the commands in the autorouter console before you execute route command.
You can attach the files in here if you click the "options" botton next to the compose botton
What you should be able to do is define inside virtuoso which vias you wish to use by creating a constraint group and defining the allowable vias. That can be done in the constraint manager in VLS-XL.
If anything is unclear though, the best thing to do is to go to customer support.