You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update ChibiOS to the latest version of the stable 20.3.x branch to allow for the STM32L4xx (found in at least the STM32L443 but possibly other MCUs). ChibiOS has in the stm32_registry.h for the STM32L4xx family it says it does not have a GPIO D & E group but the MCU does in fact have those GPIO groups.
Describe the Bug
For at least the STM32L443 (QMK uses that as the MCU for the STM32L433 as well), the ChibiOS does not enable a few of the GPIO groups for that MCU even through they are actually on the MCU and don't have a "programmatic" cost to enable them.
From my discussion with Giovanni it looks like there may be some other MCUs that had this error so this would fix those as well. These changes are backported from the more recent 21.6.x branch.
There is no way to override the stm32_registry.h in ChibiOS during the build so for things like this meaning QMK is dependent on upstream configuration changes. It may make sense to allow for keyboards to supply a stm32_registry.h so that there isn't so much extra work to get things like configuration updates for the project.
The text was updated successfully, but these errors were encountered:
Update ChibiOS to the latest version of the stable 20.3.x branch to allow for the STM32L4xx (found in at least the STM32L443 but possibly other MCUs). ChibiOS has in the
stm32_registry.h
for the STM32L4xx family it says it does not have a GPIO D & E group but the MCU does in fact have those GPIO groups.Describe the Bug
For at least the STM32L443 (QMK uses that as the MCU for the STM32L433 as well), the ChibiOS does not enable a few of the GPIO groups for that MCU even through they are actually on the MCU and don't have a "programmatic" cost to enable them.
Currently is:
Should be:
Additional Context
From my discussion with Giovanni it looks like there may be some other MCUs that had this error so this would fix those as well. These changes are backported from the more recent 21.6.x branch.
There is no way to override the
stm32_registry.h
in ChibiOS during the build so for things like this meaning QMK is dependent on upstream configuration changes. It may make sense to allow for keyboards to supply astm32_registry.h
so that there isn't so much extra work to get things like configuration updates for the project.The text was updated successfully, but these errors were encountered: