applet.interface.better_la: a more performant logic analyzer #490
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
anuejn
changed the title
anuejn
changed the title
|
The loose fixes here look like they should be in their own PRs? |
anuejn
force-pushed
the
main
branch
3 times, most recently
from
4c5d450
to
81a9a9d
Compare
wanda-phi
reviewed
Nov 16, 2023
They are and this is why compression is needed. |
this implements dynamic priority based scheduling in the LAArbiter. Also it does improvements on the host-side python
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.
This PR implements a more performant logic analyzer applet. Performance is still not great but much better than with the event analyzer based one.
It would be very nice to add DDR support for capture & maybe a faster capture clock domain for more accurate timing. However, it is unclear if that actually makes sense based on the short captures I am already getting with this. Maybe USB lag-spikes are the issue here, but that needs further investigations.
I am very happy to take any suggestions on the code style & would be happy to work on it so that this could one day live upstream since i believe that this would also be valuable to many other people