AnsweredAssumed Answered

STM32Cube_FW_F0_V1.2 versus 1.3

Question asked by NStuff on Aug 19, 2015
Latest reply on Aug 21, 2015 by 68516
It is becoming annoying that since ST's inception of a Cortex implementation there have been Standard Peripheral libraries that simply are not standards to rely on.
I thought that switching to the HAL libraries would eliminate unnecessary changes but, yet again I am proven wrong.
This time it is macro names that have changed between libraries.
1.2 had.......                                     1.3 now has..........
  __APB1_FORCE_RESET();     __HAL_RCC_APB1_FORCE_RESET();
 __GPIOx_CLK_ENABLE();      __HAL_RCC_GPIOx_CLK_ENABLE();
.......etc. et cetera
After switching from the old 1.2.0 HAL to the new 1.3.0 hoping the update would fix the multitude of UART issues; I find that I now have to go back and change anything that used a macro in my code to add "__HAL_RCC_" in front of it. Why? Why were the macro names changed?

Who at ST needed something to do that they felt like changing unnecessarily the names on macros?
If you are going to standardize a library; correct items within a function \ macro, add new functions or add more macros; STOP changing names of macros!!!!!!

Outcomes