STM32CubeProgrammer 2.10.1 Will not connect to ST-Link Nucleo (ST-Link V2/1) or Discovery ST-Link V3
Hi,
I recently updated:
- CubeMX (6.5.0)
- CubeIDE (1.9.0)
- CubeProgrammer (2.10.0)
I am having trouble with the Programmer not connecting to the targets either the Nucleo F411RE or the H7B3Li-DK. I have not tries any other types of boards.
Pushing the refresh button with ST_LINK Selected produces:
10:46:41 : ST-LINK error (DEV_CONNECT_ERR)
However the drop down control shows both the devices that are connected viz:
Pushing the Connect button for the Nucleo produces an error:
10:46:41 : ST-LINK error (DEV_CONNECT_ERR)
10:49:58 : ST-LINK SN : 066EFF535149756687093505
10:49:58 : ST-LINK FW : V2J39M27
10:49:58 : Board : NUCLEO-F411RE
10:49:58 : Voltage : 3.26V
10:49:59 : Error: No STM32 target found!
Doing this for the Discovery does the same:
10:51:30 : ST-LINK SN : 004D002A3438510634313939
10:51:30 : ST-LINK FW : V3J9M3
10:51:30 : Board : STM32H7B3I-DK
10:51:30 : Voltage : 3.29V
10:51:31 : No STM32 target found!
10:51:31 : ST-LINK SN : 004D002A3438510634313939
10:51:31 : ST-LINK FW : V3J9M3
10:51:31 : Board : STM32H7B3I-DK
10:51:31 : Voltage : 3.29V
10:51:31 : Error: No STM32 target found!
However I can update the ST-Link Firmware and on completion the USB notifies the virtual com port and windows file explorer opens.
The driver details are:
I have done the following in an attempt to rectify the situation:
- Uninstalled CubeProgrammer.
- Rebooted the PC
- Reinstalled Programmer
- Rebooted.
- Uninstalled Programmer 1.10.0
- Rebooted
- Installed Programmer 1.9.0
- Rebooted.
This did not work so I uninstalled 1.9.0 and went back to 1.10.0.
Cube IDE is able to connect to both the Nucleo and Discovery and appears to work OK. SSTMSudio also works OK.
I have tried different US cables which all worked with CubeIDE, but not with the programmer. In any event the upgrade function works so if there was a problem with the USB port or cables the upgrade would also fail.
Could someone help me solve this.
There is also a problem with multiple connections (more than two), but I have already reported this.
Regards
Rob


