The 2.14 CubeProgrammer is slower than the 2.8 programming speed

[xelus]

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,

[kweenie]

Hi Aziz,

follow-up on the 0x0425.

I downloaded and installed the latest v20 that you recently 'announced'.

I used the same powershell 'Measure-Command' as used by your colleague 'briguiah'.

Now I have a programming time of 4s, which is better than the 20s we got with the regression, but still the double I got with versions previous to v15 regression.

Is/was this expected result ?
Does the firmware of the ST-Link/V2 plays a role ?
Any explanation/clarification as to the double flashing time ?

[kweenie]

Hi Aziz,

just ran your 'MeasureCommand' on v21.

Programming time is still double as before we started this thread (4s vs 2s).

Any particular reason the dev team is unable to achieve previous performance ?

At least there's no regression this time towards 20s, so that's positive !

Thanks for looking into this 

[kweenie]

Hi Stevejon,

the performance drop was aknowledged b y Aziz & his team.
The v2.8 version was able to program in 2s.
Then v2.15 went up to 20s (and regression was confirmed in this thread, for version 0x425).
Now with v2.20 & v2.21 we are at 4s, but not back at 2s ?

Same parameters, same hardware,... just different CUBE programmer.