You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Stlink tools version and/or git commit hash: latest (as for 25/07/2019)
Stlink commandline tool name: all
At some point in the ST-Link Utility (programmer firmware upgrade) became available the option to select the device type, which allows to choose between STM32 Debug+Mass storage+VCP and STM32 Debug+VCP. In short, it became possible to disable the "Mass storage" functionality of the Nucleo programmer. So I did. As a result, stlink utilities stopped finding the programmer. Like this:
# st-info --probe
Found 0 stlink programmers
After investigating the issue, it became clear that the USB device with disabled Mass storage functionality have other PID (0x3752 instead of 0x374B).
I added one more define of 0x3752 to the include/stlink/usb.h, and then applied it to the src/usb.c file in the same way as the existing STLINK_USB_PID_STLINK_NUCLEO.
Recompiled the stlink and voila:
# st-info --probe
Found 1 stlink programmers
... bla bla bla ...
Not sure if it could be done in the way as I did... Therefore I did not make a pull-request, but tried to depict the problem in words.
Thank you,
The stlink project maintainers
The text was updated successfully, but these errors were encountered:
At some point in the ST-Link Utility (programmer firmware upgrade) became available the option to select the device type, which allows to choose between
STM32 Debug+Mass storage+VCP
andSTM32 Debug+VCP
. In short, it became possible to disable the "Mass storage" functionality of the Nucleo programmer. So I did. As a result, stlink utilities stopped finding the programmer. Like this:After investigating the issue, it became clear that the USB device with disabled
Mass storage
functionality have other PID (0x3752 instead of 0x374B).I added one more define of 0x3752 to the
include/stlink/usb.h
, and then applied it to thesrc/usb.c
file in the same way as the existing STLINK_USB_PID_STLINK_NUCLEO.Recompiled the stlink and voila:
Not sure if it could be done in the way as I did... Therefore I did not make a pull-request, but tried to depict the problem in words.
Thank you,
The stlink project maintainers
The text was updated successfully, but these errors were encountered: