Power verification: trust but verify, or verify and trust?
EE Times (07/13/2009 12:00 AM EDT)
The issue of verification has never been larger. Today, functional verification is at least as big a task as design and, in many cases, much larger. This has been the case for awhile now and the situation doesn't appear to be changing any time soon. If anything, verification is becoming an even larger and more difficult task.
It isn't hard to see why. More transistors and larger die sizes result in greater complexity. It is common today to see single chips with multiple CPUs and multiple memory systems, a DSP, and various interfaces such as USB, 802.11, and Bluetooth not to mention a healthy smattering of analog functions. And don't forget power management.
Accompanying all of the increased complexity is increased power consumption although, thanks to designer creativity, power consumption has not increased as rapidly as functional complexity. Various types of power reduction techniques have been employed to keep power concerns from derailing functional aspirations. After all, what good is a shiny new phone with video capabilities if the battery life is measured in minutes instead of hours or days?
![]() |
E-mail This Article | ![]() |
![]() |
Printer-Friendly Page |
|
Related Articles
New Articles
- What tamper detection IP brings to SoC designs
- RISC-V in 2025: Progress, Challenges,and What's Next for Automotive & OpenHardware
- Understanding MACsec and Its Integration
- Discover new Tessent UltraSight-V from Siemens EDA, and accelerate your RISC-V development.
- The Critical Factors of a High-performance Audio Codec - What Chip Designers Need to Know
Most Popular
- System Verilog Assertions Simplified
- Design Rule Checks (DRC) - A Practical View for 28nm Technology
- System Verilog Macro: A Powerful Feature for Design Verification Projects
- A Heuristic Approach to Fix Design Rule Check (DRC) Violations in ASIC Designs @7nm FinFET Technology
- Synthesis Methodology & Netlist Qualification