nrfx_config_nr9160: Add missing mappings of peripheral base addresses #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
For quite a few peripherals that are currently supported by nrfx HALs or drivers there are no definitions of corresponding CMSIS-Core peripheral accessing symbols that would provide their base addresses in the proper domain (secure or non-secure), accordingly to the build target. This commits adds these missing definitions. Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
carlescufi
approved these changes
Sep 5, 2019
pkwiek
added a commit
to pkwiek/hal_nordic
that referenced
this pull request
Dec 15, 2020
Fix zephyrproject-rtos#1: Transmission failure would cause to leave an allocated buffer resulting in a serialization failure leading to an assert, which was seen as a timeout error on APP core side. Fix zephyrproject-rtos#2: It is possible for nrf_802154_spinel_send function to be preempted resulting in the static frame buffer being reused. The buffer size was reduced accordingly to 802.15.4 frame size and possible additional data. Fix zephyrproject-rtos#3: Radio driver's API call using serialization can be preempted after issuing a serialized call request to NET core, but before preparing the notifier for an awaited property. This results in receiving a property that no one waits for and dropping the property as an unwanted. In current implementation the awaited property is prepared during the notifier lock. Re-fix zephyrproject-rtos#4: The issue which manifests itself in disabled NVIC interrupts in SED roles. Signed-off-by: Pawel Kwiek <pawel.kwiek@nordicsemi.no>
rlubos
pushed a commit
that referenced
this pull request
Dec 16, 2020
Fix #1: Transmission failure would cause to leave an allocated buffer resulting in a serialization failure leading to an assert, which was seen as a timeout error on APP core side. Fix #2: It is possible for nrf_802154_spinel_send function to be preempted resulting in the static frame buffer being reused. The buffer size was reduced accordingly to 802.15.4 frame size and possible additional data. Fix #3: Radio driver's API call using serialization can be preempted after issuing a serialized call request to NET core, but before preparing the notifier for an awaited property. This results in receiving a property that no one waits for and dropping the property as an unwanted. In current implementation the awaited property is prepared during the notifier lock. Re-fix #4: The issue which manifests itself in disabled NVIC interrupts in SED roles. Signed-off-by: Pawel Kwiek <pawel.kwiek@nordicsemi.no>
adamkondraciuk
pushed a commit
to adamkondraciuk/hal_nordic
that referenced
this pull request
Dec 18, 2020
…ure/NRFX-360-integrate-nrfx to haltium-dev * commit '3fa363cccf36ed53392b3c9d329e6cf6a2513756': NRFX-360: nrfx: integrate 3.0.0-alpha-1
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
For quite a few peripherals that are currently supported by nrfx HALs
or drivers there are no definitions of corresponding CMSIS-Core
peripheral accessing symbols that would provide their base addresses
in the proper domain (secure or non-secure), accordingly to the build
target. This commits adds these missing definitions.