STM32CubeProgrammer does nothing after clicking Start Programming button

[BlogOrDie]

Looking for something to try. I'm want to recover from a failed firmware update of an MLite-880 from Elecevolve after their their 1-click installer. Elecevolve suggested a manual install using the firmware binary and STM32CubeProgrammer. I can put the device in its "DFU FW update mode" and connect to the device from the STM32CubeProgrammer using USB. After connect, the log shows:

08:45:07 : STM32CubeProgrammer API v2.22.0 | Windows-64Bits
08:45:35 : Disconnected from device.
08:46:01 : USB speed : Full Speed (12MBit/s)
08:46:01 : Manuf. ID : MALAHITEAM
08:46:01 : Product ID : Malahit-Lite DFU
08:46:01 : SN : 305B376E3133
08:46:01 : DFU protocol: 1.1
08:46:01 : Board : --
08:46:01 : IAP
08:46:01 : UPLOADING ...
08:46:01 : Size : 1024 Bytes
08:46:01 : Address : 0x8000000
08:46:01 : Read progress:
08:46:01 : Data read successfully
08:46:01 : Time elapsed during the read operation is: 00:00:00.053

When I click Start Programming, literally nothing happens except the progress bar at the bottom previously at 100% clears. Any information as to what these results are telling me, or suggestions as to what to try would be appreciated. I'm using V2.22.0 of STM32Cube Programmer and I have run it from both Windows 10 and 11 computers.

[Andrew Neil]

---

@BlogOrDie wrote:

Elecevolve suggested a manual install using the firmware binary and STM32CubeProgrammer

---

So have you followed-up with them after their suggestion didn't work?

STM32CubeProgrammer v2.22 has only recently been released - perhaps they rely upon an earlier version?

[BlogOrDie]

Elecevolve has made 3 suggestions so far and my question here is at the point of having tried the third suggestion without success. I have replied to them today that it didn't work. From my viewpoint, all of their suggestions are pretty much the same and don't give me confidence that they know what's going on.

I asked here in case the problem is something people see all the time. I realize that it's [edited to add "not"] STM's responsibility.

[mƎALLEm]

---

@BlogOrDie wrote:

I realize that it's STM's responsibility.

---

No it's not.. as long as we don't know what is inside that device: no MCU part number, no schematics?

[mƎALLEm]

Hello @BlogOrDie and welcome to the ST community,

Better to ask Elecevolve directly on [e-mail]

I don't think we can help you here as we don't have information about the STM32 product used inside that MLite-880 device and the hardware adopted.

 

[Andrew Neil]

It seems that this is a brand new consumer product that you have purchased:

https://www.blogordie.com/2026/04/first-impressions-mlite-880-interrupted/

 

So you should do whatever is normal for failed consumer goods in your location.

Here in the UK, it would be the retailers responsibility to fix or replace it.