简体繁体 English

Specman e UVM：为什么要继承uvm_ *单位？

[英]Specman e UVM: Why to inherit from uvm_* units?

原文 2018-03-25 09:06:30 3 1 uvm/ specman/ e

I'm implementing a verification environment according to e UVM user guide . 我正在根据e UVM user guide实现验证环境。

My question is - why should my_monitor unit to inherit from uvm_monitor (same for other UVM components)? 我的问题是-为什么my_monitor单元要从uvm_monitor继承（与其他UVM组件相同）？

What exactly logic do every uvm_* have? 每个uvm_*到底具有什么逻辑？ Can I implement UVM environment without inheriting from uvm_* units? 是否可以在不继承uvm_*单元的情况下实现UVM环境？

Thank you for your help 谢谢您的帮助

1 个解决方案

First - yes, since 99% of the advanced capabilities are part of Specman and not in a library, you can implement UVM environment without loading the UVM-e. 首先-是的，由于99％的高级功能是Specman的一部分，而不是在库中，因此您可以在不加载UVM-e的情况下实现UVM环境。

The UVM-e contains VR_AD, Testflow, Scoreboard, Low Power, Unit testing, UVM-debug-window. UVM-e包含VR_AD，Testflow，记分板，低功耗，单元测试，UVM调试窗口。 If you do not care to use any of these - no need to import UVM-e. 如果您不愿意使用其中任何一个，则无需导入UVM-e。

About the UVM base types - there is a no big reason to use them. 关于UVM基本类型-没有太大的理由使用它们。 The main reason is for other tools to be able to parse the environment and recognize that a specific unit is like a UVM base type. 主要原因是其他工具能够解析环境并识别特定单位类似于UVM基本类型。 A linter is an example of an advance tool that can care about things like this (and then report that "you have a monitor without a port" and things like that). linter是高级工具的一个示例，该工具可以处理此类事情（然后报告“您有没有端口的监视器”之类的事情）。