从零搭建一个可复用的UVM验证环境：以APB总线为例的保姆级步骤拆解

从零搭建一个可复用的UVM验证环境以APB总线为例的保姆级步骤拆解在芯片验证领域UVMUniversal Verification Methodology已经成为事实上的行业标准。但对于刚接触UVM的工程师来说从理论到实践的跨越往往令人望而生畏。本文将以APB总线为例带你一步步搭建一个可复用的验证环境重点解决怎么做而非是什么的问题。APBAdvanced Peripheral Bus作为ARM AMBA协议家族中的一员因其简单可靠的特性广泛应用于低带宽外设连接。我们将从最基础的transaction定义开始逐步构建完整的验证环境特别强调模块化和可复用性设计让你不仅能完成当前项目还能快速适配其他总线协议。1. 搭建基础框架从APB transaction开始任何UVM验证环境的起点都是transaction——它是验证组件间传递的最小数据单元。对于APB总线我们需要准确模拟其协议特性。1.1 定义APB transaction类APB协议的核心信号包括PADDR地址、PWDATA写数据、PRDATA读数据、PWRITE读写控制等。我们需要在transaction中封装这些字段class apb_transaction extends uvm_sequence_item; rand bit [31:0] paddr; rand bit pwrite; rand bit [31:0] pwdata; bit [31:0] prdata; rand int delay; // 约束条件 constraint addr_c { paddr inside {[0:32hFFFF_FFFF]}; } constraint delay_c { delay inside {[0:5]}; } uvm_object_utils_begin(apb_transaction) uvm_field_int(paddr, UVM_ALL_ON) uvm_field_int(pwrite, UVM_ALL_ON) uvm_field_int(pwdata, UVM_ALL_ON) uvm_field_int(prdata, UVM_ALL_ON) uvm_field_int(delay, UVM_ALL_ON) uvm_object_utils_end function new(string name apb_transaction); super.new(name); endfunction endclass这里有几个关键设计点使用rand修饰符让字段可随机化便于生成多样化的测试场景添加合理的约束条件constraint确保生成的值符合协议要求通过uvm_field_*宏注册字段自动实现copy、compare、print等常用功能1.2 配置APB接口在搭建driver和monitor前需要先定义与DUT连接的物理接口interface apb_if(input bit pclk, input bit presetn); logic [31:0] paddr; logic psel; logic penable; logic pwrite; logic [31:0] pwdata; logic [31:0] prdata; logic pready; logic pslverr; clocking driver_cb (posedge pclk); output paddr, psel, penable, pwrite, pwdata; input prdata, pready, pslverr; endclocking clocking monitor_cb (posedge pclk); input paddr, psel, penable, pwrite, pwdata, prdata, pready, pslverr; endclocking endinterface接口设计中明确定义时钟块clocking block区分driver和monitor的视角包含所有APB协议必需信号通过clocking block的时序控制简化信号同步2. 实现核心组件driver与monitor2.1 APB driver的实现driver负责将transaction转换为实际的接口信号。APB协议采用两阶段传输PSEL-PENABLEdriver需要准确模拟这一时序class apb_driver extends uvm_driver #(apb_transaction); uvm_component_utils(apb_driver) virtual apb_if vif; function new(string name, uvm_component parent); super.new(name, parent); endfunction virtual task run_phase(uvm_phase phase); forever begin seq_item_port.get_next_item(req); drive_transfer(req); seq_item_port.item_done(); end endtask virtual task drive_transfer(apb_transaction trans); // 第一阶段设置地址和控制信号 (vif.driver_cb); vif.driver_cb.psel 1b1; vif.driver_cb.pwrite trans.pwrite; vif.driver_cb.paddr trans.paddr; if(trans.pwrite) vif.driver_cb.pwdata trans.pwdata; // 第二阶段使能传输 (vif.driver_cb); vif.driver_cb.penable 1b1; // 等待传输完成 while(!vif.driver_cb.pready) (vif.driver_cb); // 采样读数据 if(!trans.pwrite) trans.prdata vif.driver_cb.prdata; // 结束传输 (vif.driver_cb); vif.driver_cb.psel 1b0; vif.driver_cb.penable 1b0; // 协议要求的空闲周期 repeat(trans.delay) (vif.driver_cb); endtask endclass关键实现细节严格遵循APB协议的两阶段传输时序正确处理读写操作的不同数据流向支持可配置的传输间隔delay使用clocking block确保信号同步2.2 APB monitor的实现monitor负责观察总线活动并将信号转换回transactionclass apb_monitor extends uvm_monitor; uvm_component_utils(apb_monitor) virtual apb_if vif; uvm_analysis_port #(apb_transaction) ap; function new(string name, uvm_component parent); super.new(name, parent); ap new(ap, this); endfunction virtual task run_phase(uvm_phase phase); forever begin apb_transaction trans; monitor_transfer(trans); ap.write(trans); end endtask virtual task monitor_transfer(output apb_transaction trans); trans apb_transaction::type_id::create(trans); // 等待传输开始 (vif.monitor_cb iff vif.monitor_cb.psel !vif.monitor_cb.penable); // 捕获第一阶段信息 trans.paddr vif.monitor_cb.paddr; trans.pwrite vif.monitor_cb.pwrite; if(trans.pwrite) trans.pwdata vif.monitor_cb.pwdata; // 等待第二阶段 (vif.monitor_cb iff vif.monitor_cb.penable); // 捕获完成状态 while(!vif.monitor_cb.pready) (vif.monitor_cb); if(!trans.pwrite) trans.prdata vif.monitor_cb.prdata; endtask endclassmonitor设计要点使用analysis port广播捕获到的transaction准确识别APB协议的两阶段转换点保持与driver相同的时序理解确保数据一致性3. 构建可复用的APB agentagent是UVM中的关键复用单元它将driver、monitor和sequencer封装为一个整体class apb_agent extends uvm_agent; uvm_component_utils(apb_agent) apb_driver driver; apb_monitor monitor; uvm_sequencer #(apb_transaction) sequencer; virtual apb_if vif; function new(string name, uvm_component parent); super.new(name, parent); endfunction virtual function void build_phase(uvm_phase phase); super.build_phase(phase); monitor apb_monitor::type_id::create(monitor, this); if(get_is_active() UVM_ACTIVE) begin driver apb_driver::type_id::create(driver, this); sequencer uvm_sequencer#(apb_transaction)::type_id::create(sequencer, this); end if(!uvm_config_db#(virtual apb_if)::get(this, , vif, vif)) uvm_fatal(NOVIF, Virtual interface not set) monitor.vif vif; if(get_is_active() UVM_ACTIVE) driver.vif vif; endfunction virtual function void connect_phase(uvm_phase phase); if(get_is_active() UVM_ACTIVE) driver.seq_item_port.connect(sequencer.seq_item_export); endfunction endclass这个agent设计体现了几个重要复用特性支持UVM_ACTIVE和UVM_PASSIVE两种模式通过config_db获取虚拟接口避免硬编码自动连接driver-sequencer的TLM端口可独立配置和复用提示通过参数化agent类可以进一步通用化使其支持不同类型的总线协议。例如使用uvm_parameterized_agent模板。4. 集成完整验证环境4.1 构建scoreboard和reference modelscoreboard负责验证DUT行为的正确性。对于APB总线我们通常需要class apb_scoreboard extends uvm_scoreboard; uvm_component_utils(apb_scoreboard) uvm_analysis_imp #(apb_transaction, apb_scoreboard) mon_imp; uvm_analysis_imp #(apb_transaction, apb_scoreboard) dut_imp; apb_transaction ref_queue[$]; int match_count, mismatch_count; function new(string name, uvm_component parent); super.new(name, parent); mon_imp new(mon_imp, this); dut_imp new(dut_imp, this); endfunction virtual function void write_mon(apb_transaction trans); ref_queue.push_back(trans); endfunction virtual function void write_dut(apb_transaction trans); apb_transaction ref_trans; if(ref_queue.size() 0) begin uvm_error(SCBD, Unexpected transaction from DUT) mismatch_count; return; end ref_trans ref_queue.pop_front(); if(!trans.compare(ref_trans)) begin uvm_error(SCBD, $sformatf(Mismatch!\nExpected: %s\nActual: %s, ref_trans.sprint(), trans.sprint())) mismatch_count; end else begin uvm_info(SCBD, Transaction matched, UVM_MEDIUM) match_count; end endfunction virtual function void report_phase(uvm_phase phase); uvm_info(SCBD, $sformatf(Match/Mismatch: %0d/%0d, match_count, mismatch_count), UVM_LOW) endfunction endclassreference model根据具体功能实现简单的APB模型可能只是将写操作存入内存读操作返回相应数据class apb_model extends uvm_component; uvm_component_utils(apb_model) uvm_blocking_get_port #(apb_transaction) in_port; uvm_analysis_port #(apb_transaction) out_port; bit [31:0] mem[bit [31:0]]; function new(string name, uvm_component parent); super.new(name, parent); in_port new(in_port, this); out_port new(out_port, this); endfunction virtual task run_phase(uvm_phase phase); forever begin apb_transaction trans; in_port.get(trans); if(trans.pwrite) mem[trans.paddr] trans.pwdata; else trans.prdata mem.exists(trans.paddr) ? mem[trans.paddr] : 32hDEADBEEF; out_port.write(trans); end endtask endclass4.2 集成environment将所有组件集成到统一环境中class apb_env extends uvm_env; uvm_component_utils(apb_env) apb_agent agent; apb_model model; apb_scoreboard scoreboard; function new(string name, uvm_component parent); super.new(name, parent); endfunction virtual function void build_phase(uvm_phase phase); super.build_phase(phase); agent apb_agent::type_id::create(agent, this); model apb_model::type_id::create(model, this); scoreboard apb_scoreboard::type_id::create(scoreboard, this); endfunction virtual function void connect_phase(uvm_phase phase); agent.monitor.ap.connect(scoreboard.mon_imp); agent.monitor.ap.connect(model.in_port); model.out_port.connect(scoreboard.dut_imp); endfunction endclass环境连接关系如下图所示伪代码表示连接关系agent.monitor - scoreboard (expected) agent.monitor - model (input) model - scoreboard (actual)5. 创建测试场景与sequence5.1 基础APB sequencesequence是生成测试激励的核心。下面是一个基本的APB读写sequenceclass apb_base_sequence extends uvm_sequence #(apb_transaction); uvm_object_utils(apb_base_sequence) rand int num_trans 10; rand bit [31:0] base_addr 32h0000_1000; constraint trans_c { num_trans inside {[1:50]}; } function new(string name apb_base_sequence); super.new(name); endfunction virtual task body(); repeat(num_trans) begin uvm_do_with(req, { paddr inside {[base_addr:base_addr32hFF]}; delay inside {[0:2]}; }) end endtask endclass5.2 测试用例集成最后在test类中启动sequence并运行测试class apb_base_test extends uvm_test; uvm_component_utils(apb_base_test) apb_env env; function new(string name, uvm_component parent); super.new(name, parent); endfunction virtual function void build_phase(uvm_phase phase); super.build_phase(phase); env apb_env::type_id::create(env, this); uvm_config_db#(uvm_object_wrapper)::set(this, env.agent.sequencer.run_phase, default_sequence, apb_base_sequence::type_id::get()); endfunction virtual task run_phase(uvm_phase phase); phase.raise_objection(this); #1000; // 等待测试完成 phase.drop_objection(this); endtask endclass6. 环境复用与扩展6.1 参数化agent设计要使这个APB验证环境真正可复用我们可以将其改造为参数化设计class generic_agent #(type TRANSuvm_sequence_item, type DRIVERuvm_driver, type MONITORuvm_monitor) extends uvm_agent; // 保留原有结构但使用参数化类型 DRIVER driver; MONITOR monitor; uvm_sequencer #(TRANS) sequencer; // ... 其余实现与之前类似 endclass使用时针对APB总线特化typedef generic_agent #(apb_transaction, apb_driver, apb_monitor) apb_agent;6.2 协议扩展点在实际项目中验证环境需要适应协议的各种变体。我们可以通过以下方式增强灵活性回调机制在driver和monitor中添加回调点允许在不修改原始代码的情况下扩展行为配置对象使用独立的配置类管理协议参数如地址映射、时序要求等工厂重载利用UVM工厂模式动态替换组件实现例如添加回调支持class apb_driver_callbacks extends uvm_callback; virtual task pre_drive(apb_transaction trans); // 默认空实现 endtask virtual task post_drive(apb_transaction trans); // 默认空实现 endtask endclass然后在driver中触发回调virtual task drive_transfer(apb_transaction trans); uvm_do_callbacks(apb_driver_callbacks, pre_drive, trans) // 原有驱动代码 uvm_do_callbacks(apb_driver_callbacks, post_drive, trans) endtask这种设计允许后续用户通过注册回调来修改driver行为而无需直接修改原始代码。