Skip to content

Conversation

LouisTheLuis
Copy link
Contributor

This commit includes covergroups for logging registers as well as introducing logging in the smoke sequence.

@LouisTheLuis LouisTheLuis force-pushed the zR-ac-range-dv-log branch 3 times, most recently from 5721fd5 to 9994f54 Compare July 17, 2025 16:49
@rswarbrick rswarbrick requested a review from martin-velay July 18, 2025 11:26
Copy link
Contributor

@martin-velay martin-velay left a 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.
Copy link
Contributor

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?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"intr_enable": begin
// FIXME TODO MVy
end
"intr_test": begin
Copy link
Contributor

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

@martin-velay martin-velay added Component:DV DV issue: testbench, test case, etc. IP:ac_range_check labels Jul 18, 2025
@LouisTheLuis LouisTheLuis force-pushed the zR-ac-range-dv-log branch 7 times, most recently from 5568d72 to b6c984a Compare July 21, 2025 21:49
@LouisTheLuis
Copy link
Contributor Author

@Razer6 Can you comment on this, please?

Copy link
Contributor

@martin-velay martin-velay left a 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!

@Razer6 Razer6 marked this pull request as ready for review August 8, 2025 11:11
@Razer6 Razer6 requested a review from a team as a code owner August 8, 2025 11:11
@Razer6 Razer6 requested review from eshapira and removed request for a team August 8, 2025 11:11
@Razer6 Razer6 closed this Aug 8, 2025
@Razer6 Razer6 reopened this Aug 8, 2025
@LouisTheLuis LouisTheLuis force-pushed the zR-ac-range-dv-log branch 5 times, most recently from 0928421 to 871a966 Compare August 11, 2025 18:27
This commit includes covergroups for logging registers as well as
introducing logging in the smoke sequence.

Signed-off-by: LouisTheLuis <[email protected]>
@Razer6 Razer6 added this pull request to the merge queue Aug 12, 2025
Merged via the queue into lowRISC:master with commit 6465ffa Aug 12, 2025
45 of 46 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Component:DV DV issue: testbench, test case, etc. IP:ac_range_check

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants