-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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.
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
FMDN clock workaround: documentation update #21073
Conversation
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:sdk-nrf: PR head: 492ce245c5b0ad47db2bb079546fbe01679a8c66 more detailssdk-nrf:
Github labels
List of changed files detected by CI (2)
Outputs:ToolchainVersion: Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst
Outdated
Show resolved
Hide resolved
doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst
Outdated
Show resolved
Hide resolved
You can find the documentation preview for this PR here. Preview links for modified nRF Connect SDK documents: https://ncsdoc.z6.web.core.windows.net/PR-21073/nrf/releases_and_maturity/known_issues.html |
04c388a
to
fa79295
Compare
Added a new known issue for the clock value in the Find My Device Network (FMDN) module that has incorrect value after the system reboot in the case of nRF54L devices. Ref: NCSDK-32268 Signed-off-by: Kamil Piszczek <Kamil.Piszczek@nordicsemi.no>
Added a changelog entry that describes addition of a workaround for the issue where the Find My Device Network (FMDN) clock value is not set correctly after the system reboot for nRF54L devices. Ref: NCSDK-32268 Signed-off-by: Kamil Piszczek <Kamil.Piszczek@nordicsemi.no>
fa79295
to
492ce24
Compare
|
No description provided.