tests/periph/selftest_shield: timer allocation conflict #20096
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Contribution description
ztimer
(pulled in as dependency for a peripheral driver, e.g.periph_adc
on STM32F3) and the test applicationTIMER_DEV(1)
whenztimer_periph_timer
is in use,TIMER_DEV(0)
otherwise)Testing procedure
nucleo-f303re
inmaster
: A hard fault is triggered duringadc_init()
due to a conflict in the use of the sameperiph_timer
peripheral by the app and ztimertimer_init()
failing (because the board only has a single timer peripheral exposed)Issues/PRs references
None