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.

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

doc: update known issues for NCS 2.3.0 #10362

Merged

Conversation

greg-fer
Copy link
Contributor

@greg-fer greg-fer commented Feb 20, 2023

Added v2.3.0 tag to known issues.



  • Added JIRA task to the SLM issue from @junqingzou
  • Confirmed edits to MPSL known issues with @KAGA164
  • Rebased against new PRs
  • Add the known issue from @koffes
  • Add known issue from @bama-nordic (e-mail)

@greg-fer greg-fer added this to the 2.3.0 milestone Feb 20, 2023
@github-actions github-actions bot added changelog-entry-required Update changelog before merge. Remove label if entry is not needed or already added. doc-required PR must not be merged without tech writer approval. labels Feb 20, 2023
@NordicBuilder
Copy link
Contributor

Test specification

CI/Jenkins/NRF

  • Skipped

CI/Jenkins/integration

  • Skipped

Note: This message is automatically posted and updated by the CI

@greg-fer greg-fer added DNM CI-disable Disable CI for this PR and removed changelog-entry-required Update changelog before merge. Remove label if entry is not needed or already added. labels Feb 20, 2023
@greg-fer greg-fer force-pushed the doc_release_known_issue_update_230 branch from b601e48 to 0c043fc Compare February 20, 2023 09:40
@github-actions github-actions bot added the changelog-entry-required Update changelog before merge. Remove label if entry is not needed or already added. label Feb 20, 2023
@greg-fer greg-fer removed the changelog-entry-required Update changelog before merge. Remove label if entry is not needed or already added. label Feb 20, 2023
@NordicBuilder
Copy link
Contributor

You can find the documentation preview for this PR at this link. It will be updated about 10 minutes after the documentation build succeeds.

Note: This comment is automatically posted by the Documentation Publishing GitHub Action.

doc/nrf/known_issues.rst Outdated Show resolved Hide resolved
doc/nrf/known_issues.rst Show resolved Hide resolved
doc/nrf/known_issues.rst Outdated Show resolved Hide resolved
doc/nrf/known_issues.rst Outdated Show resolved Hide resolved
doc/nrf/known_issues.rst Outdated Show resolved Hide resolved
doc/nrf/known_issues.rst Outdated Show resolved Hide resolved
doc/nrf/known_issues.rst Outdated Show resolved Hide resolved
doc/nrf/known_issues.rst Outdated Show resolved Hide resolved
doc/nrf/known_issues.rst Outdated Show resolved Hide resolved
@MarekPieta
Copy link
Contributor

MarekPieta commented Feb 20, 2023

.. rst-class:: v2-3-0 v2-2-0 v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0 v1-7-1 v1-7-0 v1-6-1 v1-6-0 v1-5-2 v1-5-1 v1-5-0 v1-4-2 v1-4-1 v1-4-0 v1-3-2 v1-3-1 v1-3-0 v1-2-1 v1-2-0 v1-1-0 v1-0-0 v0-4-0 v0-3-0

NCSDK-19865: GATT Robust Caching issues for bonded peers
  The Client Supported Features value written by a bonded peer may not be stored in non-volatile memory.
  Change awareness of bonded peer is lost on reboot.
  After reboot each bonded peer is initially marked as change-unaware.

  **Workaround:** Disable the GATT Caching feature (:kconfig:option:`CONFIG_BT_GATT_CACHING`). Make sure that Bluetooth bonds are removed together with disabling GATT Caching if the functionality is disabled during a firmware upgrade.

@jori-nordic, @alwa-nordic, the issue is related to Bluetooth host implementation in Zephyr, fixes did not went in for NCS 2.3.
Do you think we can add the known issue under Bluetooth® LE section`? Is the wording OK for you?

@greg-fer, the root cause of the issue is in the Zephyr's Bluetooth host implementation, but it could have negative impact on nRF Desktop. Do you think we could also link the issue under nRF Desktop tab to ensure that customers are aware of it?

Hi @Thalley, FYI: the issue may also affect the Bluetooth audio use-case - CONFIG_BT_AUDIO_UNICAST_SERVER selects CONFIG_BT_GATT_CACHING.

@jori-nordic
Copy link
Contributor

@MarekPieta The wording is correct for me.

@umapraseeda
Copy link
Contributor

Minor fixes:

  • CIA-890: kconfig ->Kconfig.
  • Two styles for sdk-zephyr: normal and with backticks. May be it should just be one way for consistency.

@nordic-hani
Copy link
Contributor

@greg-fer Please add the following known issue.

.. rst-class:: v2-1-3 v2-1-2 v2-1-1 v2-1-0 v2-0-2 v2-0-1 v2-0-0 v1-9-2 v1-9-1 v1-9-0 v1-8-0

TNSW-46156: The LwM2M carrier library can in some cases trigger a modem bug related to PDN deactivation (AT+CGACT) in NB-IoT mode.
  This causes excesive network signaling which can make interactions with the modem (AT commands or :ref:`nrfxlib:nrf_modem` library functions) hang for several minutes.

  **Workaround:** Add a small delay before PDN deactivation as shown in `Pull Request #10379 <https://github.com/nrfconnect/sdk-nrf/pull/10379>`_.

@github-actions github-actions bot added the changelog-entry-required Update changelog before merge. Remove label if entry is not needed or already added. label Feb 21, 2023
@nordicjm
Copy link
Contributor

There is an issue to add for zephyr possibly, currently being looked into by @nordic-krch NCSDK-18426 - details to be provided when more on the issue known

