Skip to content

Commit 59e2b14

Browse files
kkasperczyk-noArekBalysNordic
authored andcommitted
docs: Added Matter related known issue for NUS configuration
Added known issue related to BT RX stack overflow with 54LX + NUS combination. Signed-off-by: Kamil Kasperczyk <[email protected]>
1 parent 84963fb commit 59e2b14

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

doc/nrf/releases_and_maturity/known_issues.rst

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3351,6 +3351,16 @@ The issues in this section are related to :ref:`matter_samples`.
33513351

33523352
.. rst-class:: v3-1-1 v3-1-0
33533353

3354+
KRKNWK-20915: The :ref:`matter_lock_sample` sample does not work with the nRF54L Series and Nordic UART Service (NUS)
3355+
Using the Nordic UART Service (NUS) with the :ref:`matter_lock_sample` sample on the nRF54L Series devices results in a crash.
3356+
The root cause is that the NUS requires increased BT RX stack size for the nRF54L Series devices.
3357+
3358+
**Affected platforms:** nRF54L15, nRF54L10, nRF54LM20
3359+
3360+
**Workaround:** Set the :kconfig:option:`CONFIG_BT_RX_STACK_SIZE` Kconfig option to ``2560`` in the sample's :file:`prj.conf` file.
3361+
3362+
.. rst-class:: v3-1-1 v3-1-0
3363+
33543364
KRKNWK-20691: The :ref:`matter_lock_sample` sample does not update LED state on auto-relock
33553365
The sample does not update the LED state to on after auto-relock timeout.
33563366
The attribute value after auto-relock timeout is correct (locked), but the sample does not handle this change correctly, so the state of LED visualizing the lock state is wrong.

0 commit comments

Comments
 (0)