-
Notifications
You must be signed in to change notification settings - Fork 221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CV32E40Pv2 verification update week 12 (bis) #2394
Changes from all commits
9297f32
fb200cb
f9db87f
a71ae14
ecaaf3d
27e4b0d
844f3d0
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -421,7 +421,7 @@ class uvme_cv32e40p_zfinx_instr_covg extends uvm_component; | |
// from bhv_logic_3 | ||
cp_lsu_apu_contention_wr_rd : coverpoint cntxt.cov_vif.curr_rd_at_wb_regfile_wr_contention { | ||
bins rd[] = {[0:31]} with ( (item < 32) & (fpu_latency == 1) ); | ||
illegal_bins rd_addr_32_63 = {[32:63]}; | ||
illegal_bins rd_addr_32_63 = {[32:63]}; // zfinx does not use freg | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If you are declaring these as There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This coverage file was created by previous owner and I only helped in fixing or update based on coverage analysis. there are 2 ways to detect if illegal bin is hit. the simulation log (in this case, vsim) will issue runtime error in reporting. We can also observe illegal bin by open the ucdb for coverage analysis. However, we only interested on error reporting and not coverage analysis for illegal bin, therefore log file is the only way we use to detect such error. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. OK. Let's keep this as-is for now. I will use Issue #2395 to suggest that we remove all BTW, I really dislike parsing the simulation logs for for errors. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
So do I 😀. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
@MikeOpenHWGroup , I agreed that every person has its own preferences but there are some points we need to think ahead how to address these runtime errors.
there are few things we need to take notes. illegal bins is allow according to systemverilog LRM. Even though we can set rules to prohibit the use of illegal bins in this tb, this will not become a full proof resolution because:-
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thanks @dd-baoshan for making the list of errors not managed by uvm_errors. |
||
} | ||
|
||
// from bhv_logic_2 (revised) | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not a fan of using system tasks such as
$urandom()
because it makes writing constraints difficult. Having said that, I know that riscv-dv makes extensive use of these, so I will accept this.