[sim/VUnit] support CLI argument for selecting the expected UART responses #66
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
Agree. This is really great! 👍 |
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.
Close #47
This is the last part of #47. It adds a custom switch to the VUnit run script, which is passed to the testbench as a top-level generic. That argument is used to decide which response to expect from the UARTs. The software program used in CI is different from the default blink example that people will get when running the testbench locally. This modification allows to handle that.
As discussed in #47, this is not the ideal solution for dealing with varying software execution logs. However, it is a nice showcase about how to define a CLI argument, which we can use in Python, and how to set a generic from Python to be used in VHDL.