nucleo_g431rb: Blinky too slow / wrong clock setup? #21715
Assignees
Labels
bug
The issue is a bug, or the PR is fixing a bug
platform: STM32
ST Micro STM32
priority: medium
Medium impact/importance bug
Comments
erwango
added
priority: medium
|
This is due to a AHBPrescaler not correct in the LL_PLL_ConfigSystemClock_HSI() function |
|
Great that you found the reason. So will you provide a fix? |
|
yes, in progress, I wil attach the PR which is in the Cube |
|
Refer to stm32cube: stm32g431: wrong clock setup zephyrproject-rtos/hal_stm32#34 |
Don't understand what exactly you are referring to. Was that a commit / PR? Number 34 doesn't seem related to our problem. |
|
Sorry, refer to Refer to stm32cube: stm32g431: wrong clock setup zephyrproject-rtos/hal_stm32#34 |
FRASTM
added a commit
to FRASTM/zephyr
that referenced
this issue
Jan 10, 2020
This updates the stm32cube/stm32g4xx/drivers to wa the issue zephyrproject-rtos#21715 Signed-off-by: Francois Ramu <[email protected]>
jhedberg
pushed a commit
that referenced
this issue
Jan 10, 2020
This updates the stm32cube/stm32g4xx/drivers to wa the issue #21715 Signed-off-by: Francois Ramu <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The LED is on approx. 15 times per minute (measured with stop watch), so it is 2 times slower than expected. On = off time in blinky app is set to 1 second.
To Reproduce
Steps to reproduce the behavior:
Impact
As I'm dealing with energy measurement in my application, the energy will most probably be wrong by the same factor as the blinky interval is wrong.
Environment:
Additional context
I double-checked the clock and PLL configuration in
nucleo_g431rb_defconfigvs. ST reference manual already and could not find any mistake.The text was updated successfully, but these errors were encountered: