New STLINK-V3PWR bricked during FW update in STM32CubeIDE 2.1.1

[Jack3]

Hello,

I purchased an STLINK-V3PWR from Mouser.

When I tried to use it, STM32CubeIDE 2.1.1 suggested updating the firmware. This failed, and the STLINK-V3PWR appears to be unusable (bricked).

What can I do? Return the device for a refund/replacement?

Or is there a way to re-flash the firmware using an STLINK-V3SET?

If it is possible to restore the firmware by re-flashing it, where can I find the correct firmware?

Kind regards,

Jack.

[AScha.3]

Hi,

>updating the firmware. This failed

What happened, in detail ?

+

>possible to restore the firmware by re-flashing it, where can I find the correct firmware?

No. STM keeping it secret, no official firmware avail.

[Jack3]

In detail:

I connected the STLINK-V3PWR and tried to flash my target with it from within STM32CubeIDE 2.1.1 as I did a minute before with the STLINK-V3SET.

This time, as expected, the IDE came with a popup telling the firmware of the STLINK-V3PWR needed to be updated.

I did this many times with Nucleo-Boards, and the STLINK-V3SET when STM32CubeIDE got updated, and never experienced problems ever with the process of doing that. After that I could still use those STLINK devices.

The update of the STLINK-V3PWR it didn't end with "update succesful" but with "update failed".
So I tried to redo the update, but the update process just hung after that and the STLINK-V3PWR did not indicate any activity.

I disconnected it from the USB port and plugged it in again, hoping to succeed, but discovered it was bricked.

STM32CubeIDE reported that no STLINK device was found.

So, if there's no way to fix it, I will return it for a refund.

And I learned a lesson: never atempt to update an STLINK-V3PWR! It will get bricked!
Although a low-quality USB cable could possibly also contribute to this phenomenon, that cable was new too.

I have send an email to Mouser for a refund.

[AScha.3]

Ok,

so if no more any reaction (enumeration) on PC connect, refund/replace , as you did nothing wrong.

btw

Update should work as on other st-link versions.