Inconsistent GPIO macro names

Question

Inconsistent GPIO macro names

duskwuff opened this issue 5 years ago · 5 comments

I've encountered a couple of weird inconsistencies in names used for GPIO macros:

There are no _Pos or _Msk macros for OTYPER, and the macros that do exist have an unexpected underscore between OT and the bit number. (For example, there is no GPIO_OTYPER_OT0_Pos, only GPIO_OTYPER_OT_0.) Similar issues exist for IDR, ODR, and BSRR.
The OSPEEDR register is misspelled in some places as OSPEEDER, e.g. GPIO_OSPEEDER_OSPEEDR0_Pos.

Answer 1 · 2019-09-30T14:27:05.000Z

Hi Dusk,

The issue you pointed out has been communicated to our development teams. It will be investigated soon. We will be back to you as soon as we get an answer. Thank you for your patience.

With regards,

Answer 2 · 2019-11-04T15:24:22.000Z

Hi Dusk,

Our development teams accepted your request. Definitions using _Pos and _Msk macros will be available in a future release.

Misspelled bit names GPIO_OSPEEDER_OSPEEDRx shall also be corrected.

With regards,

Answer 3 · 2019-11-04T15:24:46.000Z

ST Internal Reference: 75108

Answer 4 · 2019-11-04T15:25:26.000Z

ST Internal Reference: 75110

Answer 5 · 2020-02-28T11:13:04.000Z

Hi Dusk,

I hope you are doing well. This issue has been fixed in the STM32CubeF7 v1.16.0 firmware package which will be published soon (already available on our website "st.com").

I think we can close this issue now. Thank you again for your contribution.

With regards,