Skip to content

Commit

Permalink
doc: matter: Add a known issue about the nRF53 network crash
Browse files Browse the repository at this point in the history
Added the known issue for KRKNWK-12467 for v2.4.0 & v2.3.0.

Signed-off-by: Arkadiusz Balys <arkadiusz.balys@nordicsemi.no>
  • Loading branch information
ArekBalysNordic authored and cvinayak committed Jun 21, 2023
1 parent d4aa226 commit e434ec2
Showing 1 changed file with 11 additions and 0 deletions.
11 changes: 11 additions & 0 deletions doc/nrf/known_issues.rst
Original file line number Diff line number Diff line change
Expand Up @@ -278,6 +278,17 @@ Matter

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

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

KRKNWK-12467: Application core can crash on nRF5340 when there is a high load on Zephyr's main thread
The priority of Zephyr's main thread is set to the same value as the IPC thread's priority (``0``).
Because of this setting, when Zephyr's main thread is working for a long time, an interrupt related to the IEEE 802.15.4 radio driver can occur and the application core can crash due to a lack of communication with the network core.
To avoid blocking the communication between cores, the main thread priority should have a lower priority than the IPC priority.

**Affected platforms:** nRF5340

**Workaround:** Add an additional Kconfig option :kconfig:option:`CONFIG_MAIN_THREAD_PRIORITY` set to ``1`` to the build configuration.

.. rst-class:: v2-4-0

KRKNWK-17064: Incorrect links in the Matter documentation
Expand Down

0 comments on commit e434ec2

Please sign in to comment.