"Upgrade error, please try again" with ST-Link

[Lysandros]

Hello,

I am facing constant difficulties in connecting to my Nucleo H723ZG Boards.

Almost every time I try to update the ST-Link via STMCube32IDE, the compilation stops half-way through the process and throws an error (see image)

I have tried:

• swapping cable and adapters
• swapping Nucleo board itself
• using difference USB ports on the computer

It appears to be, that a successfull connection happens almost randomly and about 1 out of 10 tries.

Has anyone faced the same issue?

Thanks

[Tesla DeLorean]

Seems to be already at the same level.

Do with the upgrade app directly, without any secondary connectivity or daemon trying to connect.

[TDK]

Why are you trying to upgrade? The version seems to be current.

> I am facing constant difficulties in connecting to my Nucleo H723ZG Boards.

Perhaps expand on this. What difficulties? Can STM32CubeProgrammer connect reliably?

[tjaekel]

Upgrade ST-LINK FW itself (not your user MCU code) is just needed once. When you are already on the latest version (and you are) you should be fine and no need to update the ST-LINK itself all the time again (even, you could keep going with an older version of ST-LINK FW).

When you say "compilation stops half-way through the process..." what do you mean?

If you are on an older version for the ST-LINK - yes, you might get a warning to update. If you have done - it should never come again (until a newer ST-LINK FW seen with updating the IDE). Does your ST-LINK enters ST-LINK "update mode" by itself?
Or do you press on the "ST-LINK update" all the time when you want to flash a new MCU FW?

I have seen: updating the ST-LINK FW (not the MCU FW!) needs sometimes a power cycle on the ST-:LINK.

But why are you all the time in the ST-LINK FW update mode?

[Lysandros]

Thank you all for the support.

Often I can't connect neither to my Nucleo Boards neither with STM32CubeIDE, nor with Minicom (similar to Putty), nor with VScode (via Zephyr RTOS)

In these cases, have noticed that trying to upgrade the ST-Link via the STM32CubeIDE tool sometimes brings the board back to life. If you have a good suggestion on how to troubleshoot this issue, I'd be glad.

[Lysandros]

By the way, from within VScode with the Zephyr RTOS I get the error.

 

Open On-Chip Debugger 0.12.0
Licensed under GNU GPL v2
For bug reports, read
 http://openocd.org/doc/doxygen/bugs.html
init
Error: libusb_open() failed with LIBUSB_ERROR_OTHER
Error: open failed