STM32CubeProgrammer 2.16.0 fails to program STM32L433CC via USB
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-03-23 3:32 PM
Our customer attempted to update the firmware on their device which uses an STM32L433CC. Programming failed to erase and download the firmware on the device. STM32CubeProgrammer 1.4.0 succeeded in programming the device.
Customer is using a Windows 11 machine with STM32CubeProgrammer 2.16.0.
I have verified that the break occured somewhere between 2.14.0 and 2.16.0 as 2.13.0 works. I have also verified that the behavior is both OS-independent and GUI-independent as I experience the same failure on Linux with 2.16.0 STM32_Programmer_CLI.
This is clearly not a hardware issue, but something wrong with the DFU implementation in STM32CubeProgrammer 2.16.0.
A log file from the failure on Linux is attached.
Solved! Go to Solution.
- Labels:
-
Bug-report
-
STM32CubeProgrammer
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-07-04 6:44 AM
Hello @Rob.Riggs
Issue has been solved on the Last version of the STM32CubeProgrammer (V2.17.0).
Best Regards.
STTwo-32
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-03-23 8:49 PM - edited ‎2024-03-26 12:22 AM
Hello @Rob.Riggs
Thank you for reporting on our community. I will escalate your issue internally to the concerned team for more investigation (under ticket number 176977 which is just an internal tracking number)
Best Regards.
STTwo-32
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-03-24 9:37 AM
This also affects STM32L4+ chips. STM32CubeProgrammer exhibits the same issue when programming the STM32L4Q5RE via USB DFU.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-04-02 11:56 AM
Has this issue been replicated by the development and QA teams? When can we expect to see it fixed?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-04-05 4:13 AM
Hello @Rob.Riggs,
I can confirm the problem from our side. As a workaround, I suggest performing a full chip erase before programming the device via USB. A fix will be included in a future release, I will keep you updated.
Maryem.
In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-07-04 6:44 AM
Hello @Rob.Riggs
Issue has been solved on the Last version of the STM32CubeProgrammer (V2.17.0).
Best Regards.
STTwo-32
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-12-06 9:34 PM
hi, I got the same problem. I have tryed V16.0, V17.0 and V18.0, but they can't work. Could you please share how did you fix it? Thank you.
