2024-12-19 2:03 PM
Hi,
I found a bug on new version 2.18 STM32Cube programmer.
Of course, I have the same problem with the new version of STM32CubeIde 1.17
It looks file STM32_Prog_DB_0x483.xml in \Data_Base folder has changed between versions 2.17 and 2.18
If I use the file STM32_Prog_DB_0x483.xml from the version 2.17 and I replace this file in version 2.18, I can access my STM32H730 device.
We tried it on 2 different computers.
I do not really understand the xml file differences, so I do not know if I can continue to use STM32_Prog_DB_0x483.xml file of version 2.17 with version 2.18 and STM32CubeIDE 1.17
Do you have a workaround ?
Sébastien
Solved! Go to Solution.
2025-01-10 1:40 AM
Hi @Maryem
Do you have any feedback of this problem.
I just looking for a workaround right now.
I cannot develop my firmware for almost 1 month now.
Regards,
Sébastien
2025-01-20 7:57 AM
Hello @COSEBE ,
I've sent you a message. Could you check your DM?
Maryem.
2025-01-20 7:58 AM
Yes, DM is answered
2025-01-28 12:52 AM
2025-02-10 5:54 PM
I Have the same problem. How to get the patch and how to install it?
2025-02-24 9:08 PM
Hi Maryem,
I too have a custom board with this issue on this chip. I have upgraded to STM32CubeProgrammer 2.18 and upgraded my STLink V2. I cannot program via STM32cubeIDE as well, but can read target info on CubeProgrammer. Essentially the same as the original post.
What is the fix??
Thanks
2025-04-14 11:48 AM
The problem is still present in STM32CubeProgrammer 2.19 and in STM32CubeIDE 1.18:
Is there any patch to solve it?
Best regards.
2025-07-11 7:38 AM
Hello,
The issue has been resolved in STM32CubeProgrammer v2.20.0.
You can download it from this Link.
Maryem.
2025-09-02 12:23 AM
This is a big problem.
I'm currently having the problem with both versions: STM32CubeIDE v.1.19.0 and STM32CubeProgrammer v.2.20.0 for the STM32L431CBY microcontroller. See the images below.
Could you please suggest a solution as soon as possible? As you can understand, we have deadlines, and this issue has been pending for months!
Would it be better to downgrade while you investigate the issue? Or use and replace the XML database with a previous version, as one user mentioned above?
In any case, could you offer an alternative solution in the meantime?
Thanks in advance.
JaimeR
2025-09-09 4:51 AM