# New UVVM functionality: Detection of unexpected interface activity

**URL:** <https://forum.uvvm.org/t/new-uvvm-functionality-detection-of-unexpected-interface-activity/442>\
**Category:** Announcements\
**Created:** [May 29, 2024, 4:50pm UTC](https://forum.uvvm.org/t/new-uvvm-functionality-detection-of-unexpected-interface-activity/442 "2024-05-29T16:50:10Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![UVVM\_Team](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.uvvm.org/uvvm_team/32/102_2.png) [@UVVM\_Team](https://forum.uvvm.org/u/UVVM_Team)\
**Post date:** [May 29, 2024, 4:50pm UTC](https://forum.uvvm.org/t/new-uvvm-functionality-detection-of-unexpected-interface-activity/442/1 "2024-05-29T16:50:10Z")

</div>

One of the first improvements to come out of the new ESA UVVM project is detection of **unexpected** activity on a DUT interface. UVVM has provided open source BFMs (Bus Functional Models) and VVCs (VHDL Verification Components) for lots of interfaces - like AXI, AXI-stream, AXI-light, SPI, UART, SBI, Ethernet, GMII, GPIO, Avalon MM, Avalon stream, etc. - for a long time. These have provided excellent access mechanisms for transaction modelling, but also various support for protocol checking. Normal BFMs and VVCs have the limitation though, that they only initiate a transaction or wait for one to occurr. They do not check whether the DUT is only transmitting data when expected.

UVVM now introduces detection of any **unwanted or unexpected** transactions from the DUT. In fact, UVVM will now detect any **unwanted or unexpected** activity on a given interface. This new checker may of course be turned on and off from the test sequencer.

We expect this new functionality to be published in June.