PCI Express verification underscores need to plan
(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.
To read the full article, click here
Related Semiconductor IP
- Flexible Pixel Processor Video IP
- Bluetooth Low Energy 6.0 Digital IP
- Verification IP for Ultra Ethernet (UEC)
- MIPI SWI3S Manager Core IP
- Ultra-low power high dynamic range image sensor
Related White Papers
- PCI Express 3.0 needs reliable timing design
- PCI Express 3.0 needs reliable timing design
- Automotive Design Needs Efficient Verification to Survive
- How HyperTransport and PCI Express complement each other
Latest White Papers
- Security Enclave Architecture for Heterogeneous Security Primitives for Supply-Chain Attacks
- relOBI: A Reliable Low-latency Interconnect for Tightly-Coupled On-chip Communication
- Enabling Space-Grade AI/ML with RISC-V: A Fully European Stack for Autonomous Missions
- CANDoSA: A Hardware Performance Counter-Based Intrusion Detection System for DoS Attacks on Automotive CAN bus
- How Next-Gen Chips Are Unlocking RISC-V’s Customization Advantage