README explain cargo run permission for gdb #113 #116
Merged
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.
Update
README.md
to explain how to givecargo run
permission to launchgdb
.As discussed in discord and #113, on first-run the gdb debugger doesn't give
cargo run
permission to rungdb
automatically and load the FW to the HW.This PR updates the
README.md
to show a command which can give this permission, and limits the permission addition to the scope of thestm32f1xx-hal
repository in use.Because of the different conventions between Linux and Windows, the two commands were unable to be distilled into the same line of text.
It is unknown if only the Linux example is wanted, and the windows version of the command should be removed?
It seems the
README.md
already makes this assumption elsewhere?Suggestions are welcome.