Dbg guv #9
Open
Dbg guv #9
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
… a piece of garbage!
…orner cases when user defines custom packet format
…ion should now work in most cases
Closed
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.
These commits add the debugging cores as well as modifications to all scripts to add them automatically to all projects.
This works by adding a new kernel into every node, which receives all messages sent to TDEST = 0. This new kernel has control over all the debug cores added to design. However, I'm not sure what to do yet to get the output logs sent out over the internet, so I'll keep looking into that.
Each debug core allows the user to pause, drop, log, or inject flits on the inputs or outputs of any one of their kernels. Furthermore, these four operations can be combined arbitrarily, which allows for interesting capabilities such as single-stepping or "NAT"