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.
Hi, I can't import or merge 2 .brd files. I looked up hierarchy and merge, but didn't find much. Allegro PCB editor 15.2Thanks. Kevin.
Hi Kevin,You can but it is not straight forward. You need to merge the two databases by importing one of the .brd files into the other. This could be done in different ways but the bottom line is that you need the logic for both designs to be incorporated as one. If you are using a 3rd party netlist then this is not an issue as you can readily merge netlists and if you are using a circuit driven design then the circuits will also need merged. If your databases are logic driven then you could create a hierarchy including the two boards and you could possibly use re-use modules to create the combined databases.If you are using 3rd party netlists then you can recreate one of the databases within the other by outputting the data and reading this into the other. Much the same as you would re-create a corrupted database. Be aware though that your reference designators will need to be different between the two databases. An auto-rename would resolve this prior to outputting the clips and logic. See sourcelink article.http://sourcelink.cadence.com/docs/db/kdb/1998/Sept/1816549.htmlCheers,KP
The link you posted is for an error message "descendent of .sav, not reliable call Cadence Support."Problem : Allegro v13.x rebuilding a corrupt (.sav) database using clipboard.Is that the link you intended to post? I think my problem is different. Thanks. Kevin.
That was the correct link, the same principle applies. Instead of reading the generated files from one of your databases into a new .brd file you read the files into the other database. This creates one database which contains the contents of both databases. N.B. There must not be duplicate reference designators and you must offset the datums so that the designs are not placed direcly on top of each other.