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 am attempting to model a board to board connector. I am happy that I have the single line modelled correctly but I am having issues with modelling the coupled line version. I have a multi-line spice model from the connector manufacturer. I have referenced it from within a package model, using I believe the correct key words, including "terminal" lining up the order of the connector wires with that of the ports on the spice model. When I view this in the Model Integrity tool I get "ERROR @line 667: ABORT: Unable to Compile SubCircuit '11110' ". If I change the reference to another spice model the error is removed. Is there any obvious syntax gotchas I should be aware of?
I have attached the ibis model and the package model that my Ibis model refrences. I have resolved my previous error about the subcircuit compile by picking up the model from a DML file rather than an spice model. Do I need to redefine the pin/wire mapping in the package model, one of the application notes conforms that as this is defined in the Ibis model it will not be required? Pin 1 is mapped to wire 1, pin 2 to wire 2 and so on. My conections are on pins 6, 8 , 10 and 12. I was expecting that with the tracking such that only the connector should have an effect on crosstalk the crosstalk analysis would generate waveforms based on the connections within the connector but this does not happen. This has led me to think that my package model is probably incorrect in the way it maps pins to the multiline model but I am pretty sure it has been created as per "Modeling Connectors Using Coupled SPICE Subcircuits in DML PackageModels". thanks for any help or suggestions.
When using these models at the physical board level, the coupling brought into the simulation is driven by Geometry Window in the layout. For example, for coupled pins x, y, and z to be brought into the circuit, nets x, y, and z need to be coupled together on the board within the Geometry Window. To perform analysis with "connector-driven" coupling, the easiest way is to bring in the SPICE model for the coupled connector model into SigXp. In SigXp the coupling is "model-driven" rather than "layout-driven". Future functionality is expected to enable "connector-driven" coupling to be analyzed, regardless of physical layout.