-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use full version of ipq-pynq-utils package #301
Merged
Merged
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
Fix typo
imported numpy
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.
We've been using parts of https://github.com/kit-ipq/ipq-pynq-utils to configure the LMX2594 clock chips on our ZCU111 frontend. This replaces our stripped-down and modified subset of ipq-pynq-utils with the full package (imported as a subtree). We have made various changes to ipq-pynq-utils to merge in our changes and get rid of extra dependencies, and are submitting those changes back to ipq-pynq-utils.
The long-term purpose of these changes is to let us use ipq-pynq-utils instead of xrfclk for the initial configuration of the clock chips on the RFSoC boards (we are doing some ugly hacks with xrfclk to change config parameters) and readback of the clock chip status (totally unsupported by xrfclk).
For developers: when making changes to files in the ipq-pynq-utils directory, it's easiest if those changes are made in the openquantumhardware/ipq-pynq-utils repository. Then pull the subtree into the qick repository by running the following command in the base directory of the qick repo:
It's possible to make the change in qick and push it to ipq-pynq-utils, but somewhat less nice. See https://gist.github.com/SKempin/b7857a6ff6bddb05717cc17a44091202 for more about subtrees.