uvm cmdline processor类

2024-11-16

uvm_cmdline_processor，用以处理uvm命令行参数，这些参数用于仿真阶段，而非编译阶段。

UVM 参数总结

命令参数	说明	示例
+UVM_DUMP_CMDLINE_ARGS	打印所有命令行参数到报告机制中，输出格式为树形。	`+UVM_DUMP_CMDLINE_ARGS`
+UVM_TESTNAME	指定要通过工厂创建并在 UVM 阶段中执行的 test（或 uvm_component）。如果多个设置出现，则使用第一个并发出警告。	`+UVM_TESTNAME=read_modify_write_test`
+UVM_VERBOSITY	设置所有组件的初始打印级别。如果多个设置出现，则使用第一个并发出警告。	`+UVM_VERBOSITY=UVM_HIGH`
+uvm_set_verbosity	设置特定组件在特定阶段（和仿真过程中的特定时间）上的打印级别。	`+uvm_set_verbosity=uvm_test_top.env0.agent1.,ALL,UVM_FULL,time,800`
+uvm_set_action	提供与 `uvm_report_object` 相等的报告行为设置。可使用 `ALL` 设置 ID 或严重性，指定的行为可以是 `UVM_NO_ACTION` 或其他 UVM 消息行为。	`+uvm_set_action=uvm_test_top.env0.*,ALL,UVM_ERROR,UVM_NO_ACTION`
+uvm_set_severity	设置报告的严重性级别。`ALL` 可用于 ID 或当前严重性参数。	`+uvm_set_severity=uvm_test_top.env0.,BAD_CRC,UVM_ERROR,UVM_WARNING`
+UVM_TIMEOUT	设置 UVM 框架的全局超时时间。`YES` 或 `NO` 指定是否允许用户代码改变此值。	`+UVM_TIMEOUT=200000,NO`
+UVM_MAX_QUIT_COUNT	设置报告服务器的最大退出计数。`YES` 或 `NO` 指定是否允许用户代码改变此值。	`+UVM_MAX_QUIT_COUNT=5,NO`
+UVM_PHASE_TRACE	开启阶段执行信息的追踪。用户只需要将该参数放在命令行中。	`+UVM_PHASE_TRACE`
+UVM_OBJECTION_TRACE	开启对 objection 活动的追踪。用户只需要将该参数放在命令行中。	`+UVM_OBJECTION_TRACE`
+UVM_RESOURCE_DB_TRACE	开启对资源 DB 访问的追踪。用户只需要将该参数放在命令行中。	`+UVM_RESOURCE_DB_TRACE`
+UVM_CONFIG_DB_TRACE	开启对配置 DB 访问的追踪。用户只需要将该参数放在命令行中。	`+UVM_CONFIG_DB_TRACE`
+uvm_set_inst_override	设置组件实例的重载。	`+uvm_set_inst_override=eth_packet,short_eth_packet, full_path`
+uvm_set_type_override	设置组件类型的重载。第三个参数指定是否替换先前的类型重载，默认为 1，若设置为 0，则不替换。	`+uvm_set_type_override=eth_packet,short_eth_packet,0`
+uvm_set_config_int	设置整数类型的配置项。	`+uvm_set_config_int=uvm_test_top.soc_env,mode,5`
+uvm_set_config_string	设置字符串类型的配置项。	`+uvm_set_config_string=uvm_test_top.soc_env,mode,"high"`
+uvm_set_default_sequence	设置默认序列。可以使用序列类型名称来定义默认的序列。	`+uvm_set_default_sequence=path.to.sequencer,main_phase,seq_type`

这些命令行参数在 UVM 仿真中非常重要，可以控制仿真过程中的许多方面，例如打印级别、超时设置、报告行为、组件类型重载等。通过这些参数，可以灵活地调整仿真行为，帮助优化和调试 UVM 环境。

后面如果是有好几个参数的要跟一个引号括起来。如下

