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
I went to New York City last weekend and went to see a
Broadway show called Avenue Q. It's a
very adult adaption of Sesame
Street (sort of). Before you grab a bus, plane, or train to NYC
to see this show with your kids, be forewarned. Puppets aside, this is NOT a show for
children. And while that has absolutely
nothing to do with chip design, it made me think of my favorite frog from my childhood
who said "It's not that easy being green".
As chip designers, we all know how hard
it is to build a green chip. First,
there all the implications to implementing a low power design. Decisions about multi-supply voltage, power
shutoff, power aware test, etc, etc, etc. And never mind all the implications on the
design flow. I'll leave the details to
that to another blog and probably another blogger. Let's assume that you've made all the
appropriate decisions up front and have all the right tools and methodologies
in place to handle the details. OK, so
why then do so many chips end up not meeting their power budget at the end of
the project? Or worse yet, how many
projects have required respins in order to finally meet the power budget?
I believe that a lot of the
problems can be attributed to the fact that most companies don't do a good
enough job in tracking their metrics thoughout the design process. Somebody in marketing or senior engineering
management comes up with some kind of estimate of the power consumption,
usually on some mega-spreadsheet that's been handed down from generation to
generation along with secret handshakes, solemn incantations and a few martinis.
Everybody agrees that **when** that power budget is met, the project will have
a place in the market and customer will beat down their doors to buy millions
of parts. This specification is then
sent down to the engineering team to implement.
This is where the problems start. The engineering team starts working on
actually creating this monster and at some point starts to get some feedback on
the actual power consumption. Given that performance and area are most likely
higher priorities this feedback is likely to get ignored. Fast forward another 6 months. The design is in the final stages of layout. Some poor engineer gets the job of taking a
bunch of vectors from simulation, a bunch of parasitic data, and looks at the
final power numbers. Guess what, the
power budget has been blown out the window. And at this point it's probably too late to do
anything about it.
So back to my original question. When do green chips turn brown? The reality is that they probably start
turning brown very early in the design flow, but nobody bothers to look back at
the original assumptions and validates them as the design becomes more real.
They wait until way too late in the process to see what affect all the real
implementation details are having on the initial power budget. If we simply look at the metrics on a regular
basis, and revalidated and/or changed our assumptions, we might actually have
the time to go back and possibly make changes to our design to get things back
I'm not going to go into a long
winded sales pitch in this blog, but I do want those of you reading to know
that there is hope, and all you have to do is go to chipestimate.com and look around. I'm pretty excited about this tool as I see it
as way to keep things in synch between the people that come up with the
original idea for a chip and us poor slobs that have to make that idea a
reality. Take a look, you can even
download a free version. Let me know
what you think. And show it to your
architects, marketing guys, etc. I think they'll eyes will light up just like