# UVM Driver to Monitor communication in a single agent

**URL:** <https://verificationacademy.com/forums/t/uvm-driver-to-monitor-communication-in-a-single-agent/32306>\
**Category:** UVM\
**Tags:** Constraint-SystemVerilog, abstract-driver, UVM, I2C-protocol, abstract-monitor, uvm\_set\_severity\
**Created:** [September 26, 2016, 3:53am UTC](https://verificationacademy.com/forums/t/uvm-driver-to-monitor-communication-in-a-single-agent/32306 "2016-09-26T03:53:35Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![mayurkubavat](https://verificationacademy.com/forums/letter_avatar_proxy/v4/letter/m/a9a28c/32.png) [@mayurkubavat](https://verificationacademy.com/forums/u/mayurkubavat)\
**Post date:** [September 26, 2016, 6:29am UTC](https://verificationacademy.com/forums/t/uvm-driver-to-monitor-communication-in-a-single-agent/32306/2 "2016-09-26T06:29:49Z")

</div>

_In reply to [MLearner](https://verificationacademy.com/forums/t/uvm-driver-to-monitor-communication-in-a-single-agent/32306):_

You should avoid driver-monitor communication as you can reuse your monitor when driving is not required. For e.g. as intermediate monitor/checker at integration level.

You can receive read data by observing SCL interface along with SDA. Go through I2C write and read waveforms once and see if you can come up with monitoring by observing only SCL, SDA and no driver!

---

_[View the full topic](https://verificationacademy.com/forums/t/uvm-driver-to-monitor-communication-in-a-single-agent/32306)._
