STM32F2xx_HAL_Driver vs STM32 standard peripheral library

[martingingras9]

Posted on June 02, 2014 at 22:16

Hi,

I am trying to understand what library should I use mainly what are the pros and cons?  I am working right now on a STM3221G-EVAL board and will migrate soon to a custom board with a

http://www.st.com/web/catalog/mmc/FM141/SC1169/SS1575/LN9/PF245079

... I am unable to find to find a comparison...  thanx  Mart

[Tesla DeLorean]

Posted on June 03, 2014 at 00:53

Like many things it helps if you can make your own objective decisions rather than rely on the opinions of others..

The standard library is mature, relatively bug free and well supported by people like myself. ST has opted to cease development of it, and marked it Not Recommended for New Designs.

The Cube/HAL has ST's active support, but is in the early stages of development and testing, and has a lot of bugs making it unsuitable for code you expect to deploy, and support in the field.

[martingingras9]

Posted on June 03, 2014 at 15:43

Hi,

thanx for the response.  I cannot make myself an idea since I am unable to build a project using HAL driver and eclipse.  There is no option for code generation for the eclipse platform :(

[marsenault]

Posted on June 11, 2014 at 17:37

Hello clive1,

After several false starts, and an ST seminar, I have proceeded using Cube4. I am running into issues with the SPI driver and Hard Faults. I am ready to restart using the standard libraries.  Where do I find the standard libraries for the STM32F4?

Thanks,

Mark

[Tesla DeLorean]

Posted on June 12, 2014 at 02:19

Red Download button down at the bottom. The NRND seems to have disappeared, and marked as Active again.

http://www.st.com/web/en/catalog/tools/PF257901

http://www.st.com/web/en/catalog/tools/PF257904

[groufosse]

Posted on June 16, 2014 at 21:16

I was reading this thread as I am having the same issues as the post by ''marky sparky'' below.

I find this quite difficult to believe. ST puts out CUBE generator software, which seems to be quite buggy, and in the same breath, decides to no longer support the SPL ?

Can anyone explain how this makes any sense...why couldn't these seemingly basic bugs be evaluated in beta tests before issuing this, causing users to face hours of grief trying to figure out if it's what they are doing...or...?

It's one thing to understand the complexity of the task you are doing, and the device you will use to get the job done. If the company making the device gives you the job of beta testing and debugging THEIR software, how could this possibly make my job easier and let me focus on solving the problems I really need to solve, and not theirs??