Simplifying the Usage of UVM Register Model
January 6, 2015
When I began using UVM RAL, I could not understand what the UVM base class library had to say about updating the values of desired value and mirror value registers. I also felt that the terms used do not reflect the intent precisely. After spending some time, I came up with a table which helped me to understand the behavior of register model APIs, and how best they can be called.
Before I introduce the table, let us take a look at the process of creating the register model:
- Creating the register format specification
- Converting the specification into UVM register model
- Using the register model
To read the full article, click here
Related Semiconductor IP
- LPDDR6/5X/5 PHY V2 - Intel 18A-P
- ML-KEM Key Encapsulation & ML-DSA Digital Signature Engine
- MIPI SoundWire I3S Peripheral IP
- ML-DSA Digital Signature Engine
- P1619 / 802.1ae (MACSec) GCM/XTS/CBC-AES Core
Related Blogs
- Announcing the launch of CHERI Alliance: A unified front against digital threats
- Say Goodbye to Limits and Hello to Freedom of Scalability in the MIPS P8700
- The Future of Technology: Transforming Industrial IoT with Edge AI and AR
- The Future of Technology: Generative AI in China
Latest Blogs
- PCIe Low-Power Validation Challenges and Potential Solutions (PIPE/L1 Substates)
- Rethinking Edge AI Interconnects: Why Multi-Protocol Is the New Standard
- Tidying Up: FIPS-Compliant Secure Zeroization for OTP
- Accelerating Your Development: Simplify SoC I/O with a Single Multi-Protocol SerDes IP
- Why What Where DIFI and the new version 1.3