Add OpenOCD support for onboard ESP32-S2-Kaluga-1 debug tool #1185
Conversation
This file contains hidden or 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
Author
|
Separately, I've also submitted a PR for the docs repo to reflect that this board does in fact have an on-board debugger that is compatible with Platformio. |
Member
|
The doc page for this board will be automatically updated once the next release of this dev-platform is published. |
Author
|
One note about the code that was merged - will that alsoadd FTDI to the flash protocols? That was a requirement to get it to work when I was testing on my end. |
Member
Yes, FTDI is added, but only for ESP32-S2-Kaluga-1. |
Author
|
Cool. I’ll give the updated version a shot this afternoon and report back. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 updates the default OpenOCD version from v0.11 to v0.12 (which adds support for the Kaluga dev board amongst other things) and changes the board definition to refer to the Espressif-provided configuration file.
I've tested this with a Kaluga board locally and can confirm that - although requiring a bit of driver-juggling, similar to other Espressif dev boards - it works.