Avoiding Redundant Simulation Cycles for your UVM VIP with a Simple Save-Restore Strategy
January 6, 2015
In many verification environments, we reuse the same configuration cycles across different testcases. These cycles may involve writing and reading from different configuration and status registers, loading program memories, and other similar tasks to set up a DUT for its targeted stimulus. In many such environments, the time taken during these configuration cycles is very long. Also, there is a lot of redundancy as verification engineers have to run the same set of verified configuration cycles for different testcases leading to a loss in productivity. This is especially true for complex verification environments with multiple interfaces which require different components to be configured.
To read the full article, click here
Related Semiconductor IP
- SMC 2nm 1V8 ESD Power Clamp – Low Leakage
- TSMC 2nm 1V8 ESD Local Clamp – Low Leakage
- Zigbee Transceiver PHY
- Data Flow Architecture IP
- AMBA SPI Controller MRAM Controller
Related Blogs
- Analog Bits Steals the Show with Working IP on TSMC 3nm and 2nm and a New Design Strategy
- Upgrade the Raspberry Pi for AI with a Neuromorphic Processor
- How fast a GPU do you need for your user interface?
- Maximizing the Usability of Your Chip Development: Design with Flexibility for the Future
Latest Blogs
- Introducing SKL: The SiFive Kernel Library
- IDS-NoC: A Scalable Interconnect Solution for Modern SoC Design
- Leading-edge AI IC designs demand comprehensive HAV methodologies
- Beyond the Fab: Building Europe’s Next Generation of Semiconductor Champions
- AI Semiconductor Design at 3nm and 2nm: Silicon-Proven IP