STM32G4xx: Wrong SystemCoreClock variable #22245
Description
Description
Because of a bug in STM32Cube LL, the SystemCoreClock variable is set wrong if the actual system frequency is >80 MHz.
More details are described in a related (but already closed) PR:
zephyrproject-rtos/hal_stm32#34 (comment)
I raised this issue to track the bug, as I can't raise an issue in the original HAL repository.
Impact
Boards with STM32G431 are hardly useable with high clock frequencies, as e.g. UART baud rates are get configured wrong.
Preliminary workaround could be to reduce the system frequency to <80 MHz.