[fud2] Add consistent parameter to correctly emulate or execute on Xilinx. #2400
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.
More small parts of #2267. This should fix treatment of the
XCL_EMULATION_MODE
environment variable, with respect tohw
andhw_emu
values (aka execution and emulation).Currently
fud2
does not allow forsw_emu
values because software emulation requires C files, not something we've really been dealing with.From some spot checking on havarti seems like
hw_emu
can compile to anxclbin
fine, but targeting actual execution seems to fail? At least on my toydyn-mem-vec-add.futil
file.Also finally wrote down the explicit steps to use (and the parameters required at each step) and added them to the docs.
I'll move them and polish them up if needed.
To ease dealing with parameters would it make sense to require the
[xilinx]
parameters to be part of thefud2
config file? That way most of the logic between runs would be consistent, independent of the user remembering what they compiled to originally.