Add a --pgm tool option to stop build stage from automatically programming #392
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 fine to me. I always envisioned a pgm switch as a bool, but this makes it easier to bring in alternative programming methods if needed. Thanks! |
olofk
pushed a commit
that referenced
this pull request
Nov 21, 2023
…mming (#392) Add --pgm flag to tools with programming capabilities
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.
Add a
--pgmargument to separate place & route from programming in build stages using relevant tools (Vivado, Quartus, ISE). By default these won't attempt to program a device (which can quite easily crash servers unless a number of other options are also configured), but setting--pgm=<applicable tool>will allow it to do so.