Error when trying to use the STLINK-V3PWR probe
@DavidLesnjak is already working on this.
Since Nov 12, 2025.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 560
- Avg merge
- 1h 41m
- Merged PRs (30d)
- 3
Description
I get the following error when trying to list probes with a connected STLINK-V3PWR
> pyocd list -L 'pyocd.probe.*=debug'
0000900 D USB CMD> (16) f5 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [usb]
0000900 D USB IN < (req 2 bytes) [usb]
0000900 D USB IN < (2) 01 04 [usb]
0000900 D USB CMD> (16) f1 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [usb]
0000900 D USB IN < (req 6 bytes) [usb]
0000900 D USB IN < (6) 40 00 83 04 57 37 [usb]
0000900 D USB CMD> (16) fb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [usb]
0000900 D USB IN < (req 12 bytes) [usb]
0000900 D USB IN < (12) 04 00 06 00 02 06 00 00 83 04 57 37 [usb]
0000900 D STLink probe 002C00243133511439303434 firmware version: V4J6M0 [stlink]
0000900 D USB CMD> (16) f7 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [usb]
0000900 D USB IN < (req 8 bytes) [usb]
0000900 D USB IN < (8) 55 05 00 00 40 00 00 00 [usb]
0000900 D USB CMD> (16) f5 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [usb]
0000900 D USB IN < (req 2 bytes) [usb]
0000900 D USB IN < (2) 01 04 [usb]
0000900 C Error: 4 [__main__]
The same error message is also printed when trying to flash a target.
Also, when I disconnect the probe from USB, the error message disappears.
I flashed the latest software version of the STLINKV3-PWR (V4J6B2P6) with the same result. However, interestingly enough, when I set the probe to update mode through the STLinkUpgrade tool, the probe is detected without errors:
> pyocd list -L 'pyocd.probe.*=debug'
# Probe/Board Unique ID Target
--------------------------------------------------------
0 STLINK-V3PWR 002C00243133511439303434 n/a
It is not possible to flash any device in this state since the resource is busy, but maybe this gives some kind of hint as to what the source of the error is.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.