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.
With no standard way to represent power consumption for silicon IP, early IC power estimation can be difficult. But help may be on the way, as the SPIRIT Consortium and its members, including Cadence, discuss possible approaches to IP power modeling.
I first became aware of this problem at a seminar held by Cadence on the Encounter Digital Implementation System 8.1. During a discussion about chip planning, an audience member noted that there is no standard way for hard IP providers to represent power data. Thus, he noted, one provider might use a worst-case number derived from a static analysis, while another uses a best-case number from simulation. This makes it difficult to run a meaningful chip estimation that includes power.
For more insight into the problem, I talked to Thad McCracken, product engineer for chip planning solutions at Cadence. He noted that it’s somewhat problematic to give a power consumption number for a given piece of IP. You can say the IP consumes 145 milliwatts, but what is that statement based on? Actual power consumption depends on many factors, including technology node, activity level, clock rates, and selection of low or high voltage threshold cells. It’s also impacted by voltage and temperature – and we may not know whether the IP provider assumed best case, worst case, or something in between.
Moreover, Thad noted, embedded IP increasingly comes with low-power features such as voltage domains. What information is conveyed about those domains, when they shut off, and what voltage levels they run? A processor core probably has different operating modes, such as active, idle and sleep. To get a good power estimation, you have to know what the processor is doing at any given time.
“If one vendor characterizes power consumption in IP with one set of assumptions, and another vendor assumes a different set of conditions, and you put all those numbers together in an estimation context, it’s difficult to know whether your total chip power estimate is realistic,” Thad said.
The folks over at the SPIRIT Consortium are aware of the problem and are discussing ways to resolve it. SPIRIT provides IP-XACT, an XML-based metadata specification that describes many aspects of IP. Now, SPIRIT is considering ways in which IP-XACT can be leveraged to describe power.
Gary Delp, SPIRIT technical director, said that a solution to the power modeling issue will have three aspects: a common vocabulary, a data representation, and a set of modeling assumptions that come with the data representation. He noted three possible approaches that could be taken with IP-XACT to help provide consistent power information:
Right now, it’s all still in the discussion phase, but Gary said he’s hoping to have a clearer view of what might be possible by the July Design Automation Conference. The intent is to provide a standard way to convey information, not to enforce a standard methodology.
Gary is also a distinguished engineer at LSI Logic, which has a stake in the discussion. “Power is very important to our customers,” he said. “We want to be able to give an accurate view as early as possible. If we over-estimate power, we’re making it [IP] more expensive. If we under-estimate, it’s even worse.” SPIRIT, he said, is “trying to get a language we can use to convey conclusions from one group to another.”