This repository was archived by the owner on Oct 23, 2024. It is now read-only.
Conversation
ghost
Author
|
Up to date with gatecat/nextpnr-xilinx@f793875. Next is post-gatecat/nextpnr-xilinx#76 merge, probably. |
|
@charlottia You will also need this for it to work: |
Author
|
@hansfbaier awesome; thank you! Noted! |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Per https://social.treehouse.systems/@jleightcap/110895504300158953.
Separate build to the rest of nextpnr since it's not integrated.
I think i hauve forgotten the chipdb? But need to wait until I'm ready to deploy to my xc7 to actually test either way.