Introduce VUnit logging and checking #48
Closed
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
… Made testbench self-checking.
Using basic VUnit logging and checking provides (in this case) - Simpler calls for common assertions like checking equality. - Color coded logs that makes it easier to spot log entries with different severity levels
Rather than a separate logging to show what's being produced on a UART output the checking of that value can log passing checks. Separate loggers for UART0 and UART1 means that this can be configured for UART0 only where the interesting stuff happens.
stnolting
added
delayed
This was referenced Jun 11, 2021
Merged
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 PR builds on #47. See the commit comments for rationale.