-
Notifications
You must be signed in to change notification settings - Fork 2k
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
boards/common/nucleo: increase XTIMER_BACKOFF for STM32F103 #11975
boards/common/nucleo: increase XTIMER_BACKOFF for STM32F103 #11975
Conversation
- Boards using stm32f103xx use the same custom config for xtimer which relies on the same underlying hardware timers that hang when sleeping for <20us so spin when approaching that limit.
@cladmi might want to take a look at this one as well. |
Note, this does not change the |
Yes, would you want me to change it here as well? There are a couple of more |
I indeed had failures for these tests on the Note, you have an error in your testing procedure as you list two times the same application. It works for me with
|
@MrKevinWeiss you may want to test the bluepill |
No need to change it here. I just wanted to precise as you were saying The |
Yes, but two boards. But I should have specified to test both apps as well. |
You test the same app two times on each board :)
|
|
I can test on the nucleo-f103rb, it is a bit easier... |
Ahh sorry... fine I will test on the bluepill. |
|
How did you determine the number (19)? Trial and error? |
Yes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK
@cladmi @MrKevinWeiss Thanks for the review! |
Thank you for addressing the failing tests :) |
Contribution description
This PR increases XTIMER_BACKOFF for all
stm32f103
based board that are using customXTIMER_BACKOFF
definitions. While testing #11809 it was seen that fornucleo-f103rb
2 tests where failing because of too smallXTIMER_BACKOFF
definitions. This PR fixes this for allstm32f103
based board running on the same timer with the sameCORE_CLOCK
Testing procedure
Tested on
nucleo-f103rb
andbluepill
:python dist/tools/compile_and_test_for_board/compile_and_test_for_board.py --jobs 2 . nucleo-f103rb --applications="tests/xtimer_usleep_short tests/xtimer_periodic_wakeup"
python dist/tools/compile_and_test_for_board/compile_and_test_for_board.py --jobs 2 . bluepill --applications="tests/xtimer_usleep_short tests/xtimer_usleep_short/"
Issues/PRs references