Fixed STLINK-V3 programmer lock up when no target connected #1467
+5
−0
Conversation
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
5 tasks
Nightwalker-87
approved these changes
Apr 17, 2025
Nightwalker-87
added
status/resolved
programmer/STLINK/V3
Nightwalker-87
changed the title
Nightwalker-87
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The STLINK-V3 firmware locks up and stops responding to USB traffic when it receives a
STLINK_DEBUG_EXITcommand while it is not actually inSTLINK_DEV_DEBUG_MODE. Sincestlink_exit_debug_mode()is an exposed library function, I believe checking every time before sending the command is warranted, instead of trusting the caller to not trigger this bug.Fixes #1399
Tested on STLINK-V3MINIE (Firmware V3J15) and STLINK-V3EC (Firmware V3J15S1)