Is STM32Cube speed optimized?

[yavar_zarei]

Posted on August 30, 2014 at 06:30

I saw the code of stm32cube, It seems the code is not speed optimized,because nowadays micros have large amount of flash memory,the code size optimization is not important but speed optimization is very important, but stm32cube driver is written with no speed optimization in mind.

this makes our 168MHz micro in practical a 72MHz micro, and makes our 72MHz micro a 24MHz micro!   #can't-have-cake-&-eat-it

[Andrew Neil]

Posted on September 01, 2014 at 15:31

Depends what ''speed''  you're talking about:

''

STM32CubeMX is part of STMicroelectronics STMCubeâ„¢ original initiative to ease developers life by reducing development efforts, time and cost. STM32Cube covers STM32 portfolio''

http://www.st.com/web/catalog/tools/FM147/CL1794/SC961/SS1743/PF259242?icmp=stm32cubemx_pron_prcube_feb2014&sc=stm32cube-pr

It is ''optimised'' for the developer's  convenience - not the performance (execution speed, size, whatever) of the generated code.

[Montassar BEN ROMDHANE_O]

Posted on September 02, 2014 at 12:23

Hi mohseni.mohsen,

During the development of the STM32Cube firmware, there was a dilemma between the portability and the performance for some peripheral drivers to ensure the availability of the STM32Cube firmware for all the STM32 series by the e/o the current year. That is why the first versions of the STM32Cube focused rather on the portability across the different STM32Series. The performance factor  is today one of the major fields that ST is working on and should be visible on the coming releases.    Keep submitting feedback and we'll keep working to make a better STM32Cube solution!

With regards.

[Andrew Neil]

Posted on September 02, 2014 at 17:53

But that is

always

  going to be a conflict!Portability, Generality, and ''Developer Convenience'' are pretty much always  at odds with optimum runtime performance.