2021-02-05 04:16 AM - last edited on 2023-07-21 01:45 AM by Amel NASRI
2021-02-20 08:06 PM
I encountered the same problem, I received ST-LINK V3SET three days ago, and is a new unit but cannot do a firmware upgrade via STM32CubeProgrammer as picture shown below:
2021-02-21 05:53 AM
Did they work properly before?
Cheap/charging cables?
Try with better cables.
Try with the stand-alone utility, not spawning from STM32 Cube Programmer.
To troubleshoot or identify common causes it would be super helpful to provide as much system context as possible.
ie
Make and Type of machine.
Version of Windows, Corporate or Personal.
Use of Hubs or Docking Stations.
Rear or Front USB ports.
USB2 or USB3 ports.
Types of other software, AV, Remote Diagnostic, Optimization Tools, Policies, etc, installed on the machine which might stop in functioning normally.
2021-02-21 03:57 PM
I am returning this unit to Element14, to obtain a replacement later.
2022-02-08 03:00 PM
I had the same with STLinkUpgrade 3.3.7. I have been using this device for one year and tried to update it and was left with bricked device now.
Is there any way to recover it ? Or maybe the second stlink to reflash the first one ?
2022-11-17 08:47 AM
I have the same problem in a linux machine. I used the en.stsw-link007_v3-10-3 utility to update the st-link firmware of a STM32H747I-DISC0 module and it worked ok. Next, with the same USB cable and software utility the upgrading process failed for a second STM32H747I-DISC0 module and this module is now bricked.
2022-11-17 10:09 AM
Two year old thread to which ST hasn't officially responded with advice, or solution.
Start a NEW thread.
Version numbering also looks inconsistent.
@Amel NASRI @STOne-32
2023-01-19 01:26 AM
Hi, I might be a little late to the party, but I solved this kind of issue here:
https://community.st.com/s/question/0D73W000001npikSAA/detail
Hope it helps!