-
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/waspmote: Fix timer config #14799
Conversation
@jdavid: Could you test this PR and report back here? Thanks :-) |
|
but
|
Sorry, my bad. The test manually configured the timer frequency via the |
|
It's because this test expect the timer to run at 250kHZ and now it's set to RIOT/tests/periph_timer/Makefile Lines 5 to 13 in 6bf6b6b
Can you try |
This should be changed by this commit: 9575ffd |
Good that I took a second look. I sneaked in the drop of the |
Arghh, and no I accidentially added a space :-/ |
This PR seems to go a bit out of scope: the changes in test application affect several boards. Maybe that would deserve a separate PR ? |
f9c8ae1
to
d674511
Compare
xtimer.h must not be included, when the xtimer module is not use. Otherwise compilation on the waspmote-pro with RIOT-OS#14799 will not longer work. gnrc_netif_pktq includes xtimer.h and uses xtimer, but gnrc_netif includes gnrc_netif_pktq.h regardless of whether gnrc_netif_pktq is used. This makes sure that gnrc_netif_pktq.h is only included when actually used.
xtimer.h must not be included, when the xtimer module is not use. Otherwise compilation on the waspmote-pro with RIOT-OS#14799 will not longer work. gnrc_netif_pktq includes xtimer.h and uses xtimer, but gnrc_netif includes gnrc_netif_pktq.h regardless of whether gnrc_netif_pktq is used. This makes sure that gnrc_netif_pktq.h is only included when actually used.
xtimer.h must not be included, when the xtimer module is not use. Otherwise compilation on the waspmote-pro with RIOT-OS#14799 will not longer work. gnrc_netif_pktq includes xtimer.h and uses xtimer, but gnrc_netif includes gnrc_netif_pktq.h regardless of whether gnrc_netif_pktq is used. This makes sure that gnrc_netif_pktq.h is only included when actually used.
xtimer.h must not be included, when the xtimer module is not use. Otherwise compilation on the waspmote-pro with RIOT-OS#14799 will not longer work. gnrc_netif_pktq includes xtimer.h and uses xtimer, but gnrc_netif includes gnrc_netif_pktq.h regardless of whether gnrc_netif_pktq is used. This makes sure that gnrc_netif_pktq.h is only included when actually used.
d674511
to
46f0f9c
Compare
It would be nice to get this bugfix into the next release. I just rebased on top of the now merged compilation fix. @jdavid provided testing results, so that only needs a code review, a green Murdock and an ACK 😄 (And I have good reason to believe that the recently merged compilation fixes results in a green Murdock.) |
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, changes make sense and test output was provided.
- Set XTIMER_HZ to something that is actually possible to generate with one of the available clock dividers from the core frequency - Use xtimer_on_ztimer if xtimer is used and not ztimer_xtimer_compat is used - This is needed because xtimer is simply not compatible with any of the possible clock frequencies of this board
The waspmote-pro cannot run at 250 kHz, as no available divider can divide its core frequency down to that. Instead, the board can be tested at its core clock frequency.
46f0f9c
to
f465ada
Compare
All green. |
Still good IMO |
Thanks everyone! Especially thanks to @jdavid for reporting the issue and testing the fix! |
Thank you very much! |
Contribution description
XTIMER_HZ
to something that is actually possible to generate with one of the available clock dividers from the core frequencyxtimer_on_ztimer
ifxtimer
is used and notztimer_xtimer_compat
is usedxtimer
is simply not compatible with any of the possible clock frequencies of this boardTesting procedure
The tests for
periph_timer
andxtimer
intests/
should now pass on the waspmote-proIssues/PRs references
Fixes #14750
Includes #14807