Performance in Hardware Emulators
Emulation performance -- or its speed of execution -- depends on the architecture of the emulation system and the type of deployment.
Continuing my discourse on various aspects of hardware emulators (see also DAC Trip Report: Expanding EDA's Charter & Topical Hardware Emulation), I now wish to discuss one of the most important aspects of hardware emulation: speed of execution.
Emulation performance -- or its speed of execution -- depends on the architecture of the emulation system and the type of deployment. In this first column of a two-part series, I wish to discuss the type of deployment; i.e., how the design under test (DUT) and the test environment communicate with each other, managed by the run-time software. In my next column, I will elaborate on the architecture of emulation systems and how this affects performance.
To read the full article, click here
Related Semiconductor IP
- NoC Interconnect IP Generator
- Over-Voltage Lockout (OVLO) IP
- Verification IP for Universal Chiplet Interconnect Express (UCIe) up to 3.0
- UCIe-S (Gen2) Compatible PHY for Standard Package (x16) in TSMC N3P, North/South Orientation
- DSP-Based 112G SerDes
Related Blogs
- Performance in Hardware Emulators: System Architecture
- Understanding Design Capacity in Hardware Emulators
- Cryptographic Modules Provide Critical Security in a Unified and Isolated Hardware Solution
- Unveiling NOP Insertion Hint: A Performance Optimizer in CXL 3.0
Latest Blogs
- Building the engine behind Arm’s silicon shift
- M31 High-Speed and Long-Channel MIPI C/D-PHY Solution on TSMC N3P/N3C
- Understanding security certification and how analog IP can help
- Embedded Security explained: Secure boot for embedded systems
- World's First Standards-Compliant 112G PHY IP for Linear Optics: A Turning Point for AI Interconnects