2023-10-30 11:39 AM
Hi, I was using CubeProgrammer version 2.8 to program the STM32L552 microcontroller, using the ‘STM32_Programmer_CLI’ file. After updating to version 2.14, I have noticed a significantly longer programming time. For example, before the update, it took 1.8 seconds to program approximately 20kB; after the update, it takes over 10 seconds. My programming settings are as follows:
call "%programmer%" -c port=swd freq=1000 -w "%hexfile%" -v
I have tried different SWD frequencies, 3300 and 24000, but no luck. Does anyone else have this issue and know the solution?
I also have one more question - if a verification error occurs, why does STM32_Programmer_CLI return 0 as the exit code? Shouldn’t it be a different value that indicates an error?
Best regards,
2025-02-25 7:31 AM
Hi @kweenie
Thank you for the quick test. I was really hoping that would help with the programming time, but that would have been too simple, haven't it ?
Regarding the write protection address, it could be a real fix that has been made after v13, the only way to know is to look at the device datasheet, which is / should be the ultimate truth.
2025-02-25 7:34 AM
I replaced the '425' files (html or stdlr) from v13 into the corresponding v18 folders for these folders:
AND..... bham, back at 2s ???
2025-02-25 7:35 AM
and now ?
who can 'forward' this to ST ?
2025-02-25 7:41 AM
Excellent, kudos for digging deeper and getting it to work !
Then again, why should it need the files scattered in 5 different places ?
2025-03-03 4:24 AM
Hi Aziz,
did you notice this thread ?
Just to inform you that also v2.19 flashes the '425' chip (ID 425, STMicroelectronics, Cortex-M0+, STM32L03x/L04x/L010, ARM 32-bit Cortex-M0+) 10x slower than previous versions ?!
I think this was broken in v2.12...
Any comments on the STM side ?
2025-03-11 12:34 AM
Aziz (or anyone else),
how/where can I open a support request for this (since you are not reacting) ?
2025-03-11 1:28 AM - edited 2025-03-11 1:31 AM
Hello @kweenie,
Thanks for bringing this to our attention.
We are already investigating the concerns you raised internally (Internal tracking number: 205049).
Please be patient, I will get back to you ASAP.
Aziz