Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

README explain cargo run permission for gdb #113 #116

Merged
merged 1 commit into from
Oct 2, 2019

Conversation

hazelutf8
Copy link
Contributor

Update README.md to explain how to give cargo run permission to launch gdb.
As discussed in discord and #113, on first-run the gdb debugger doesn't give cargo run permission to run gdb 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 the stm32f1xx-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.

Copy link
Member

@therealprof therealprof left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks. It's a clear improvement and we can always tweak it some more later.

@therealprof therealprof merged commit 22dcce5 into stm32-rs:master Oct 2, 2019
@TheZoq2
Copy link
Member

TheZoq2 commented Oct 2, 2019

It is unknown if only the Linux example is wanted, and the windows version of the command should be removed?

We definitvely should have windows instructions as well if possible. Forutnately, I have been able to avoid using windows for years :P, unfortunately that means that I can't really write instructions for it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants