FrameV2 support and output data before TMS stage shift #3
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
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.
My goal here was to be able to write a High-Level analyzer for our development environment's debugger. The two problems were that this JTAG low-level analyzer doesn't output data until there is a state change. With our debugger, it remains in the Shift-DR state while debugging. So, I added the ability to chunk the data as it comes in, with the default value of "0" resulting in the same behavior as it currently provides. If changed to something like "8", then you get data output every 8 bits.
The second change is to output the data in a FrameV2 format for a python High-Level analyzer to be written.