samples: bluetooth: fast_pair: locator_tag: fix memory map for nRF54L10 #23479
Conversation
This file contains hidden or 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
github-actions
bot
added
the
doc-required
kapi-no
added
DNM
and removed
doc-required
|
Requires the following PR to be merged: |
peknis
approved these changes
Jul 28, 2025
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:sdk-nrf: PR head: c5d5074a5ef27f834e86d31341f715a7fe42478c more detailssdk-nrf:
Github labels
List of changed files detected by CI (4)Outputs:ToolchainVersion: 8ea1732c3a Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
|
You can find the documentation preview for this PR here. Preview links for modified nRF Connect SDK documents: |
alstrzebonski
approved these changes
Jul 28, 2025
mkapala-nordic
approved these changes
Jul 28, 2025
|
Remember to fix the following: https://github.com/nrfconnect/sdk-nrf/pull/23490/files#r2236427219 |
kapi-no
force-pushed
the
fast_pair_locator_tag_nrf54l10_memory_map_align
branch
from
5977028 to
1017591
Compare
github-actions
bot
added
the
doc-required
|
Rebase required to include the fix for MPSL build error: |
Fixed the memory layout for the nrf54l15dk/nrf54l10/cpuapp target in the Bluetooth Fast Pair Locator Tag sample. Previously, it was assumed that the memory size was 10 KB larger than the actual one. The NVM size in the nRF54L10 SoC is equal to 1012 KB. This change in the nRF54L10 partition map is a breaking change and cannot be performed using DFU. As a result, the DFU procedure will fail if you attempt to upgrade the sample firmware based on one of the nRF Connect SDK v3.0 releases. Ref: NCSDK-34582 Signed-off-by: Kamil Piszczek <[email protected]>
Added a changelog entry for the Fast Pair Locator Tag sample that describes the update of the memory map for the nrf54l15dk/nrf54l10/cpuapp board target. Ref: NCSDK-34582 Signed-off-by: Kamil Piszczek <[email protected]>
kapi-no
force-pushed
the
fast_pair_locator_tag_nrf54l10_memory_map_align
branch
from
1017591 to
c5d5074
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Fixed the memory layout for the nrf54l15dk/nrf54l10/cpuapp target in the Bluetooth Fast Pair Locator Tag sample. Previously, it was assumed that the memory size was 10 KB larger than the actual one. The NVM size in the nRF54L15 SoC is equal to 1012 KB.
This change in the nRF54L10 partition map is a breaking change and cannot be performed using DFU. As a result, the DFU procedure will fail if you attempt to upgrade the sample firmware based on one of the nRF Connect SDK v3.0 releases.
Ref: NCSDK-34582