Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

STM32G4xx: Wrong SystemCoreClock variable #22245

Closed
martinjaeger opened this issue Jan 27, 2020 · 2 comments · Fixed by #22311
Closed

STM32G4xx: Wrong SystemCoreClock variable #22245

martinjaeger opened this issue Jan 27, 2020 · 2 comments · Fixed by #22311
Assignees
Labels
bug The issue is a bug, or the PR is fixing a bug platform: STM32 ST Micro STM32 priority: low Low impact/importance bug

Comments

@martinjaeger
Copy link
Member

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.

@martinjaeger martinjaeger added the bug The issue is a bug, or the PR is fixing a bug label Jan 27, 2020
@martinjaeger martinjaeger changed the title STM32G431: Wrong SystemCoreClock variable STM32G4xx: Wrong SystemCoreClock variable Jan 27, 2020
@ulfalizer
Copy link
Collaborator

ulfalizer commented Jan 28, 2020

Semi-unrelated, but could we enable issues on module repos? I ran into it too. @nashif

@rosterloh
Copy link
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug The issue is a bug, or the PR is fixing a bug platform: STM32 ST Micro STM32 priority: low Low impact/importance bug
Projects
None yet
6 participants