Conversation
Contributor
|
I'm wondering if we should also have an extension API handle adding support for new hardware or new drivers because now one has to make manual changes to the codebase to add new boards/drivers. |
Member
Author
|
@vloncar yes, i think that's a good idea. Regarding this PR in particular, I'm having an issue in Vivado 2020.1 where it says: even after installing the board files / pointing Vivado to the right place (and the same procedure works for pynq-z2). Could this mean this FPGA part is only supported in >= 2020.2 ? |
Contributor
|
Release 2020.1.1 added some support, though I am not sure it includes this: |
This file contains hidden or 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
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 support for
pynq-zu.Type of change
Tests
https://gist.github.com/jmduarte/41a6afcd412dbd7c39cdbd0e2a1a01a3
Checklist
pre-commiton the files I edited or added.