Skip to content
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.

Sign up for GitHub

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

FMDN clock workaround: documentation update #21073

Merged
merged 2 commits into from
Mar 24, 2025
+13 −0
Merged

FMDN clock workaround: documentation update #21073

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7d32092
doc: known_issues: add entry for NCSDK-32268
kapi-no Mar 20, 2025
492ce24
doc: changelog: fast_pair: fmdn: mention workaround for FMDN clock issue
kapi-no Mar 20, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions doc/nrf/releases_and_maturity/known_issues.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3333,6 +3333,17 @@ NCSDK-23682: The Fast Pair Seeker might be unable to bond again after losing the

**Workaround:** Keep the :kconfig:option:`CONFIG_BT_SETTINGS_CCC_LAZY_LOADING` Kconfig option enabled.

.. rst-class:: v2-9-0-nRF54H20-1 v2-9-1 v2-9-0 v2-8-0

NCSDK-32268: FMDN clock might not be correctly set after the system reboot for nRF54L Series devices
The clock value in the Find My Device Network (FMDN) module is calculated using the kernel uptime function (:c:func:`k_uptime_get`).
For nRF54L Series devices, the kernel uptime persists after a system reset if the reset reason is of a specific type, such as a software reset (for example, triggered by the :c:func:`sys_reboot` API during the DFU process).
This platform-specific behavior breaks the assumption in the FMDN clock module that the uptime starts from zero after the system reboot.
For more information, see the description of the :kconfig:option:`CONFIG_BT_FAST_PAIR_FMDN_CLOCK_UPTIME_PERSISTENCE` Kconfig option that activates a workaround for this issue as part of the following patch commit.

**Affected platforms:** nRF54L Series

**Workaround:** Manually cherry-pick and apply the commit with the fix from the ``main`` branch (commit hash: ``190839b44b678e2a90793e01471155fa9e579dc1``).

Other libraries
===============
Expand Down
2 changes: 2 additions & 0 deletions doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -736,6 +736,8 @@ Bluetooth libraries and services
* A new information callback - :c:member:`bt_fast_pair_fmdn_info_cb.conn_authenticated` - to the FMDN extension API.
In the FMDN context, this change is required to support firmware update intents on the Android platform.
For further details on the Android intent feature for firmware updates, see the :ref:`ug_bt_fast_pair_provisioning_register_firmware_update_intent` section in the Fast Pair integration guide.
* A workaround for the issue where the FMDN clock value might not be correctly set after the system reboot for nRF54L Series devices.
For details, see the ``NCSDK-32268`` issue in the :ref:`known_issues` page.

* Updated:

Expand Down