{ "id": "epgfa0kvc3", "slug": "hardware-emulation", "title": "Hardware emulation", "updated": "2026-10-21", "topic_path": [ { "id": "technology", "label": "Technology and the built world", "api_url": "https://www.edgepedia.org/api/v1/topics/technology" }, { "id": "technology.computing", "label": "Computing and digital systems", "api_url": "https://www.edgepedia.org/api/v1/topics/technology.computing" }, { "id": "technology.computing.hardware", "label": "Computer hardware", "api_url": "https://www.edgepedia.org/api/v1/topics/technology.computing.hardware" }, { "id": "technology.computing.hardware.hardware-semiconductors", "label": "Semiconductor devices & fabrication", "api_url": "https://www.edgepedia.org/api/v1/topics/technology.computing.hardware.hardware-semiconductors" } ], "geo": [ { "id": "geo.nongeo.t1946.technology.computing", "label": "Non-geographic · 1946 to 2000: Computing and digital systems", "api_url": "https://www.edgepedia.org/api/v1/geo/geo.nongeo.t1946.technology.computing", "path": [ { "id": "geo.nongeo", "label": "Non-geographic", "api_url": "https://www.edgepedia.org/api/v1/geo/geo.nongeo" }, { "id": "geo.nongeo.t1946", "label": "Non-geographic · 1946 to 2000", "api_url": "https://www.edgepedia.org/api/v1/geo/geo.nongeo.t1946" }, { "id": "geo.nongeo.t1946.technology", "label": "Technology and the built world", "api_url": "https://www.edgepedia.org/api/v1/geo/geo.nongeo.t1946.technology" }, { "id": "geo.nongeo.t1946.technology.computing", "label": "Computing and digital systems", "api_url": "https://www.edgepedia.org/api/v1/geo/geo.nongeo.t1946.technology.computing" } ] } ], "excerpt": "Hardware emulation is a pre-silicon chip verification method that maps an RTL design onto programmable hardware, running hundreds of thousands to millions of times faster than simulation.", "snippet": "Hardware emulation is a pre-silicon chip verification method that maps an RTL design onto programmable hardware, running hundreds of thousands to millions of times faster than simulation.", "node": "technology.computing.hardware.hardware-semiconductors", "markdown": "# Hardware emulation\n\nHardware emulation is a pre-silicon verification method that executes a chip or system design, mapped from RTL (register-transfer level: a chip's design description before fabrication) or a gate-level netlist onto programmable hardware, at speeds high enough to run real embedded software before the chip is fabricated. Where HDL simulators execute a design at tens or hundreds of hertz, emulators run at hundreds of kilohertz to megahertz-level speeds, roughly three to six orders of magnitude faster.[1](https://www.rizzatti.com/the-rise-fall-and-rebirth-of-in-circuit-emulation-part-1-of-2/) • [2](https://www.eetimes.com/a-match-made-in-chip-verification-heaven-simulation-and-emulation/) Unlike FPGA prototyping boards, commercial emulators map designs beyond a billion gates and provide extensive signal visibility and configurable tracing, subject to finite capture resources.[3](https://www.electronicdesign.com/technologies/test-measurement/article/21800494/point-counterpoint-hardware-emulations-versatility)\n\n| Key fact | Value |\n|---|---|\n| Execution speed | 600 kHz to 1.5 MHz for processor-based emulation with 1x clocking; up to 4 MHz on Cadence Palladium Z1[4](https://www.design-reuse.com/article/58131-a-primer-on-processor-based-emulation/) • [5](https://www.cadence.com/content/dam/cadence-www/global/en_US/documents/tools/system-design-verification/palladium-z1-ds.pdf) |\n| Design capacity | Up to 9.2 billion ASIC gates (Palladium Z1); over 30 billion gates (ZeBu Server 5, 10 racks), enhanced to scale beyond 60 billion gates[5](https://www.cadence.com/content/dam/cadence-www/global/en_US/documents/tools/system-design-verification/palladium-z1-ds.pdf) • [6](https://www.synopsys.com/content/dam/synopsys/verification/technical-papers/zebu-server5-spec-mar2023.pdf) |\n| Compile speed | Up to 140 million gates per hour on one workstation (Palladium Z1); days to weeks for large FPGA-based flows[5](https://www.cadence.com/content/dam/cadence-www/global/en_US/documents/tools/system-design-verification/palladium-z1-ds.pdf) • [7](https://people.csail.mit.edu/sanchez/papers/2023.ash.micro.pdf) |\n| Speedup over simulation | Over 100,000x for a full-chip Bluegene/Q multi-FPGA emulation versus logic-level software simulation[8](https://dl.acm.org/doi/10.1145/2145694.2145720) |\n| Debug visibility | Emulators generally offer greater internal signal visibility and configurable tracing than FPGA prototypes, but capture resources are finite[3](https://www.electronicdesign.com/technologies/test-measurement/article/21800494/point-counterpoint-hardware-emulations-versatility) |\n| Cost evolution | About $5 per gate with months of setup in 1992 (Quickturn Enterprise) to under 1 cent per gate with under one week of setup in modern systems[9](https://dvcon-proceedings.org/wp-content/uploads/hardware-emulation-ice-vs-virtual-presentation.pdf) |\n\n## How it works\n\nTwo mechanisms dominate. In processor-based emulation, the design database is compiled into instructions for a vast array of tiny Boolean processors. During each time step, every processor can compute any 4-input logic function, taking as inputs the results of any prior calculation by any processor, design inputs, or memory contents.[4](https://www.design-reuse.com/article/58131-a-primer-on-processor-based-emulation/) An emulation cycle schedules all processor steps needed to model the complete design; large designs typically schedule 125 to 320 steps, which with 1x clocking yields 600 kHz to 1.5 MHz.[4](https://www.design-reuse.com/article/58131-a-primer-on-processor-based-emulation/) Because thousands of solvers work concurrently, processing-element speed matters less than concurrency for cycles per second.[10](http://www.deepchip.com/items/0522-02.html)\n\nIn FPGA-based emulation, RTL is synthesized into configurable logic spread across many FPGAs. The Mentor Veloce 2, for example, is built from custom Crystal2 chips carrying a programmable logic array, user memories, virtual-wire logic that transports signals between chips, and debug resources that trace every sequential element.[11](https://indico.cern.ch/event/305730/contributions/703215/attachments/581425/800387/Veloce_Emulator.pdf) Partitioning, clocking and synchronization, and debugging support must preserve cycle accuracy and cycle reproducibility across FPGAs.[8](https://dl.acm.org/doi/10.1145/2145694.2145720)\n\n## How it is done\n\nThe engineer first prepares the design: gated clocks must be converted, because a failure to generate the intended gated clocks forces the tool to use cascaded clocks instead of a clock tree, and technology-library memory instantiations are replaced with FPGA memory primitives or generic memory models.[12](https://blaauw.engin.umich.edu/wp-content/uploads/sites/342/2024/02/FALCON_-An-FPGA-Emulation-Platform-for-Domain-Specific-SoCs-DSSoCs.pdf) Compilation then performs RTL synthesis, partitioning across emulator chips or FPGAs, place-and-route, and resource allocation, producing a platform-specific configuration or execution image; FPGA-based flows produce a bitstream.[11](https://indico.cern.ch/event/305730/contributions/703215/attachments/581425/800387/Veloce_Emulator.pdf) • [13](https://technav.ieee.org/topic/hardware-emulation/) For a large SoC this takes hours or days.[13](https://technav.ieee.org/topic/hardware-emulation/)\n\nThe compiled design is then connected to a stimulus source: a testbench running on a workstation through transactors, a virtual prototype, or physical target hardware. Transaction-based communication, in which the host exchanges transactions rather than individual signal toggles, underlies the SCE-MI interface between host and hardware design-under-test.[14](https://www.eejournal.com/article/20100601-simem/) Debug setup selects which signals to trace before the run, since capture resources are finite.[15](https://arxiv.org/abs/2604.15073)\n\n## Origin\n\nHardware emulation followed the invention of the field-programmable gate array in the second half of the 1980s, with arrays of interconnected FPGAs used to exercise designs before silicon. Dedicated hardware-based verification engines were experimented with, and hardware-assisted verification tools, including emulators and FPGA-based prototypes, were begun.[1](https://www.rizzatti.com/the-rise-fall-and-rebirth-of-in-circuit-emulation-part-1-of-2/)\n\nA processor-based architecture ran inside IBM for internal use only and was never launched commercially; in 1996 IBM OEM'd the technology to Quickturn, and the CoBALT (Concurrent Broadcast Array Logic Technology) emulation system was a custom processor-based compiled-code family.[16](https://www.edn.com/quickturns-new-emulation-family-sets-the-standard-for-verification-performance-and-capacity/) In 1998 Cadence purchased Quickturn and discontinued the FPGA-based approach, citing slow setup and compilation, poor debugging, and execution speed that dropped with design size; Cadence promoted the processor-based architecture as the [Palladium](https://www.edgepedia.org/palladium) family.[17](https://www.edn.com/hardware-emulation-in-mid-life-moving-to-center-stage/) In academic work, RAMP (Research Accelerator for Multiple Processors), a multi-FPGA platform for multiprocessor architecture research, was described by John Wawrzynek and colleagues in IEEE Micro in 2007.[18](https://doi.org/10.1109/mm.2007.39)\n\n## Variants\n\nThe EDA industry has settled on three emulation architectures: processor-based, promoted by Cadence in the Palladium family; custom FPGA-based, championed by Mentor Graphics (now [Siemens EDA](https://www.edgepedia.org/siemens-eda)) in the Veloce family; and standard FPGA-based, adopted by EVE, whose ZeBu name stands for \"zero-bugs\".[3](https://www.electronicdesign.com/technologies/test-measurement/article/21800494/point-counterpoint-hardware-emulations-versatility) • [19](https://www.rizzatti.com/lauro-on-cdns-palladium-xp2-vs-ment-veloce-2-vs-snps-zebu-3/)\n\nUse models include simulation acceleration, in-circuit emulation (ICE) connected to actual hardware, co-emulation testbenches with transactors for protocols such as PCIe and USB, and virtual protocol solutions such as VirtuaLAB.[11](https://indico.cern.ch/event/305730/contributions/703215/attachments/581425/800387/Veloce_Emulator.pdf) In ICE mode the emulator is plugged into a socket on the physical target system in place of a yet-to-be-built chip, exercising the design with live data; ICE suits real traffic and proprietary interfaces, while virtual transactor-based modes suit remote access, deterministic behavior, and what-if analysis.[9](https://dvcon-proceedings.org/wp-content/uploads/hardware-emulation-ice-vs-virtual-presentation.pdf) ICE delivers the highest performance, often 10,000 to 100,000 times faster than a simulator, but requires speed-buffering devices around the emulator.[4](https://www.design-reuse.com/article/58131-a-primer-on-processor-based-emulation/) Hybrid co-emulation couples a virtual platform on the host, such as SystemC/TLM or fast CPU models, with an emulator executing selected RTL blocks at cycle accuracy.[15](https://arxiv.org/abs/2604.15073)\n\n## Applications\n\nEmulation sits late in the design flow, where its long compile times are acceptable because RTL changes are rare; commercial emulators are designed to support very large designs at MHz speeds, while some large FPGA-prototype systems can also validate billion-gate designs.[7](https://people.csail.mit.edu/sanchez/papers/2023.ash.micro.pdf) Once an emulation image is built, it is reused across many hours or days of high-throughput execution, regressions, and large verification campaigns.[15](https://arxiv.org/abs/2604.15073) Embedded-software bring-up is a signature use: one published co-verification effort finished OS development before fabrication and found a fatal DMA bug pre-silicon, with the evaluation board working within one day after the chip returned, and the Ultra Sparc I project was verified before fabrication by booting Solaris test-bench code on an emulator.[20](https://www.cs.york.ac.uk/rts/docs/SIGDA-Compendium-1994-2004/papers/2004/dac04/pdffiles/p299.pdf) [Simulation](https://www.edgepedia.org/simulation) farms of 1,000 PCs can process close to one billion cycles per day but cannot run sequential embedded-software tests, for which emulation is the suitable choice.[2](https://www.eetimes.com/a-match-made-in-chip-verification-heaven-simulation-and-emulation/)\n\n## Limitations and alternatives\n\nBy the numbers, published comparisons of one generation put Palladium-XP2 and Veloce-2 at roughly 1.5 to 2.0 MHz and ZeBu Server 3 at about 5.0 MHz, with compile rates of about 70, 35, and 5 million gates per hour respectively.[19](https://www.rizzatti.com/lauro-on-cdns-palladium-xp2-vs-ment-veloce-2-vs-snps-zebu-3/) No independent benchmark resolves these differences.\n\nFailure modes are well documented. Compiling a large design can take days to weeks because the netlist must be partitioned across emulator chips and each partition placed and routed; one research design on two Alveo U250 FPGAs reached only 1.4 MHz after days of tuning, limited by inter-FPGA latency.[21](https://people.csail.mit.edu/sanchez/papers/2026.lotus.isca.pdf) • [7](https://people.csail.mit.edu/sanchez/papers/2023.ash.micro.pdf) Debug observability carries a steep price: peak performance of several MHz drops to 10 to 100 kHz when debugging is required, and a debug-focused versus performance-focused architecture showed close to a 100x performance difference on the Coremark test.[22](https://dvcon-proceedings.org/wp-content/uploads/TS1D-Architecture-to-tradeoff-Performance-vs-Debug-for-SW-Development-on-Emulation-Platform-paper.pdf) Capturing every internal signal at full speed is infeasible, [trace buffers](https://www.edgepedia.org/trace-buffer) are finite, so signals and triggers must be chosen a priori, and unmonitored bugs force recompilation.[15](https://arxiv.org/abs/2604.15073) Higher-performance ICE likewise implies lower debuggability and needs Speedbridge adapters for peripherals.[22](https://dvcon-proceedings.org/wp-content/uploads/TS1D-Architecture-to-tradeoff-Performance-vs-Debug-for-SW-Development-on-Emulation-Platform-paper.pdf)\n\nAgainst alternatives: RTL simulation tops out around 20 million gates and under 1 cycle per second at that size, while emulation runs 1,000x to 1,000,000x faster with a 2-billion-gate capacity, a 100x capacity advantage.[10](http://www.deepchip.com/items/0522-02.html) [FPGA prototyping](https://www.edgepedia.org/fpga-prototyping) runs faster, 10 to 300 MHz with a free-running asynchronous clock versus emulation's synchronous deterministic clocking, and costs far less, but current-generation capacity varies by platform, with systems such as the HAPS-200 running chip designs with up to 10.8 billion gates at the RTL level, and prototypes lack full visibility and produce prototype-only debug confusion from mapping artifacts.[3](https://www.electronicdesign.com/technologies/test-measurement/article/21800494/point-counterpoint-hardware-emulations-versatility) • [10](http://www.deepchip.com/items/0522-02.html) • [23](https://semiwiki.com/eda/synopsys/372834-unified-emulation-and-prototyping-pipedream-or-reality/)\n\n## References\n\n1. [The Rise, Fall, and Rebirth of In-Circuit Emulation (Part 1 of 2)](https://www.rizzatti.com/the-rise-fall-and-rebirth-of-in-circuit-emulation-part-1-of-2/)\n2. [A Match Made in Chip Verification Heaven: Simulation and Emulation](https://www.eetimes.com/a-match-made-in-chip-verification-heaven-simulation-and-emulation/)\n3. [Point/Counterpoint: Hardware Emulation's Versatility](https://www.electronicdesign.com/technologies/test-measurement/article/21800494/point-counterpoint-hardware-emulations-versatility)\n4. [A primer on processor-based emulation](https://www.design-reuse.com/article/58131-a-primer-on-processor-based-emulation/)\n5. [Cadence Palladium Z1 Enterprise Emulation Platform (datasheet)](https://www.cadence.com/content/dam/cadence-www/global/en_US/documents/tools/system-design-verification/palladium-z1-ds.pdf)\n6. [Synopsys ZeBu Server 5 Spec Sheet (March 2023)](https://www.synopsys.com/content/dam/synopsys/verification/technical-papers/zebu-server5-spec-mar2023.pdf)\n7. [Accelerating RTL Simulation with Hardware-Software Co-Design (ASH, MICRO 2023)](https://people.csail.mit.edu/sanchez/papers/2023.ash.micro.pdf)\n8. [A cycle-accurate, cycle-reproducible multi-FPGA system for accelerating multi-core processor simulation](https://dl.acm.org/doi/10.1145/2145694.2145720)\n9. [Hardware Emulation: ICE vs Virtual User Experiences (DVCon 2016 slides)](https://dvcon-proceedings.org/wp-content/uploads/hardware-emulation-ice-vs-virtual-presentation.pdf)\n10. [The science of SW simulators, acceleration, prototyping, emulation (ESNUG 522)](http://www.deepchip.com/items/0522-02.html)\n11. [The Veloce Emulator and its Use for Verification and System Integration of Complex Multi-node SOC Computing System](https://indico.cern.ch/event/305730/contributions/703215/attachments/581425/800387/Veloce_Emulator.pdf)\n12. [FALCON: An FPGA Emulation Platform for Domain-Specific SoCs (DSSoCs)](https://blaauw.engin.umich.edu/wp-content/uploads/sites/342/2024/02/FALCON_-An-FPGA-Emulation-Platform-for-Domain-Specific-SoCs-DSSoCs.pdf)\n13. [Hardware Emulation | IEEE Technology Navigator](https://technav.ieee.org/topic/hardware-emulation/)\n14. [From Simulation to Emulation](https://www.eejournal.com/article/20100601-simem/)\n15. [Emulation-based System-on-Chip Security Verification: Challenges and Opportunities](https://arxiv.org/abs/2604.15073)\n16. [Quickturn's New Emulation Family Sets the Standard for Verification Performance and Capacity - EDN](https://www.edn.com/quickturns-new-emulation-family-sets-the-standard-for-verification-performance-and-capacity/)\n17. [Hardware Emulation in Mid-Life, Moving to Center Stage - EDN](https://www.edn.com/hardware-emulation-in-mid-life-moving-to-center-stage/)\n18. [John Wawrzynek and colleagues (2007). RAMP: Research Accelerator for Multiple Processors. IEEE Micro.](https://doi.org/10.1109/mm.2007.39)\n19. [Lauro on CDNS Palladium-XP2 vs. MENT Veloce 2 vs. SNPS ZeBu 3](https://www.rizzatti.com/lauro-on-cdns-palladium-xp2-vs-ment-veloce-2-vs-snps-zebu-3/)\n20. [A Fast Hardware/Software Co-Verification Method for System-On-a-Chip by Using a C/C++ Simulator and FPGA Emulator with Shared Register Communication (DAC 2004)](https://www.cs.york.ac.uk/rts/docs/SIGDA-Compendium-1994-2004/papers/2004/dac04/pdffiles/p299.pdf)\n21. [Lotus: A Multi-FPGA Task Dataflow Architecture to Accelerate Cycle-Level Simulation (ISCA 2026)](https://people.csail.mit.edu/sanchez/papers/2026.lotus.isca.pdf)\n22. [Architectures to Tradeoff Performance vs. Debug for Software Development on Emulation Platform](https://dvcon-proceedings.org/wp-content/uploads/TS1D-Architecture-to-tradeoff-Performance-vs-Debug-for-SW-Development-on-Emulation-Platform-paper.pdf)\n23. [Unified Emulation and Prototyping: Pipedream or Reality? (SemiWiki, Synopsys EP-Ready)](https://semiwiki.com/eda/synopsys/372834-unified-emulation-and-prototyping-pipedream-or-reality/)\n\n---\n*Topic: Encyclopedia › Technology and the built world › Computing and digital systems › Computer hardware › Semiconductor devices & fabrication*\n\n*Initially written Sep 29, 2026 · Reviewed: Sep 30, 2026 · Edited: Sep 30, 2026; Oct 21, 2026 · Last review: Sep 30, 2026*\n\n*Copyright 2026 EdgeChat AI, a subsidiary of Biostate AI.*\n\nLicense: Edgepedia Community License 1.0, https://www.edgepedia.org/edgepedia/license\n", "same_as": [], "url": "https://www.edgepedia.org/hardware-emulation", "markdown_url": "https://www.edgepedia.org/hardware-emulation.md", "license": { "name": "Edgepedia Community License 1.0", "url": "https://www.edgepedia.org/edgepedia/license", "summary": "Free with credit, commercial use included. AI training is open to everyone. For other uses, organizations over USD 100M in revenue or 100M monthly users license separately.", "spdx": "LicenseRef-Edgepedia-Community-1.0" }, "credit": "\"Hardware emulation\", Edgepedia (EdgeChat), https://www.edgepedia.org/hardware-emulation. Edgepedia Community License 1.0.", "credit_md": "\"[Hardware emulation](https://www.edgepedia.org/hardware-emulation)\", Edgepedia (EdgeChat), [https://www.edgepedia.org/hardware-emulation](https://www.edgepedia.org/hardware-emulation). [Edgepedia Community License 1.0](https://www.edgepedia.org/edgepedia/license).", "credit_html": "\"Hardware emulation\", Edgepedia (EdgeChat), https://www.edgepedia.org/hardware-emulation. Edgepedia Community License 1.0.", "speakable": "Hardware emulation is a pre-silicon chip verification method that maps an RTL design onto programmable hardware, running hundreds of thousands to millions of times faster than simulation." }