English
Bluetooth low energy v6.0 Baseband Controller, Protocol Software Stack and Profiles IP
PCI Express verification underscores need to plan
Levent Caglar, Cadence Design Systems Inc.
(11/07/2005 10:00 AM EST)
EE Times
PCI Express-based designs are textbook examples of a complex verification problem. Using a compliance checklist can kick-start verification planning. But you also need a well-planned verification methodology that addresses these questions: What compliance items are verified? Have you covered all compliance scenarios? Can you provide a progress report to your manager?
These challenges are not new for verification engineers. But complex verification projects force the extended team to do more planning, to avoid getting lost in the 1,300+ item compliance checklist.
An extensive checklist can serve as a compliance verification plan to identify how to co-relate compliance items to the data automatically provided by the verification environment. This involves mapping English definitions to a mechanism. Often, we underestimate the workload and get confused between checking a single scenario and proving that a specific feature works in all scenarios.
(11/07/2005 10:00 AM EST)
EE Times
PCI Express-based designs are textbook examples of a complex verification problem. Using a compliance checklist can kick-start verification planning. But you also need a well-planned verification methodology that addresses these questions: What compliance items are verified? Have you covered all compliance scenarios? Can you provide a progress report to your manager?
These challenges are not new for verification engineers. But complex verification projects force the extended team to do more planning, to avoid getting lost in the 1,300+ item compliance checklist.
An extensive checklist can serve as a compliance verification plan to identify how to co-relate compliance items to the data automatically provided by the verification environment. This involves mapping English definitions to a mechanism. Often, we underestimate the workload and get confused between checking a single scenario and proving that a specific feature works in all scenarios.
|
E-mail This Article | 
|
|
Printer-Friendly Page |
Related Articles
- Learning Not to Fear PCI Express Compliance Using a Predictable, Metrics Based Verification Closure Methodology
- SoC technology underscores need for verification
- Attacking the Verification Challenge: Applying Next Generation Verification IP to PCI Express-based Design (by N. Mullinger, J. Hopkins & R. Hill from Synopsys)
- PCI Express 3.0 needs reliable timing design
- PCI Express 3.0 needs reliable timing design
New Articles
- Accelerating RISC-V development with Tessent UltraSight-V
- Automotive Ethernet Security Using MACsec
- What is JESD204C? A quick glance at the standard
- Optimizing Power Efficiency in SOC with PVT Sensor-Assisted DVFS Technology
- Bandgap Reference (BGR) Circuit Design and Transient Analysis in 90nm VLSI Technology
Most Popular
- Accelerating RISC-V development with Tessent UltraSight-V
- System Verilog Assertions Simplified
- Synthesis Methodology & Netlist Qualification
- System Verilog Macro: A Powerful Feature for Design Verification Projects
- Enhancing VLSI Design Efficiency: Tackling Congestion and Shorts with Practical Approaches and PnR Tool (ICC2)