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.
Hello,I want to create a new schematic from the library which is created by me. I put an instance from this library to the new schematic. I want to change pin names of this instance. The problem is that some pin names have a bus notation ( Ex: A<3:0>) and i want to change width of this pin (Ex: A<5:0>). Cadence document says width of pin cannot change by " myInst~>pin~>term~>numBits". Is there any way to do this?
You can't change the name of the pin on an instance - it makes no sense. This is nothing to do with it being a bus pin - but the pin name (or rather terminal name,) can only be set on the master (i..e the symbol itself). This then has to match the corresponding schematic, otherwise view switching during netlisting won't work.
So I'm not sure what you're really trying to do here?
In reply to Andrew Beckett:
Thanks for the prompt reply Andrew.
I might have not been very clear. The aim is to generate a schematic and a symbol programitically, instantiating several modules under a new schematic and a symbol which are connected to the above hierarchy level. The instantiation might have different bus widths, so the pins have to change accordingly. I'm not trying to just modify the selected instance, which, I realize may not be ideal, but right now, using a scratch cellview (a copy of a generic symbol-schematic pair and editing the corresponding pin names and widths under that symbol.)
I realize that the approach I'm taking (instantiating the instance first and then trying to edit it) may not be correct. Is there a better way to approach this?
In reply to cgurleyuk:
A bit of a late reply - I'm still not really sure what you're doing. You normally would need to set the pin (or terminal) names on the symbol and then instantiate it and connect it up - even if doing it programmatically.