doc: Update known issues for NCS 3.2.0 #25844

peknis · 2025-11-27T08:09:24Z

Added v3-2-0 to known issues

NordicBuilder · 2025-11-27T08:14:51Z

CI Information

^{To view the history of this post, click the 'edited' button above}
Build number: 28

Inputs:

Sources:

more details

Github labels

Enabled	Name	Description
	ci-disabled	Disable the ci execution
	ci-all-test	Run all of ci, no test spec filtering will be done
	ci-force-downstream	Force execution of downstream even if twister fails
	ci-run-twister	Force run twister
	ci-run-zephyr-twister	Force run zephyr twister

List of changed files detected by CI (0)

Outputs:

Toolchain

Version:
Build docker image:

Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped; ⚠️ Quarantine

◻️ Toolchain
◻️ Build twister
◻️ Integration tests

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

divipillai · 2025-12-05T11:40:45Z

doc/nrf/releases_and_maturity/known_issues.rst

+.. rst-class:: v3-2-0 v3-1-1 v3-1-0 v3-0-2 v3-0-1 v3-0-0 v2-9-0-nRF54H20-1 v2-9-2 v2-9-1 v2-9-0 v2-8-0 v2-7-0 v2-6-4 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0
+
+OCT-3490: Connection pointer unfeferenced and then used
+  In the :file:`bt_mgmt.c´ file, the connection pointer for ``disconnected_cb`` might be unreferenced before being sent over zbus.


Suggested change

In the :file:`bt_mgmt.c´ file, the connection pointer for ``disconnected_cb`` might be unreferenced before being sent over zbus.

In the :file:`bt_mgmt.c` file, the connection pointer for ``disconnected_cb`` might be unreferenced before being sent over zbus.

umapraseeda · 2025-12-05T13:37:03Z

doc/nrf/releases_and_maturity/known_issues.rst

+  If the application tries to bond with the same peer again without reboot, the Host will print the error message "Failed" to add IRK to the controller.
+  This issue is highly likely to happen if the application calls the :c:func:`bt_unpair` function right after :c:func:`settings_load`.
+
+  **Workaround:** Insert a delay (``k_sleep()``) of a few hundreed milliseconds before calling the :c:func:`bt_unpair` function.


Suggested change

**Workaround:** Insert a delay (``k_sleep()``) of a few hundreed milliseconds before calling the :c:func:`bt_unpair` function.

**Workaround:** Insert a delay (``k_sleep()``) of a few hundred milliseconds before calling the :c:func:`bt_unpair` function.

umapraseeda · 2025-12-05T13:38:15Z

doc/nrf/releases_and_maturity/known_issues.rst

+.. rst-class:: v3-1-1 v3-1-0 v3-0-2 v3-0-1 v3-0-0
+
+NCSDK-36539: Assertion in Host when UART driver is used
+  When using the Bluetooth Host over HCI UART and the `:kconfig:option:`CONFIG_ASSERT` Kconfig option is enabled, an assertion can occur.


Suggested change

When using the Bluetooth Host over HCI UART and the `:kconfig:option:`CONFIG_ASSERT` Kconfig option is enabled, an assertion can occur.

When using the Bluetooth Host over HCI UART and the :kconfig:option:`CONFIG_ASSERT` Kconfig option is enabled, an assertion can occur.

umapraseeda · 2025-12-05T13:38:40Z

doc/nrf/releases_and_maturity/known_issues.rst

+
+.. rst-class:: v3-0-2 v3-0-1 v3-0-0 v2-9-0-nRF54H20-1 v2-9-2 v2-9-1 v2-9-0 v2-8-0 v2-7-0

 NCSDK-33631: Preemptible ``bt_gatt_notify`` assert


Suggested change

NCSDK-33631: Preemptible ``bt_gatt_notify`` assert

NCSDK-33631: Preemptible ``bt_gatt_notify()`` assert

umapraseeda · 2025-12-05T13:46:01Z

doc/nrf/releases_and_maturity/known_issues.rst


