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.
Get email delivery of the Cadence blog featured here
This posting is part of a series of blogs on dynamic power management in digital-centric mixed-signal verification environments. In this post, I will cover metrics collection from analog circuits during mixed-signal simulation.
My previous blogs covered some of the following topics:
Previous postings include:
Analog Coverage Model
Once the desired features of interest have been extracted from the spec and captured in an executable verification plan, the next step is to quantify the desired functionality that needs to be tested. This is typically done by designing a coverage model and collecting metrics from the analog elements in the design.
For maximum dynamic power savings, it is best to run the device at the lowest possible operating voltage. The device can function at any of the following operating nominal-voltages:
In our example, the effect of varying Vbat on Voltage regulation by the LDOs is carefully monitored, and voltage transitions are measured and assigned to voltage bins in the cover groups.
Figure 1 shows code for collecting functional coverage from the wreal models used in the prototype SoC. In this example, the battery voltage Vbat is binned into four categories. Vbat varies over different tests through predetermined ranges and sequences specified in the verification plan, and is kept track of to ensure all intended test conditions have been met. Figure 2 and Figure 3 show the cumulative results of the full regression run.
As the device is run through various tests, the output voltages from each LDO are carefully tracked. This gives us a good measure of the percentage of the time that each power domain in the device is run at lowest possible voltage, which has a direct correlation to the dynamic power actually being conserved. As seen in Figure 2, the MCU is successfully being run to conserve dynamic power - the higher the coverage data for the lowest nominal-voltage (0.8V), the more power that has been conserved. It is also important to ensure that all possible combinations of LDO voltages have been exercised for all possible legal Vbat values. This can be achieved by creating a cross product of Vbat with Vldo_mcu.
Figure 3 shows the hole analysis run from the vPlan which in turn reveals that the DSP power domain was never run at the highest nominal voltage of 1.6V. Thus, this part of the plan has not been fully exercised and needs more tests to cover missing condition.
Similarly, holes in the verification space are seen in Figure 2. These need to be filled by running adequate incremental tests to achieve functional closure.
In the next blog, I will talk about concepts behind DMSV - Digital-Centric Mixed Signal Verification.
Stay tuned for more...