What Does it Take to Migrate from e to UVMe?
So you are developing your verification environment in e, and like everyone else, you've been hearing a lot of buzz surrounding UVM (Universal Verification Methodology). Maybe you would also like to give it a try. The first question that pops in your mind is, "What would it take to migrate from e to UVM e?"
Well, this is a bit of a trick question. The short answer is that if you've adopted eRM in the past, migration to UVM e will only take a few minutes. If your environment is not eRM-compliant, it will take you longer.
And now to the details. What exactly is UVM e, in comparison to native e (IEEE 1647), and to eRM? What is in UVM? And what's all the fuss about?
To read the full article, click here
Related Semiconductor IP
- UALink 200G v1.0 Verification IP
- CCSDS SCCC Demapper and Turbo Decoder
- NPU IP
- JPEG XL Encoder
- I2C Master/Slave Controller Core
Related Blogs
- From GPUs to Memory Pools: Why AI Needs Compute Express Link (CXL)
- From AI-Assisted EDA to AI-Mediated Engineering
- From Bug Hunting to Engineering Methodology: Lessons from AI-Driven Development
- Rambus CXL IP: A Journey from Spec to Compliance