通常为了event中能够传输一些信息,我们会首先定义一个uvm_object, 然后在object里面定义需要传输的数据的类型;
import uvm_pkg::*;
class cpu_finish_status extends uvm_object;
`uvm_object_utils(cpu_finish_status)
int status;
function new(string name "cpu_finish_status");
super.new(name);
end
endclass
然后在使用uvm_envent, wait_trigger_data:
uvm_event e9002_finish_e;
uvm_object_string_pool #(uvm_event) evt_pool;
cpu_finish_status cpu_finish;
evt_pool = uvm_object_string_pool #(uvm_event)::get_global_pool();
e902_finish_e = evt_pool.get("e902_finish_e");
cpu_finish = cpu_finish_status::type_id::create("cpu_finish");
e902_finish_e.wait_trigger_data(cpu_finish_tmp)
$cast(cpu_finish,cpu_finish_tmp)
具体见上一篇,这样才能编译过,并且实现功能;
但是现在,整个event只需要传递bit[31:0]类型的数据,又不想这么麻烦,还要定义object,然后就想到强制数据类型;
uvm_event#(bit[31:0]) e9002_finish_e;
uvm_object_string_pool #(uvm_event#(bit[31:0])) evt_pool;
evt_pool = uvm_object_string_pool #(uvm_event#(bit[31:0]))::get_gloabal_pool();
但是这样定义编译就会报错
原因是在uvm_event_base中定义了uvm_event_callback,而他需要的参数是uvm_object,而这个地方如果强制将参数定义为bit[31:0],由于参数不匹配,会编译错误;
但是如果使用的是uvm-1.2版本,他提供了一种方法避免定义uvm_event_callbacks相关操作;
//uvm_event.svh
virtual class uvm_event_base extends uvm_object;
const static string type_name = "uvm_event_base";
protected event m_event;
protected int num_waiters;
protected bit on;
protected time trigger_time=0;
`ifndef UVM_EVENT_CALLBACK_FIX
protected uvm_event_callback callbacks[$];
`endif
....
所以只要使用的是uvm-1.2在vcs编译的时候添加编译选项
+define+UVM_EVENT_CALLBACK_FIX
这样强制转换参数后编译就可以成功;