Add VUnit #65
Merged
Add VUnit #65
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
|
This looks quite complete, right?! 🤔 : |
|
It is. If you are good with it, go ahead and merge! |
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.
This is another subset of #47. As discussed, the existing testbench is copied and it's modified for supporting VUnit's Python runner. In following PRs, the proposal is to add advanced verification features and Verification Components to the VUnit testbench(es). As we add those, we can remove the equivalent hand-written test code. In this sense, testing of the UART1 is disabled in the
neorv32_tb.simple.vhd, but it is tested in theneorv32_tb.vhd(run with VUnit). Moreover, the Processor workflow is modified, in order to run VUnit tests using the VUnit/vunit_action Action.