1	`+uvm_set_inst_override="m_monitor, new_monitor, env.agt.monitor"

Source Code

UVM仿真命令行参数（直接上代码里的注释吧，写得挺全了）：
// Variable: +UVM_DUMP_CMDLINE_ARGS
// ~+UVM_DUMP_CMDLINE_ARGS~ allows the user to dump all command line arguments to the
// reporting mechanism. The output in is tree format.
// The implementation of this is in uvm_root.
// Group: Built-in UVM Aware Command Line Arguments
//
// Variable: +UVM_TESTNAME
//
// ~+UVM_TESTNAME=~ allows the user to specify which uvm_test (or
// uvm_component) should be created via the factory and cycled through the UVM phases.
// If multiple of these settings are provided, the first occurrence is used and a warning
// is issued for subsequent settings. For example:
//
//| +UVM_TESTNAME=read_modify_write_test
//
// The implementation of this is in uvm_root since this is procedurally invoked via
// ovm_root::run_test().
// Variable: +UVM_VERBOSITY
//
// ~+UVM_VERBOSITY=~ allows the user to specify the initial verbosity
// for all components. If multiple of these settings are provided, the first occurrence
// is used and a warning is issued for subsequent settings. For example:
//
//| +UVM_VERBOSITY=UVM_HIGH
//
// The implementation of this is in uvm_root since this is procedurally invoked via
// ovm_root::new().
// Variable: +uvm_set_verbosity
//
// ~+uvm_set_verbosity=,,,~ and
// ~+uvm_set_verbosity=,,,time,~ allow the users to manipulate the
// verbosity of specific components at specific phases (and times during the “run” phases)
// of the simulation. The ~id~ argument can be either ~ALL~ for all IDs or a
// specific message id. Wildcarding is not supported for id due to performance concerns.
// Settings for non-“run” phases are executed in order of occurrence on the command line.
// Settings for “run” phases (times) are sorted by time and then executed in order of
// occurrence for settings of the same time. For example:
//
//| +uvm_set_verbosity=uvm_test_top.env0.agent1.,ALL,UVM_FULL,time,800
//
// Variable: +uvm_set_action
//
// ~+uvm_set_action=<comp>,<id>,<severity>,<action>~ provides the equivalent of
// various uvm_report_object’s set_report_action APIs. The special keyword,
// _ALL_, can be provided for both/either the id and/or severity arguments. The
// action can be UVM_NO_ACTION or a | separated list of the other UVM message
// actions. For example:
//
//| +uvm_set_action=uvm_test_top.env0.*,ALL,UVM_ERROR,UVM_NO_ACTION
//
// Variable:+uvm_set_severity
//
// ~+uvm_set_severity=,,,~ provides the
// equivalent of the various uvm_report_object’s set_report_severity_override APIs. The
// special keyword, _ALL_, can be provided for both/either the id and/or
// ~current severity~ arguments. For example:
//
//| +uvm_set_severity=uvm_test_top.env0.,BAD_CRC,UVM_ERROR,UVM_WARNING
//
// Variable:+UVM_TIMEOUT
//
// ~+UVM_TIMEOUT=<timeout>,<overridable>~ allows users to change the global timeout of the UVM
// framework. The argument (‘YES’ or ‘NO’) specifies whether user code can subsequently
// change this value. If set to ‘NO’ and the user code tries to change the global timeout value, an
// warning message will be generated.
//
//| +UVM_TIMEOUT=200000,NO
//
// The implementation of this is in uvm_root.
// Variable: +UVM_MAX_QUIT_COUNT
//
// +UVM_MAX_QUIT_COUNT=<count>,<overridable> allows users to change max quit count for the report
// server. The argument (‘YES’ or ‘NO’) specifies whether user code can subsequently
// change this value. If set to ‘NO’ and the user code tries to change the max quit count value, an
// warning message will be generated.
//
//| +UVM_MAX_QUIT_COUNT=5,NO
//
// Variable: +UVM_PHASE_TRACE
//
// +UVM_PHASE_TRACE turns on tracing of phase executions. Users simply need to put the
// argument on the command line.
// Variable: +UVM_OBJECTION_TRACE
//
// +UVM_OBJECTION_TRACE turns on tracing of objection activity. Users simply need to put the
// argument on the command line.
// Variable: +UVM_RESOURCE_DB_TRACE
//
// +UVM_RESOURCE_DB_TRACE turns on tracing of resource DB access.
// Users simply need to put the argument on the command line.
// Variable: +UVM_CONFIG_DB_TRACE
//
// +UVM_CONFIG_DB_TRACE turns on tracing of configuration DB access.
// Users simply need to put the argument on the command line.
// Variable: +uvm_set_inst_override
// Variable: +uvm_set_type_override
//
// +uvm_set_inst_override=<req_type>,<override_type>,<full_inst_path> and
// +uvm_set_type_override=<req_type>,<override_type>[,<replace>] work
// like the name based overrides in the factory–factory.set_inst_override_by_name()
// and factory.set_type_override_by_name().
// For uvm_set_type_override, the third argument is 0 or 1 (the default is
// 1 if this argument is left off); this argument specifies whether previous
// type overrides for the type should be replaced. For example:
//
//| +uvm_set_type_override=eth_packet,short_eth_packet
//
// The implementation of this is in uvm_root.
// Variable: +uvm_set_config_int
// Variable: +uvm_set_config_string
//
// +uvm_set_config_int=<comp>,<field>,<value> and
// +uvm_set_config_string=<comp>,<field>,<value> work like their
// procedural counterparts: set_config_int() and set_config_string(). For
// the value of int config settings, 'b (0b), 'o, 'd, 'h ('x or 0x)
// as the first two characters of the value are treated as base specifiers
// for interpreting the base of the number. Size specifiers are not used
// since SystemVerilog does not allow size specifiers in string to
// value conversions. For example:
//
//| +uvm_set_config_int=uvm_test_top.soc_env,mode,5
//
// No equivalent of set_config_object() exists since no way exists to pass a
// uvm_object into the simulation via the command line.
//
// The implementation of this is in uvm_root.
// Variable: +uvm_set_default_sequence
//
// The +uvm_set_default_sequence=<seqr>,<phase>,<type> plusarg allows
// the user to define a default sequence from the command line, using the
// typename of that sequence. For example:
//
//| +uvm_set_default_sequence=path.to.sequencer,main_phase,seq_type
//
// This is functionally equivalent to calling the following in your
// test:
//
//| uvm_coreservice_t cs = uvm_coreservice_t::get();
//| uvm_factory f = cs.get_factory();
//| uvm_config_db#(uvm_object_wrapper)::set(this,
//| “path.to.sequencer.main_phase”,
//| “default_sequence”,
//| f.find_wrapper_by_name(“seq_type”));

本文作者： ICXNM-ZLin
本文链接： https://talent-tudou.github.io/2024/11/16/UVM/uvm-cmdline-processor类/
版权声明： 本作品采用 CC BY-NC-SA 4.0 进行许可。转载请注明出处！