nRF52 SDK 15.0 - Enable more than 1 interrupt #11622
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.
Description
With the move from nRF52 SDK v14.2 to v15.0, the
GPIOTE_CONFIG_NUM_OF_LOW_POWER_EVENTS
setting was changed from a default of 4 to a default of 1 (the setting has now been renamedNRFX_GPIOTE_CONFIG_NUM_OF_LOW_POWER_EVENTS
). This setting controls how many interrupts you can configure in your application and silently fails when you try to enable more than are configured. This issue was initially raised in #10949 by @anton-veretenenko, but we also ran into this problem while diagnosing why the mbed-os-example-lorawan example application stopped working with our nRF52840-based board once we moved to mbed-os-5.13.0 (the first release containing v15.0 of the nRF52 SDK).This PR resets the default value for
NRFX_GPIOTE_CONFIG_NUM_OF_LOW_POWER_EVENTS
to 4 for both the nRF52840 and nRF52832.Pull request type
Reviewers
Release Notes