USB4 Gen3X2 and DP1.4 X4 PHY IP with Type-C connector support
The best of both worlds: Optimizing OCP slave memory behavior
By Neill Mullinger, Synopsys, Inc. EDA DesignLine
(11/09/2009 0:56 AM EST)
Verification IP for OCP is generally used to achieve one of two main verification objectives; at the module level to test OCP components and their interfaces; or at the bus fabric level when some or all of the components may be replaced by the verification IP to test the behavior of a system. In either case, the VIP behavior used in verification will ultimately be replaced with a real component or interface, and so it is important that the verification IP can represent the behavior of the real component or components; even better to represent a spread of components that might be used in conjunction with the design being tested. The real slave components in an OCP design will have memory of one form or another and so accurately modeling the behavior of the memory in the verification IP can be critical to understanding system performance and identifying potential hazards.
E-mail This Article | Printer-Friendly Page |
|
Related Articles
- Optimizing flash memory selection for automotive & other uses
- Optimizing data memory utilization
- Optimizing embedded software for power efficiency: Part 3 - Optimizing data flow and memory
- Optimizing High Performance CPUs, GPUs and DSPs? Use logic and memory IP - Part II
- Optimizing high-performance CPUs, GPUs and DSPs? Use logic and memory IP - Part I
New Articles
- The Rise of RISC-V and ISO 26262 Compliance
- Synopsys 3DIO Solution for Multi-Die Integration (2.5D/3D)
- SoC NoCs: Homegrown or Commercial Off-the-Shelf?
- From a Lossless (~1.5:1) Compression Algorithm for Llama2 7B Weights to Variable Precision, Variable Range, Compressed Numeric Data Types for CNNs and LLMs