@greg-fer greg-fer force-pushed the doc_release_known_issue_update_230 branch from 030942d to 3c28664 Compare February 28, 2023 10:15
Copy link
Contributor

@trantanen trantanen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Known issue comment is fine now for CIA-892. If we decide to take zephyrproject-rtos/zephyr#54901 into the release, we'll remove this known issue.


NCSDK-19727: Cannot build the :ref:`peripheral_hids_mouse` sample with security disabled.
Copy link
Contributor Author

@greg-fer greg-fer Feb 28, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not removing it. I'm just moving it down a couple of lines (see line 1569) after the rebase.

@greg-fer greg-fer removed the changelog-entry-required Update changelog before merge. Remove label if entry is not needed or already added. label Feb 28, 2023
@greg-fer greg-fer force-pushed the doc_release_known_issue_update_230 branch from 3c28664 to 834cb43 Compare February 28, 2023 10:52
@github-actions github-actions bot added the changelog-entry-required Update changelog before merge. Remove label if entry is not needed or already added. label Feb 28, 2023
@greg-fer greg-fer force-pushed the doc_release_known_issue_update_230 branch from 834cb43 to 5c01d3d Compare February 28, 2023 11:42
@pdunaj pdunaj dismissed their stale review February 28, 2023 11:45

Talked offline - it seems the discussion about these issues go deeper. We can add this entry later when it's decided so there is no need to block this PR.

Comment on lines 3190 to 3199
.. note::
The list of security vulnerbilities has been introduced only in the |NCS| v2.3.0.
For this reason, no previous versions are listed.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
.. note::
The list of security vulnerbilities has been introduced only in the |NCS| v2.3.0.
For this reason, no previous versions are listed.
.. note::
The list of security vulnerabilities has been introduced only in the |NCS| v2.3.0.
For this reason, no previous versions are listed.

@greg-fer greg-fer removed the changelog-entry-required Update changelog before merge. Remove label if entry is not needed or already added. label Feb 28, 2023
@greg-fer greg-fer force-pushed the doc_release_known_issue_update_230 branch from 5c01d3d to b86ad6a Compare February 28, 2023 14:34
@github-actions github-actions bot added the changelog-entry-required Update changelog before merge. Remove label if entry is not needed or already added. label Feb 28, 2023
Comment on lines 440 to 446
nRF7002
*******

.. rst-class:: v2-3-0

SHEL-1352: Incorrect base address used in the OTP TX trim coefficients
Because of the use of an incorrect base address used in the One-Time Password TX trim coefficients, the transmit power will deviate by +/- 2dB from the target value.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bama-nordic , please review.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest rewording the description as "Incorrect base address used for TX trim coefficients in the One-Time Programmable (OTP) memory, resulting in transmit power deviating by +/- 2dB from the target value"

Copy link
Contributor

@gregersrygg gregersrygg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Found a typo. I guess most users understand what we mean, but it would be nice if this could be fixed.

@@ -160,7 +167,7 @@ CIA-661: Asset Tracker v2 application configured for LwM2M cannot be built for t
CIA-890: The application cannot be built with :file:`overlay-debug.conf` and :kconfig:option:`CONFIG_DEBUG_OPTIMIZATIONS` set to ``y``
Due to insufficient flash space for the application when it is not optimized, the :ref:`asset_tracker_v2` application cannot be built with :file:`overlay-debug.conf` and :kconfig:option:`CONFIG_DEBUG_OPTIMIZATIONS` set to ``y``.

**Workaround:** To free up flash space when debugging locally, uncomment the following kconfig options in the :file:`prj.conf` file:
**Workaround:** To free up flash space when debugging locally, uncomment the following Kconfig options in the :file:`prj.conf` file:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
**Workaround:** To free up flash space when debugging locally, uncomment the following Kconfig options in the :file:`prj.conf` file:
**Workaround:** To free up flash space when debugging locally, comment out the following Kconfig options in the :file:`prj.conf` file:

@greg-fer greg-fer force-pushed the doc_release_known_issue_update_230 branch from b86ad6a to 8856823 Compare March 1, 2023 08:39
Copy link
Contributor

@bama-nordic bama-nordic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM (Wi-Fi)

@greg-fer greg-fer force-pushed the doc_release_known_issue_update_230 branch from 8856823 to bb8a57a Compare March 1, 2023 09:09
Copy link
Contributor

@nvlsianpu nvlsianpu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add known issues not related to NCSDK-20046:
nrf/sample/ipc/ipc_service sample does not work as it is misconfigured

@greg-fer greg-fer force-pushed the doc_release_known_issue_update_230 branch from bb8a57a to a7ce01b Compare March 1, 2023 12:25
@greg-fer
Copy link
Contributor Author

greg-fer commented Mar 1, 2023

Can you add known issues not related to NCSDK-20046:

@nvlsianpu , what do you mean by "not related"?

Added v2.3.0 tag to known issues.
NCSDK-19916.

Signed-off-by: Grzegorz Ferenc <Grzegorz.Ferenc@nordicsemi.no>
@greg-fer greg-fer force-pushed the doc_release_known_issue_update_230 branch from a7ce01b to ea52764 Compare March 1, 2023 12:42
@greg-fer
Copy link
Contributor Author

greg-fer commented Mar 1, 2023

@nvlsianpu , please check.

@greg-fer greg-fer removed DNM changelog-entry-required Update changelog before merge. Remove label if entry is not needed or already added. labels Mar 1, 2023
@tmon-nordic tmon-nordic merged commit bea2d87 into nrfconnect:main Mar 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI-disable Disable CI for this PR doc-required PR must not be merged without tech writer approval.
Projects
None yet