stm32f4: xtimer clock running at twice the speed #6460
Labels
Area: timers
Area: timer subsystems
Platform: ARM
Platform: This PR/issue effects ARM-based platforms
Type: bug
The issue reports a bug / The PR fixes a bug (including spelling errors)
So, this evening I experienced the same problem as with #6287 on my nucleo-f401 board.
Tested with the timer_periodic wakeup example again.
CPU: stm32f401RE
board: Nucleo-f401
expected to receive a message every second. A message is received every 500ms.
RIOT seems to think that a second has elapsed:
Problem seem to be introduced by #6184
Might be related to the fix in #6287 that the stm32f4(01) needs to be added to the solution from #6291
The text was updated successfully, but these errors were encountered: