v2 plans back-annotation #236
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I also included a rework of CSR vplan as it did not match verification environment state when v2 project started + I completed it with new v2 verification items. HWLOOP Vplan as been updated: some interrupt/debug requirement has been detailed. Every file has been pushed as a new v2 file, to make it clearer that these plans target v2 verification. Old v1 plans could be reverted to a previous state to avoid confusion and to prevent history loss between projects
|
Approved for now in order to merge these files to dev_dd, and also not to gate others from adding new testcase names into CV32E40Pv2_test_list.xlsx. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here are v2 test plans back-annotated.
I pushed all files as new files to make clear distinction between v1 and v2 files, and to ease keeping project history and avoid conflicts between v1 and v2 "Link to Coverage" (paths).
I didn't not revert v1 files yet to the state they were before we start v2 verification project.
I will let you see with Mike if it seems fine for him.
There are still holes here and there, I will let you see and try to complete as much as you could if you see any room for improvement.