Add initial support for (ESP32) RISC-V devices #17
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
|
Althrough teleprobe is a month out of date, |
|
Don't have time for this right now unfortunately, somebody else can pick up where I left off if they want. |
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.
Notably lacking the ability to run from RAM, but that is Coming Soon™️. This works well enough to prove out the concept and run some basic tests for the time being.
I've additionally added an
ftdifeature, as the ESP32-C2 does not have the USB Serial JTAG peripheral and as such we must use an external programmer; the ESP-Prog is FTDI-based which drove this decision.Please let me know if you'd like to see anything changed in this PR :)