STM32CubeProgrammer V2.16 DFU Download Problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-03-25 11:10 PM - edited ‎2024-03-25 11:26 PM
Hi,
Updated from 2.15 today. Having DFU download problem seen attached.
Board is recognised but upper right still stated as "Not connected" and download fails.
Downgraded to V2.15 and same board connects and downloads OK.
OS: W10 64bit
Board: STM32F767NI custom
Fyi
Timucin KANATLI
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:57 AM
Hello @TKana.1
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-26 12:24 AM
Hello @TKana.1
Are you having the same problem as mentioned on the following post:
STM32CubeProgrammer 2.16.0 fails to program STM32L... - STMicroelectronics Community
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-26 1:06 AM
Hi,
Exactly. Mine works on V2.15
Best Regards,
Tim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-03-27 1:20 AM
I've added your problem to the ticket created for the post mentioned on my first Comment. We will be back to you as soon as there is any News.
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-07-04 6:57 AM
Hello @TKana.1
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-07-04 10:40 PM - edited ‎2024-07-04 10:40 PM
Hi,
2.17 works OK with StlinkV2 firmware V2J45S7.
Meantime, don't understand why 2.15 updater as of today still shows "no updates available". See attached
Best Regards,
Tim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-12-06 9:25 PM
No, I got the same problem. And I have test V2.17.0 and V2.18.0, but they don't work. I can still use V2.15.0.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-12-07 9:55 AM
Hello @6689157
Could you please create a new post with the issue you have and a full description of the problem (MCU or board used, versions, OS on your PC,...).
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-07 7:09 PM
Thank you. I have solve the problem, and it can work fine in V17.0 and V18.0. I found V17.0 and V18.0 are different from V15.0. In V15.0, my boatloader code can wait after clicking the 'connect' button, but in V17.0 and V18.0 the code didn't. Thus, I add a new flag to fix it.