+.. rst-class:: v3-2-0 v3-1-1 v3-1-0 v3-0-2 v3-0-1 v3-0-0 v2-9-0-nRF54H20-1 v2-9-2 v2-9-1 v2-9-0 v2-8-0 v2-7-0 v2-6-4 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0
+
+OCT-3490: Connection pointer unfeferenced and then used


Suggested change

OCT-3490: Connection pointer unfeferenced and then used

OCT-3490: Connection pointer unreferenced and then used

umapraseeda · 2025-12-05T13:50:03Z

doc/nrf/releases_and_maturity/known_issues.rst

+.. rst-class:: v3-2-0
+
+NCSDK-34929: The :ref:`nrf_compression_mcuboot_compressed_update` sample does work correctly on nRF54H20
+  After updating a compressed image for app/radio slot, MCUBoot fails to verify the start address of the binary.


Suggested change

After updating a compressed image for app/radio slot, MCUBoot fails to verify the start address of the binary.

After updating a compressed image for app/radio slot, MCUboot fails to verify the start address of the binary.

umapraseeda · 2025-12-05T13:53:34Z

doc/nrf/releases_and_maturity/known_issues.rst


  **Affected platforms:** nRF9160, nRF9161, nRF9151

  ** Workaround:** Apply the fix from `sdk-nrf PR #16242`_.


Suggested change

** Workaround:** Apply the fix from `sdk-nrf PR #16242`_.

**Workaround:** Apply the fix from `sdk-nrf PR #16242`_.

umapraseeda · 2025-12-05T13:54:44Z

doc/nrf/releases_and_maturity/known_issues.rst


+.. rst-class:: v3-2-0 v3-1-1 v3-1-0 v3-0-2 v3-0-1 v3-0-0 v2-9-0-nRF54H20-1 v2-9-2 v2-9-1 v2-9-0 v2-8-0 v2-7-0
+
+NCSDK-35089: Combination of NSIB, MCUBoot with encrypted images or external flash does not work properly (also NCSIDB-1173)


Suggested change

NCSDK-35089: Combination of NSIB, MCUBoot with encrypted images or external flash does not work properly (also NCSIDB-1173)

NCSDK-35089: Combination of NSIB, MCUboot with encrypted images or external flash does not work properly (also NCSIDB-1173)

umapraseeda · 2025-12-05T13:57:56Z

doc/nrf/releases_and_maturity/known_issues.rst

  **Workaround:** Enable protection manually using the :kconfig:option:`CONFIG_FPROTECT` and  :kconfig:option:`CONFIG_FPROTECT_ALLOW_COMBINED_REGIONS` Kconfig options of MCUboot.

-.. rst-class:: wontfix v3-1-1 v3-1-0 v3-0-2 v3-0-1 v3-0-0
+.. rst-class:: wontfix v3-2-0 v3-1-1 v3-1-0 v3-0-2 v3-0-1 v3-0-0


Line 4569: MCUBoot's -> MCUboot's

umapraseeda · 2025-12-05T14:05:44Z

doc/nrf/releases_and_maturity/known_issues.rst

 CVE-2023-2626: OpenThread KeyID Mode 2 Security Vulnerability
  This vulnerability impacts all Thread devices using OpenThread and allows an attacker in physical proximity to compromise non-router-capable devices and the entire Thread network in the case of router-capable devices.
-  The vulnerability allows an attacker in physical proximity to inject arbitrary IPv6 packets into the Thread network via IEEE 802.15.4 frame transmissions.
+  The vulnerability allows an attacker in physical proximity to inject arbitrary IPv6 packets into the Thread network through IEEE 802.15.4 frame transmissions.


Line 1363: This issue only affects to Thread 1.2 builds. -> This issue only affects Thread 1.2 builds.

umapraseeda · 2025-12-05T14:15:13Z

doc/nrf/releases_and_maturity/known_issues.rst

+  After updating a compressed image for app/radio slot, MCUBoot fails to verify the start address of the binary.
+
+  **Affected platforms:** nRF54H20
+


Line 3684: This PSK can be obtain from the carrier. -> This PSK can be obtained from the carrier.

