Difference between CubeF0 and CubeF1 HAL driver

[Gabriel Germanovix]

Posted on April 23, 2015 at 17:58

Hello,

A few months ago I started to use HAL driver (cubeF0, F1 and F4) instead of Stdlib.

I'm trying to create generalized codes using HAL driver to take advantage of compatibility, but when I copied some functions from a F1xx chip to F0xx the first mistake I found into HAL was that F1 RCC exported macros were different than F0 RCC exported macros.

F1 RCC exported macros:

__HAL_RCC_GPIOA_CLK_ENABLE() ....

F0 RCC exported macros

__GPIOA_CLK_ENABLE() .... (without HAL_RCC)

Will you change this feature in a future version? The actual problem is that it is difficult to create compatible codes between chip families.

Thanks

#cubef1 #cubef0 #hal-driver

[l239955_stm1]

Posted on April 24, 2015 at 06:36

I found diferences between series also. HAL library is a right direction but they have to deal with these details.

[Amel NASRI]

Posted on April 24, 2015 at 13:16

Hi,

I want to keep you informed that there is already an action to ensure compatibility across all STM32 series based on Macros and Literals naming alignment.

It will be deployed in coming releases.

-Mayla-

[Gabriel Germanovix]

Posted on April 26, 2015 at 06:08

I appreciate this efforts to ensure compatibility across all STM32 series.

Many thanks.