# AXI4 driver for read and write functionaluty

**URL:** <https://verificationacademy.com/forums/t/axi4-driver-for-read-and-write-functionaluty/32184>\
**Category:** UVM\
**Tags:** UVM, axi-driver\
**Created:** [August 23, 2016, 6:09am UTC](https://verificationacademy.com/forums/t/axi4-driver-for-read-and-write-functionaluty/32184 "2016-08-23T06:09:52Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![cgales](https://verificationacademy.com/forums/letter_avatar_proxy/v4/letter/c/ccd318/32.png) [@cgales](https://verificationacademy.com/forums/u/cgales)\
**Post date:** [August 23, 2016, 12:37pm UTC](https://verificationacademy.com/forums/t/axi4-driver-for-read-and-write-functionaluty/32184/2 "2016-08-23T12:37:46Z")

</div>

_In reply to [saritr](https://verificationacademy.com/forums/t/axi4-driver-for-read-and-write-functionaluty/32184):_

If you need an AXI4 UVC to verify a production quality IP block, I highly recommend that you use a commercially available UVC from an EDA vendor. If you are not familiar with the the AXI4 protocol, the complexity involved will require multiple man-months of work to develop an accurate model.

However, if you are developing this for a personal project, grab the AXI4 spec from ARM, read it, and implement your own UVC.

---

_[View the full topic](https://verificationacademy.com/forums/t/axi4-driver-for-read-and-write-functionaluty/32184)._