kaushalmodi / custom_uvm_report_server Goto Github PK

View Code? Open in Web Editor NEW

34.0 5.0 8.0 434 KB

Customized UVM Report Server

License: Apache License 2.0

Makefile 1.92% SystemVerilog 89.88% nesC 2.46% Tcl 5.75%

uvm systemverilog cadence xcelium synopsys vcs

custom_uvm_report_server's People

Contributors

Stargazers

Watchers

Forkers

yuravg dummy11 scottj97 diecaptain vivhfu seamlesse ninadpachpute

custom_uvm_report_server's Issues

Behavior of table_print_detected?

In the included demo code, it seems the table_print_detected logic is never activated. The table that gets printed in producer.sv does not go through this custom_report_server at all, it seems.

I'm trying to understand what the intended behavior is. I tried modifying the producer.sv so it uses `uvm_info to print the table, like so:

`uvm_info("producer", $sformatf("Sending %s",p.get_name()), UVM_MEDIUM)                                              
`uvm_info("scottj", p.sprint(), UVM_HIGH) // instead of p.print()

And now the table_print_detected logic is activated, but the output is a little messed up:

   UVM_INFO @      0ns  Sending producer2-0 :producer
   UVM_INFO @      0ns  ---------------------------------------                                                               
Name         Type           Size  Value
---------------------------------------
producer2-0  packet         -     -
  addr       integral       32    'h1a
  initiator  producer #(T)  -1    @1942
---------------------------------------  :scottj
                          top.producer2, producer.sv(69)
   UVM_INFO @      0ns  Starting. :producer

As you can see, the first line is not lined up with the rest of the table. (Even with +UVM_REPORT_DEFAULT, it is similarly misaligned.)

I can see that without the table_print_detected logic, the word wrapping messes up the table far more, so it is useful, but I'm curious if this is really the intended behavior?

Use Nim/DPI-C to improve the string parsing performance

Ref:

https://github.com/kaushalmodi/nim-systemverilog-dpic

Unexplained behavior with max_quit_count

Using UVM 1.2, on the default uvm_report_server, I use the max_quit_count feature:

uvm_report_server report_server = uvm_report_server::get_server();                                                                               
report_server.set_max_quit_count(3); // stop after 3 UVM_ERRORs reported

When I use your custom report server, the max quit count feature no longer seems to take effect. The simulation keeps reporting dozens of errors, until something else causes it to finish.

custom_report_server report_server;                                                                                                               
report_server = new("report_server");                                                                                                             
report_server.set_max_quit_count(3); // stop after 3 UVM_ERRORs reported                                                                           
uvm_report_server::set_server(report_server);

I am assuming the set_server() call replaces the default server with the custom one. Yet, when I set the max_quit_count on the original one, before I replace it, this takes effect:

custom_report_server report_server;                                                                                                               
uvm_report_server original_report_server = uvm_report_server::get_server();                                                                       
original_report_server.set_max_quit_count(3); // stop after 3 UVM_ERRORs reported                                                                  

report_server = new("report_server");
uvm_report_server::set_server(report_server);

Do you understand why this would work, and not the second one?

kaushalmodi / custom_uvm_report_server Goto Github PK

custom_uvm_report_server's People

Contributors

Stargazers

Watchers

Forkers

custom_uvm_report_server's Issues

Behavior of table_print_detected?

Use Nim/DPI-C to improve the string parsing performance

Unexplained behavior with max_quit_count

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent

Jobs