Generalize SWD debugging stuff so it works on all nrf52 targets. #4377
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
Mostly for documentation purposes for future devs.
geeksville
changed the title
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.
Move the SWD debugging support I added to rak4631 up into the shared nrf52 platform.ini file - this allows SWD debugging on all of our targets. I defaulted to using "stlink" USB debugging dongles instead of "jlink" because stlinks are much cheaper and just as fast. This shouldn't change behavior for anyone who was already doing debugging because most of the nrf52 projects have been manually slamming in jlink instead.
Add a small script in bin for installing bootloaders on wio tracker boards (per @markbirss wisdom) mostly as documentation for other advanced developers.