[setups/osflow/filesets] do not provide default NEORV32_MEM_SRC, require it to be explicitly set #159
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
…ire it to be explicitly set
|
Makes sense 👍 |
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.
As the title explains, currently there is a default NEORV32_MEM_SRC variable in
filesets.mk, which is overriden for some boards/examples. In this PR, that is changed so that no default NEORV32_MEM_SRC is defined. Therefore, for each board/design, the user needs to explicitly select whether to use the default description or some custom sources (such as SPRAM on UP5K).