-
Notifications
You must be signed in to change notification settings - Fork 907
[ac_range_check,dv] Included logging support in testbench #27645
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
Conversation
5721fd5
to
9994f54
Compare
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.
Some comments are minors but some others will require some changes in order to make this DV robust in case of reuse in other context (refers to the hard coded values) and also to ensure proper checking (refers to illegal_bins).
But, this PR looks great in general!
// Add individual case item for each csr | ||
// TODO: Coverage sampling for interrupts should be moved to the CIP | ||
// instead of it being performed in the scoreboard / predictor. Why it is | ||
// implemented in such a manner must be examined. |
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.
That's a good question. I don't have the answer, but maybe it's because some IPs have to deal with it in special ways?
@rswarbrick, do you know?
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.
Ping @rswarbrick
"intr_enable": begin | ||
// FIXME TODO MVy | ||
end | ||
"intr_test": begin |
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.
Details
FYI, when you'll test the interrupts at port level, that's the way I've done it for the HMAC. It might not the best approach but I share it in case it may help:
// Check interrupt pins in test mode |
hw/ip_templates/ac_range_check/dv/env/ac_range_check_predictor.sv
Outdated
Show resolved
Hide resolved
hw/ip_templates/ac_range_check/dv/env/ac_range_check_predictor.sv
Outdated
Show resolved
Hide resolved
hw/ip_templates/ac_range_check/dv/env/seq_lib/ac_range_check_smoke_vseq.sv
Outdated
Show resolved
Hide resolved
hw/ip_templates/ac_range_check/dv/env/seq_lib/ac_range_check_smoke_vseq.sv
Outdated
Show resolved
Hide resolved
hw/ip_templates/ac_range_check/dv/env/seq_lib/ac_range_check_smoke_vseq.sv
Outdated
Show resolved
Hide resolved
hw/ip_templates/ac_range_check/dv/env/seq_lib/ac_range_check_smoke_vseq.sv
Show resolved
Hide resolved
hw/ip_templates/ac_range_check/dv/env/seq_lib/ac_range_check_smoke_vseq.sv
Show resolved
Hide resolved
5568d72
to
b6c984a
Compare
@Razer6 Can you comment on this, please? |
hw/ip_templates/ac_range_check/dv/env/ac_range_check_predictor.sv
Outdated
Show resolved
Hide resolved
b6c984a
to
f05b074
Compare
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 think all my comments have been addressed properly, thanks @LouisTheLuis!
0928421
to
871a966
Compare
871a966
to
29f53b5
Compare
This commit includes covergroups for logging registers as well as introducing logging in the smoke sequence. Signed-off-by: LouisTheLuis <[email protected]>
29f53b5
to
51dff19
Compare
This commit includes covergroups for logging registers as well as introducing logging in the smoke sequence.