Page 1 of 1

STM32L4x3 GPIO Bank D and E enable mask not correct

Posted: Wed Jul 28, 2021 3:36 pm
by Jeansburger
The STM32L4x3 registry has the STM32_HAS_GPIOD and the STM32_HAS_GPIOE set to TRUE however the enable mask for the GPIO is not set correctly

Code: Select all

/os/hal/ports/STM32/STM32L4xx/stm32_registry.h

The STM32_GPIO_EN_MASK is set to

Code: Select all

#define STM32_GPIO_EN_MASK                  (RCC_AHB2ENR_GPIOAEN |          \
                                             RCC_AHB2ENR_GPIOBEN |          \
                                             RCC_AHB2ENR_GPIOCEN |          \
                                             RCC_AHB2ENR_GPIOHEN)


But it should be

Code: Select all

#define STM32_GPIO_EN_MASK                  (RCC_AHB2ENR_GPIOAEN |          \
                                             RCC_AHB2ENR_GPIOBEN |          \
                                             RCC_AHB2ENR_GPIOCEN |          \
                                             RCC_AHB2ENR_GPIODEN |          \
                                             RCC_AHB2ENR_GPIOEEN |          \
                                             RCC_AHB2ENR_GPIOHEN)

Re: STM32L4x3 GPIO Bank D and E enable mask not correct

Posted: Wed Jul 28, 2021 8:20 pm
by Giovanni
Hi,

Thanks for finding.

Giovanni

Re: STM32L4x3 GPIO Bank D and E enable mask not correct

Posted: Sat Aug 14, 2021 5:59 am
by Jeansburger
Any status on when this change would be implemented into one of the supported versions?

I would contribute the change but I'm unsure how to either make a patch or the equivalent of a PR to the repo to order to fix this. It would fix the registry I found but also any other STM32 registries I found a similar bug in.

Let me know,
~JB

Re: STM32L4x3 GPIO Bank D and E enable mask not correct

Posted: Sat Aug 14, 2021 6:16 am
by Giovanni
Hi,

This will be fixed in next release and in all active branches.

Please specify all registries where this problem is present.

Giovanni

Re: STM32L4x3 GPIO Bank D and E enable mask not correct  Topic is solved

Posted: Tue Aug 17, 2021 2:10 pm
by Giovanni
Hi,

Fixed as bug #1174.

Giovanni