MarekPieta · 2025-12-05T15:18:46Z

One more nRF Desktop known issue to be added:

.. rst-class:: v3-2-0                                                                         

NCSDK-36662: The :ref:`nrf_desktop_battery_meas` uses invalid ADC driver configuration
  The used ADC input is invalid because of configuration misalignment after switching to nrfx 4.0.
  This may result in silently using an invalid pin as input or :c:func:`adc_channel_setup` function call errors which lead to an application module fatal error state right after boot.

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

Hi @peknis,
The fix was eventually backported to NCS 3.2.0. Please remove the known issue. Sorry for the noise.

umapraseeda · 2025-12-08T09:09:15Z

doc/nrf/releases_and_maturity/known_issues.rst

-  You may encounter the following errors:
+KRKNWK-20948: The Matter west :ref:`ug_matter_gs_tools_matter_west_commands_zap_tool_generate` command might not work properly on Windows
+  The matter west ``zap-generate`` command might return several errors when using it on Windows with the ``--full`` option.
+  You might encounter the following errors:


Line 699: KRKNWK-20308: The ``MyCluster.xml`` file -> KRKNWK-20308: The :file:`MyCluster.xml` file

henrla · 2025-12-08T12:01:50Z

doc/nrf/releases_and_maturity/known_issues.rst

  **Affected platforms:** nRF54L15, nRF54L10, nRF54L05

  **Workaround:** Increase the configured HFXO startup time to 1650 microseconds.



Need to add the following known issue under Multiprotocol Service Layer (MPSL):

`.. rst-class:: v3.2.0

DRGN-27120: MPSL pin debug radio has an out of bounds array access. This error applies if :kconfig:option:CONFIG_MPSL_HFCLK_LATENCY is set.

Affected platforms: nRF52832, nRF52833, nRF52820, nRF52811, nRF52810, nRF5340

Workaround: Fix the out of bounds access of the array.
`

Added, but is that really a workaround, if the issue is out of bounds array access?

I see your point, I just followed the structure, but maybe it doesn't work well for this known issue entry. I'm happy with any suggestion you have to communicate that the issue is fixable by the user since the issue is public/in nrf.

Can we refer to other pull-requests or commits in a workaround?
This PR merged a fix to main: https://github.com/nrfconnect/sdk-nrf/pull/26139/files

This commit should apply cleanly to the release branch, or at least give enough information for someone to implement the workaround.

Referred to that PR in the Workaround now. See line 5023.

henrla · 2025-12-08T13:02:36Z

doc/nrf/releases_and_maturity/known_issues.rst

+.. rst-class:: v3-2-0 v3-1-1 v3-1-0 v3-0-2 v3-0-1 v3-0-0 v2-9-0-nRF54H20-1 v2-9-2 v2-9-1 v2-9-0 v2-8-0 v2-7-0 v2-6-4 v2-6-3 v2-6-2 v2-6-1 v2-6-0 v2-5-3 v2-5-2 v2-5-1 v2-5-0 v2-4-4 v2-4-3 v2-4-2 v2-4-1 v2-4-0 v2-3-0 v2-2-0 v2-1-4 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

 DRGN-16013: Initiating connections over extended advertising is not supported when external radio coexistence and FEM support are enabled
  The initiator can assert when initiating a connection to an extended advertiser when both external radio coexistence and FEM are enabled.


After having reviewed this jira, I think it should be updated to the following:

DRGN-16013: Initiating connections over extended advertising is not supported when external radio coexistence and FEM support are enabled and the secondary PHY is CODED The initiator can assert when initiating a connection to an extended advertiser when both external radio coexistence and FEM are enabled, and the secondary PHY is CODED, and the whitelist and the resolving lists are full. **Workaround:** Do not enable both coex (:kconfig:option:`CONFIG_MPSL_CX_BT`) and FEM (:kconfig:option:`CONFIG_MPSL_FEM`) when support for extended advertising packets is enabled (:kconfig:option:`CONFIG_BT_EXT_ADV`), and use CODED as secondary PHY.

kapi-no · 2025-12-08T13:24:50Z

