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 have a problem with a model supplied by an IC vendor. SQ does not produce the expected waveform, and produces the message"warning - waveform contains less than the requested 1 cycle". By trial and error, I've determined that the problem is with the rising waveform with Vfixture = 0 - if I comment out part of this, the problem goes away. The problem waveform is attached. Can anyone tell me why this is happening, and what the SQ warning means ?Thans
Aball,The warning message is about the measurement due to bad waveforms.About VT waveforms, I don't think it will be a problem for Vfixture=0 or not. I couldn't figure out from your attached file for the issues but I guess something wrong with VI and VT curve mismatch.
It is quite common to get IBIS models where the I-V and V-t curves have some inconsistency that leads to problems with the simulation engine. Removing the v-t curves (or one set of curves) fixes this but you lose some accuracy. The warning message from the tool is telling you that the signal did not cross the threshold for the required number of pulses that you had selected.
Kai/LanceThanks for your help - I'm a bit of an IBIS novice, as you will have gathered, so I was a bit nervous about removing part of the model, however I think the part I've removed will have limited effect on the results. Bit disappointing to use a model from a major IC vendor, and a simulator from a major CAD vendor, and find them incompatible/not tested together - this was quite a fundamental and obvious fault - perhaps I'm being unrealisticThanks again
Aball,IBIS model has its own rules for syntax and usages. When it is broken, we called it "Bad" model. Simulator always play "Gabage in, gabage out" rule since it will not be able to find the way to fix them. So, to use kai's comment about VT and IV curve inconsistant issue as an example, if IBIS model is bad, it is not the problem for the simulator. but it is model self. It must be fixed. When you have a bad model no matter it is IBIS, Spice, S-parameters, VHDL or others, simulator will not give you the answers that you expected no matter simulator is from Cadence or Mentor or Synopsis or other vendors.By saying this, Good model is the MUST requirement to get correct results from simulations. Don't complain the simulator first, but needs to check whether your models are good first.
Aball:It is common to find IBIS models from large or small companies that sometimes do not even pass the syntax checks. Models that pass the checks are not necessarily tested. Some companies actually provide a comparison between the HSPICE model and the IBIS model showing good correlation. The chip vendors are in the business of making chips. Creating IBIS models is not a core function and they are often not given the attention we SI people feel they need. Chances are good that your particular model would also give you convergence errors in HSPICE. Deleting the v-t curves brings you back to IBIS 1.0. IBIS 2.1 brought out the V-T curves. Two sets of V-T curves are better for accuracy. If you do some searching, you will find papers that show comparisons between only using ramp info and using v-t curves.
The problem mentioned typically means that the logic thresholds are missing in the receivers, hence the waveform doesn't ever appear to "switch". So the tool thinks the "cycles" didn't happen. If you're just looking at waveforms, the warning typically can be ignored. But if you're doing automated cycle-based measurements/reports, you'll need to add the thresholds so the tool can count cycles.Donald