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.
When using mtline model in cadence spectre schematic simulation, why I
can not connect output of one mtline to output of another mtline?
(warnings show there will be short circuit and floating nodes)
This vaguely rings a bell.
Where is the warning appearing, and what exactly is the message you see?
Which IC and MMSIM version are you using? (the spectre version will appear in the spectre log file at the top, and the IC version can be found by using Help->About in the CIW, or by typing getVersion(t) in the CIW).
In reply to Andrew Beckett:
In reply to jyang:
Please show a picture of the schematic (use the Option tab on the forum to upload it) and the precise messages from the CIW (please cut and paste them).
The problem is something other than what I was remembering (which was fixed a long time ago)
warning message in CIW
It's because the symbol has the pins on the left as being input pins, and those on the right as being output pins.
It won't affect the simulation - it's just a spurious check because the pin directions are set on mtline. It would be better if mtline had inputOutput pins as each pin - then the problem wouldn't occur. So I'd suggest raising this with customer support.
You can go to Check->Rules and set "Shorted Output Pins" to "ignored" and then the warnings will go away.
This has been submitted as CCR 1156640 (Title: Pins of mtline should have inputOutput direction). Anyone who also has a problem with the pin directions of the mtline component should consider asking Cadence support to file a duplicate of this CCR on his behalf. If more people are asking for this change, it is more likely to be implemented soon.
In reply to Frank Wiedmann:
I have just received the following email from Cadence:
Hello Frank,Regarding Case 45446581, "Change pins of mtline in analogLib to inputOutput." I wanted to inform you that your Cadence Change Request (CCR) number status has been changed.The new status is set to Inactive, which means that no action is planned. EachCCR is carefully considered, evaluated, and prioritized along with other fixes,planned feature additions, and enhancement requests, for possible inclusion inupcoming product updates and releases.If you feel this is very important and would like us to reconsider, respond to thismessage and the AE working on your Case will be in contact with you.Regards,Cadence Customer Support
I am a bit surprised about this as I would have assumed that this change could be made in a few minutes. Anyone who still would like to have this changed should ask Cadence to file a duplicate of CCR 1156640 on his behalf.
First of all, there really is no such thing as a "few minute" fix. Fixes need to be implemented, reviewed, checked in and potentially merged into multiple streams, tested, regression tests implemented - all of which takes more time. Given that we end up with lots of small fixes such as this which are competing for attention, we tend to focus on those which are the biggest obstacles to be fixed in hotfixes. Other things will be planned for future releases during the planning phase for a release. If submitted before that planning phase, or even if the plate is too full for a particular release, they may be marked Inactive-Backlog. These are then reconsidered at the next planning phase - we cannot plan the next release as we go along as otherwise it would always be first-in first-out rather than assessing the overall requirements.
So no need to campaign for this in public; it's not being ignored.
Thanks a lot for the clarification. Unfortunately, the wording of that email gave me the impression that Cadence did not intend to ever implement this change at all.