doc/nrf/releases_and_maturity/known_issues.rst

 The issues in this section are related to the :ref:`ug_nfc` protocol.

-.. rst-class: v3-1-1 v3-1-0 v3-0-2 v3-0-1 v3-0-0 v2-9-0-nRF54H20-1 v2-9-2 v2-9-1 v2-9-0 v2-8-0 v2-7-0
+.. rst-class:: v3-2-0 v3-1-1 v3-1-0 v3-0-2 v3-0-1 v3-0-0 v2-9-0-nRF54H20-1 v2-9-2 v2-9-1 v2-9-0 v2-8-0 v2-7-0


@maje-emb, isn't it fixed? at least for the nRF54L series?

For nrf54L15, this is fixed.
For nrf54H20, this is still relevant.

Should we then remove nRF54L15 from the texts and affected platforms? Then again, it would be wrong then for the older releases.

doc/nrf/releases_and_maturity/known_issues.rst

jostn · 2025-12-09T14:28:00Z

doc/nrf/releases_and_maturity/known_issues.rst

-DRGN-16013: Initiating connections over extended advertising is not supported when external radio coexistence and FEM support are enabled
-  The initiator can assert when initiating a connection to an extended advertiser when both external radio coexistence and FEM are enabled.
+DRGN-16013: Initiating connections over extended advertising is not supported when external radio coexistence and FEM support are enabled and the secondary PHY is CODED
+  The initiator can assert when initiating a connection to an extended advertiser when both external radio coexistence and FEM are enabled, and the secondary PHY is CODED, and the whitelist and the resolving lists are full.


Sorry, we need an update here again:
"The initiator can assert when initiating a connection to an extended advertiser when both external radio coexistence and FEM are enabled, and the secondary PHY is CODED."

Added v3-2-0 to known issues Signed-off-by: Pekka Niskanen <[email protected]>

peknis requested a review from a team as a code owner November 27, 2025 08:09

NordicBuilder added doc-required PR must not be merged without tech writer approval. changelog-entry-required Update changelog before merge. Remove label if entry is not needed or already added. labels Nov 27, 2025

peknis added 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 Nov 27, 2025

divipillai approved these changes Dec 5, 2025

View reviewed changes

peknis force-pushed the known_issues_320 branch from 7a3a093 to 62ede12 Compare December 5, 2025 11:59

mariusz-nordicsemi approved these changes Dec 5, 2025

View reviewed changes

umapraseeda requested changes Dec 5, 2025

View reviewed changes

peknis force-pushed the known_issues_320 branch from 62ede12 to fb60ef4 Compare December 8, 2025 06:24

peknis requested a review from umapraseeda December 8, 2025 06:24

umapraseeda approved these changes Dec 8, 2025

View reviewed changes

henrla self-requested a review December 8, 2025 10:16

henrla reviewed Dec 8, 2025

View reviewed changes

peknis force-pushed the known_issues_320 branch from fb60ef4 to 5afb30d Compare December 8, 2025 12:44

peknis requested a review from henrla December 8, 2025 12:45

henrla reviewed Dec 8, 2025

View reviewed changes

peknis force-pushed the known_issues_320 branch from 5afb30d to f20aa5e Compare December 8, 2025 13:13

peknis requested a review from henrla December 8, 2025 13:14

kapi-no approved these changes Dec 8, 2025

View reviewed changes

peknis requested a review from maje-emb December 9, 2025 09:06

peknis mentioned this pull request Dec 9, 2025

known issues: 'ffff' in key hash #26161

Closed

peknis force-pushed the known_issues_320 branch from f20aa5e to b8de841 Compare December 9, 2025 10:31

michalek-no approved these changes Dec 9, 2025

View reviewed changes

SeppoTakalo approved these changes Dec 9, 2025

View reviewed changes

tomchy reviewed Dec 9, 2025

View reviewed changes

doc/nrf/releases_and_maturity/known_issues.rst Show resolved Hide resolved

doc/nrf/releases_and_maturity/known_issues.rst Show resolved Hide resolved

