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.

Sign up for GitHub

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

Jump to bottom

Added 'k' (kill) command to gdb-server, which resets the connection #528

Merged
merged 1 commit into from
Dec 11, 2016
Merged

Added 'k' (kill) command to gdb-server, which resets the connection #528

merged 1 commit into from
Dec 11, 2016

Conversation

galexander1
Copy link
Contributor

@galexander1 galexander1 commented Dec 11, 2016 •
edited by Nightwalker-87
Loading

(Closes #358, Closes #525)

@galexander1 galexander1 mentioned this pull request Dec 11, 2016
Closed
@texane texane merged commit ecc31f7 into stlink-org:master Dec 11, 2016
@Nightwalker-87 Nightwalker-87 added this to the v1.3.0 milestone Mar 16, 2020
@Nightwalker-87 Nightwalker-87 linked an issue Mar 17, 2020 that may be closed by this pull request
st-util should detect when USB commands fail #525
Closed
@stlink-org stlink-org locked as resolved and limited conversation to collaborators Apr 14, 2020
@Nightwalker-87 Nightwalker-87 linked an issue Apr 4, 2021 that may be closed by this pull request
resetting a stm32f103 with a "kill + run" doesn't seem to work #358
Closed
@Nightwalker-87 Nightwalker-87 changed the title Add 'k' (kill) command to gdb-server, which resets the connection Added 'k' (kill) command to gdb-server, which resets the connection Apr 4, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
No reviews
Assignees
No one assigned
Labels
bug/fixed code/feature-request component/st-util status/resolved
Projects
None yet
Milestone
v1.3.0
Development

Successfully merging this pull request may close these issues.

st-util should detect when USB commands fail resetting a stm32f103 with a "kill + run" doesn't seem to work
3 participants
@galexander1 @texane @Nightwalker-87