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.
Yes, there was another Embedded Systems Conference this year. Several "multi-year attendees" commented it was smaller. In the middle of it all was a theater where the stage provided easy viewing of various presentations, and a panel on Embedded and EDA markets converging. Executives from Cadence (Mike McNamara), Tensilica, Windriver, Synopsys, and CoWare joined moderator Ron Wilson for an interesting tussle about System Level
Design. These guys know what's going on with System Design - they've
been doing it their entire careers.
For sport I spent my creative energy thinking about how a point made by a particular participant was posited to fit their individual interests rather than those of the industry. While I respect the achievements of every individual on that panel, my predisposition is to be suspect of their motives. Maybe someday I'll write a blog about that competitive analysis process.
There was a very cool floor demo: a robot that would compete with "all comers" in a game of airhockey! Not the most sophisticated, but I found myself entertained evaluating how this thing worked.
The ~45 minute panel discussion was somewhat docile - I have to admit I was hoping for some good arguments. There were several debates, but mostly there were many, many interesting points made. The overall discussion broke down into two main themes: how do we need to look at System Design, and how should we tool for System Design.
One of the important topics mentioned during System Level Design was thenotion that system design has to handle optimizing the system for pre-architected IP (eg - processor cores), sw applications, and the "could be SW, could be HW" stuff in the middle. The panelists pointed at this topic from each of their respective positioned, but never summed it up in this totality. In fairness I know the "ESL industry" has been addressing this for some time. However, there are interesting issues about language to express such systems for analysis, optimization, and design. Those isseus were not debated, though Ron did ask about language.
A related topic that I will blog more on late is IP reuse. As more customers adopt system level design and verification, more IP will be created "at the transaction level". That IP needs to be designed for reuse - a concept that is vaguely defined in the ESL industry today. In fact, going back to the language point, there is actually a lot of disagreement, or misalignment, about TLM IP reuse. As I said, I'll blog more...
And finally, there was a shallow treatment of one of the more vexing questions for the industry. Who is going to become the ESL designer of the future? Our customers are not currently organized such that a natural candidate is obvious. The same issue existed when RTL emerged and become the language of choice. The role of an RTL designer grew from the designer community over time. RTL verification engineering was a role that came along later. Many of these engineers were groomed in college, not transitioned from hand-created digital logic engineers. So a similar question will need to be addressed: will the ESL design and verification engineers be groomed from today's RTL design and verification engineers? From the SW teams? From the architect teams? Or from today's college graduation classes?