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
Device driver software is an essential part of any system-on-chip offering. But who develops and verifies this software, and what tools and methodologies do they use? This is an increasingly vexing question for many design teams - but it's absolutely critical as the industry moves towards application-driven design.
Why are drivers so important? Because they provide the link between a software application and the hardware it runs on, allowing the OS and the application to manage hardware resources. Application developers today don't want to have to know about special features in the hardware. They rely on a hardware abstraction layer that includes drivers to abstract those details away. If the drivers don't present hardware features accurately to the OS and the applications, the applications can't use those features, and all the hard work that goes into differentiating hardware goes nowhere.
Drivers Tacked On Later
So how are software drivers typically developed? The EDA360 vision paper notes that hardware is typically built first and drivers are tacked on later. This leaves two bad choices. One is an expensive, custom driver development effort, typically by a software person with limited hardware knowledge (or a hardware person with limited OS knowledge). The other choice is the procurement of a generic device driver that won't reflect the unique capabilities of the hardware.
For these reasons, the vision paper suggests that device drivers be provided as part of an IP "stack" (right) that also includes design IP, verification IP, and design constraints. Optimally, the drivers are specified and designed in tandem with the rest of the IP stack. This eases IP integration, avoids redundant driver development efforts, and makes it easier for the OS to directly control hardware resources such as memory bandwidth to meet the needs of the application.
Verifying Device Drivers
Who verifies the drivers, and how, is another tough question. Techniques such as metric-driven verification (MDV), coverage metrics, and constrained-random test sequence generation are widely used in hardware verification, but are virtually unknown in the software world. However, these techniques would be extremely helpful in tracking down tough bugs that may have their origins in the interface between hardware and software.
A newly-published Cadence technical paper suggests a new approach. It shows how Incisive Software Extensions can extend the Cadence Incisive simulation environment for driver verification and debugging, bringing techniques such as MDV and random sequence generation into the software domain. One result is a unified hardware/software debugging environment that can be used by both hardware and software engineers.
The real point of this post, however, is that software device driver development and verification should no longer be thought of something that is "outside EDA." It is very much a part of silicon design. In fact, if it's not done well, all those neat features you put in silicon won't matter much at all.