SWO support when using ST-LINK GDB server#1072
Merged
haneefdm merged 4 commits intoMarus:masterfrom Jan 14, 2025
Merged
Conversation
Collaborator
|
Can you please update the CHANGELOG.md as well? Just something brief for anything that might be user-visible. |
Collaborator
|
Especially for new features. |
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
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.
Adds the ability to use the raw SWO stream from the ST-LINK debugger.
One important change is waiting for SWO connection during startup - this seems to be necessary because starting the actual launch completely confuses ST-LINK's GDB and leaves it in a semi-frozen state. I'm sure this change should be beneficial for other adapters as well as I've seen SWO randomly not working from time to time and this is a possible explanation.
For the future, we could consider refactoring the GDB server controllers for better code sharing, there is not much about SWO init that is server specific, other than an occasional
monitorcommand.