Add RISCV TRACE Encoder driver #864
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
MabezDev
approved these changes
Oct 23, 2023
|
In the first iteration the decoder will be a standalone tool - the first version will pretty much just spit out all the addresses of the execution path but once we have it and we know it works reliable we can expand on that by integration it into something else and/or adding a nice GUI |
|
Sorry I'm kind of confused, how do we use this? |
|
without the said decoder there is not yet too much use for it ... that's why there are no examples yet Actually, using the driver is as simple as the docs show. enable it and when you want to get the latest data just stop it |
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 adds the driver for the RISCV TRACE Encoder for ESP32-C6 / ESP32-H2
There are no examples added in this PR since it won't be very helpful without a decoder (which is currently in the works) - and even with a decoder it would probably make more sense to add a chapter to the no_std training since it needs more explanation than just running an example spitting out some hex numbers.