Nucleo ST Link bricked in CUBEIDE

[tschwarz]

Hi,

tried to update the ST-Link Firmware on my NUCLEO-F429ZI as requested by STM32CubeIDE. Updating failed and the board is no longer recognized as a USB device. The COM LED (LD4) on the ST-Link section blinks red.

Is there a way to resurrect the firmware? I'm running on a Linux VM inside VirtualBox on a Windows 11 host. I've mapped the USB device to the VM. Have been using this board successfully from VS Code for days now...

Thanks for any assistance...

[mƎALLEm]

Hello,

Give a try from Windows side using STM32CubeProgrammer tool. Moreover, with another PC/Laptop.

If it it doesn't fix the issue, I fear you lost your ST link! 

So maybe you need to try this at final stage: https://electronics.stackexchange.com/questions/477166/st-link-v2-repairing-issue

[tschwarz]

SOLVED!
Thanks for the suggestion to use the Windows utility for updating - will give that a try.

Anyhow - I plugged the board into a different USB port on the windows box and it works again. So the ST-Link does not have a problem, the program in flash works as before !

[Andrew Neil]

Could it be that the ST-Link is stuck in update mode?

If so, using the STSW-LINK007 ST-Link firmware updater app might help ... ?

https://www.st.com/en/development-tools/stsw-link007.html

[tschwarz]

SOLVED COMPLETELY!
Updating the ST-Link from native Windows (STM32CubeProgrammer) worked seamlessly. Now the CubeIDE ist still complaining about an outdated ST-Link version but when ignored still flashes and debugs my application as expected.

VirtualBox allows redirecting USB Links into the VM. This could have caused the problem, as the programming process seems to drop and reset the USB connection at one point. I'd assume the USB device redirection into the VM is either not fast enough or Windows connects first and then redirects, throwing the IDE off. 

Takeaway: Use the native CubeProgrammer Tool to flash the ST-Link firmware. For now I'm guessing that a native Linux setup would also have worked correctly...

[Bob S]

Yes - the firmware update sequence causes the STLink to re-enumerate as a DFU device to do the update, then back to an "STLink" device when done.