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 hope you will undestand me. My English is not very well.
I have to check a layout with assura. It is an array and consists of tree components. I call them "basic cells". So I build tree types of columns of those cells and then I add them to an array. If I check the columns separetly. It works. Thereby the "basic cells" will be ckecked with ?flattenCellContents contition. If I try to verify the whole array. I get errors (device, nets) in one column and their subcell, "one of a basic cell". This column consist of two mirrored and overloop "basic cells of one type".
I think I get the error message because the cells overlap. I assume Assura put some devices on the top of hierarchy and then can not map schmetatic and layout. So my question is, are there any rules I can put to avoid this problem?
I have a solution that woks but I have to flatten one type of array. It take a lot of time to check the whole array.
If you have some ideas, post otherwise correct my language skills! :-)
Best regards, Dennis
Hi DennisWould you please post the specific error messages? It would be good if you can upload the cls file in the run directory. Perhaps you can try adding expandOnError cmd and see if it solves the problem. It can be found in avCompareRules of the lvs form. If you are running by batch mode, please add the following to the rsf file:avCompareRules( expandOnError( (unstableDevices t) (swap t) (reduce t) (pins t) (match t) (swapThres t) (instCount t) (skipMatchOnReduceError t) (ambiguousPinAssignment t) (parameter t) )) ;avCompareRulesBest regardsQuek
In reply to Quek:
Thank you very mach for your reply and your hint! It works! Schematic and Layout match without any warrnings and errors!
Thank you once more!
In reply to Dennis Faber: