Stats

  • Locked Locked
  • Replies 1
  • Subscribers 12
  • Views 15493
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

I have a question about UVM_INFO in my output log file

kkurenkov

It's seems strange UVM_INFO like that.

UVM_INFO [config_direct_seq.sv(55) (55) (81) (81) (55) (55) (55) (55) (81) (81) (55) (55) (81) ] { 35596.0ns } [mem_sys_st_config_direct_seq_1] [mem_sys_st_config_direct_seq_1] 'mem_sys_st_config_direct_seq_1' is completed
UVM_INFO [config_direct_seq.sv(55) (55) (81) (81) (55) (55) (55) (55) (81) (81) (55) (55) (81) (55) ] { 35596.0ns } [mem_sys_st_config_direct_seq_1] [mem_sys_st_config_direct_seq_1] 'mem_sys_st_config_direct_seq_1' is started
ld end in hvt_mem_sys_tb_top.dut.multi_rw_unit_inst.adm_control[0] at  49666.9ns
UVM_INFO [ys_item_transform.sv(638) (638) (355) (355) (348) (348) (348) (638) (638) (355) (355) (348) (348) (355) (348) ] { 50536.0ns } [xi4_to_memsys_item_transform_0] [UPD] hvt_mem_sys_ld_config_desc is updated
UVM_INFO [config_direct_seq.sv(54) (54) (80) (80) (54) (54) (80) (54) (54) (54) (80) (80) (54) (54) (80) ] { 50536.0ns } [mem_sys_ld_config_direct_seq_0] [mem_sys_ld_config_direct_seq_0] 'mem_sys_ld_config_direct_seq_0' is completed
UVM_INFO [config_direct_seq.sv(54) (54) (80) (80) (54) (54) (80) (54) (54) (54) (80) (80) (54) (54) (80) (54) ] { 50536.0ns } [mem_sys_ld_config_direct_seq_0] [mem_sys_ld_config_direct_seq_0] 'mem_sys_ld_config_direct_seq_0' is started
st end in hvt_mem_sys_tb_top.dut.multi_rw_unit_inst.adm_control[1] at  57652.5ns
UVM_INFO [ys_item_transform.sv(638) (638) (355) (355) (348) (348) (348) (638) (638) (355) (355) (348) (348) (355) (348) (355) ] { 58425.0ns } [xi4_to_memsys_item_transform_1] [CONFIG STORE] [STORE] in uvm_test_top.env.mem_sys_axi4_to_memsys_item_transform_1
UVM_INFO [config_direct_seq.sv(55) (55) (81) (81) (55) (55) (55) (55) (81) (81) (55) (55) (81) (55) (81) ] { 58425.0ns } [mem_sys_st_config_direct_seq_1] [mem_sys_st_config_direct_seq_1] 'mem_sys_st_config_direct_seq_1' is completed

UVM_INFO [config_direct_seq.sv(54) (54) (80) (80) (54) (54) (80) (54) (54) (54) (80) (80) (54) (54) (80) (54) ] { 50536.0ns } [mem_sys_ld_config_direct_seq_0] [mem_sys_ld_config_direct_seq_0] 'mem_sys_ld_config_direct_seq_0' is started

I use AXI VIP and XCELIUM1909

Do you know how to fix this bug?

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.