English
Unified Verification for Hardware and Embedded Software Developers
By Lauro Rizzatti, EVE-USA
edadesignline.com (November 25, 2008)
Moore's Law continues to drive chip complexity and performance to new highs, while stressing and periodically "breaking" existing design flows. Fortunately for consumers of electronic design automation (EDA) tools, the same shrinking geometries that make their design problems tougher are also helping to improve the performance of these tools.
But when it comes to functional verification, traditionally the largest bottleneck in the design process, software-based approaches, such as hardware description language (HDL) simulation, continue to lose ground. HDL simulation speeds aren't keeping pace with device complexity because many new devices -- 3G cell phones, internet routers and image processors, for example -- require massive verification sequences that would take many years to simulate on even the fastest PC. These sequences are often a result of the need to run long, contiguous, serial protocol streams or complex embedded software to fully verify a new system on chip (SoC) or system design.
Increasingly, embedded software is overtaking the hardware content of SoC devices. The net result is a causality dilemma: which comes first -- the "final" hardware or the "final" software?
In recent years, a new breed of tools, collectively called virtual prototyping platforms based on a high-level of design abstraction, have been introduced in an attempt to start software validation well ahead of silicon availability. While some may have achieved the scope of jump-starting software development, they only address application programs that do not require an accurate representation of the underling hardware design. They fall short when testing the interaction of the embedded software with hardware, such as firmware, device drivers, operating systems and diagnostics. For this testing, embedded software developers need an accurate model of the hardware to validate their code, while hardware designers need fairly complete software to fully validate their application specific integrated circuit (ASIC) or SoC.
edadesignline.com (November 25, 2008)
Moore's Law continues to drive chip complexity and performance to new highs, while stressing and periodically "breaking" existing design flows. Fortunately for consumers of electronic design automation (EDA) tools, the same shrinking geometries that make their design problems tougher are also helping to improve the performance of these tools.
But when it comes to functional verification, traditionally the largest bottleneck in the design process, software-based approaches, such as hardware description language (HDL) simulation, continue to lose ground. HDL simulation speeds aren't keeping pace with device complexity because many new devices -- 3G cell phones, internet routers and image processors, for example -- require massive verification sequences that would take many years to simulate on even the fastest PC. These sequences are often a result of the need to run long, contiguous, serial protocol streams or complex embedded software to fully verify a new system on chip (SoC) or system design.
Increasingly, embedded software is overtaking the hardware content of SoC devices. The net result is a causality dilemma: which comes first -- the "final" hardware or the "final" software?
In recent years, a new breed of tools, collectively called virtual prototyping platforms based on a high-level of design abstraction, have been introduced in an attempt to start software validation well ahead of silicon availability. While some may have achieved the scope of jump-starting software development, they only address application programs that do not require an accurate representation of the underling hardware design. They fall short when testing the interaction of the embedded software with hardware, such as firmware, device drivers, operating systems and diagnostics. For this testing, embedded software developers need an accurate model of the hardware to validate their code, while hardware designers need fairly complete software to fully validate their application specific integrated circuit (ASIC) or SoC.
|
E-mail This Article | 
|
|
Printer-Friendly Page |
|
||||||
Related Articles
- Using unified modeling methods to reduce embedded hardware/software development
- Will Generative AI Help or Harm Embedded Software Developers?
- Processor-In-Loop Simulation: Embedded Software Verification & Validation In Model Based Development
- Optimizing embedded software for power efficiency: Part 2 - Minimizing hardware power
- An introduction to offloading CPUs to FPGAs - Hardware programming for software developers