doc/nrf/releases_and_maturity/known_issues.rst Show resolved Hide resolved

peknis force-pushed the known_issues_320 branch from b8de841 to d476081 Compare December 9, 2025 13:06

peknis requested a review from tomchy December 9, 2025 13:11

peknis force-pushed the known_issues_320 branch from d476081 to cdddafe Compare December 9, 2025 13:14

jostn reviewed Dec 9, 2025

View reviewed changes

peknis requested a review from jostn December 10, 2025 06:31

osaether approved these changes Dec 10, 2025

View reviewed changes

doc: Update known issues for NCS 3.2.0

5bced8c

Added v3-2-0 to known issues Signed-off-by: Pekka Niskanen <[email protected]>

peknis force-pushed the known_issues_320 branch from cdddafe to 5bced8c Compare December 10, 2025 07:11

	In the :file:`bt_mgmt.c´ file, the connection pointer for ``disconnected_cb`` might be unreferenced before being sent over zbus.
	In the :file:`bt_mgmt.c` file, the connection pointer for ``disconnected_cb`` might be unreferenced before being sent over zbus.

	Workaround: Insert a delay (``k_sleep()``) of a few hundreed milliseconds before calling the :c:func:`bt_unpair` function.
	Workaround: Insert a delay (``k_sleep()``) of a few hundred milliseconds before calling the :c:func:`bt_unpair` function.

	When using the Bluetooth Host over HCI UART and the `:kconfig:option:`CONFIG_ASSERT` Kconfig option is enabled, an assertion can occur.
	When using the Bluetooth Host over HCI UART and the :kconfig:option:`CONFIG_ASSERT` Kconfig option is enabled, an assertion can occur.


		.. rst-class:: v3-0-2 v3-0-1 v3-0-0 v2-9-0-nRF54H20-1 v2-9-2 v2-9-1 v2-9-0 v2-8-0 v2-7-0

		NCSDK-33631: Preemptible ``bt_gatt_notify`` assert


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

		OCT-3490: Connection pointer unfeferenced and then used

	OCT-3490: Connection pointer unfeferenced and then used
	OCT-3490: Connection pointer unreferenced and then used

	After updating a compressed image for app/radio slot, MCUBoot fails to verify the start address of the binary.
	After updating a compressed image for app/radio slot, MCUboot fails to verify the start address of the binary.


		Affected platforms: nRF9160, nRF9161, nRF9151

		Workaround: Apply the fix from `sdk-nrf PR #16242`_.

	Workaround: Apply the fix from `sdk-nrf PR #16242`_.
	Workaround: Apply the fix from `sdk-nrf PR #16242`_.


		.. rst-class:: v3-2-0 v3-1-1 v3-1-0 v3-0-2 v3-0-1 v3-0-0 v2-9-0-nRF54H20-1 v2-9-2 v2-9-1 v2-9-0 v2-8-0 v2-7-0

		NCSDK-35089: Combination of NSIB, MCUBoot with encrypted images or external flash does not work properly (also NCSIDB-1173)

		After updating a compressed image for app/radio slot, MCUBoot fails to verify the start address of the binary.

		Affected platforms: nRF54H20

		Affected platforms: nRF54L15, nRF54L10, nRF54L05

		Workaround: Increase the configured HFXO startup time to 1650 microseconds.

doc: Update known issues for NCS 3.2.0 #25844

Are you sure you want to change the base?

doc: Update known issues for NCS 3.2.0 #25844

Conversation

peknis commented Nov 27, 2025 • edited by osaether Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

NordicBuilder commented Nov 27, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

CI Information

Inputs:

Sources:

Github labels

Outputs:

Toolchain

Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped; ⚠️ Quarantine

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

MarekPieta commented Dec 5, 2025

Uh oh!

umapraseeda Dec 8, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

peknis Dec 8, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

20 participants

peknis commented Nov 27, 2025 •

edited by osaether

Loading

NordicBuilder commented Nov 27, 2025 •

edited

Loading

umapraseeda Dec 8, 2025 •

edited

Loading

peknis Dec 8, 2025 •

edited

Loading