You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/nrf/protocols/matter/end_product/security.rst
+14-2Lines changed: 14 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -81,9 +81,9 @@ An important setting, that depends on the hardware platform in use, is the way o
81
81
The recommended and the most secure option is to use :ref:`lib_hw_unique_key` (HUK) library.
82
82
HUK support is automatically enabled with the :kconfig:option:`CONFIG_TRUSTED_STORAGE_BACKEND_AEAD_KEY_DERIVE_FROM_HUK` Kconfig option for compatible configurations.
83
83
84
-
The HUK library is supported for the nRF52840, nRF5340, and nRF54L15 platforms, but for :ref:`matter_samples` in the |NCS|, it is only enabled for the nRF5340 and NRF54L15 platforms:
84
+
The HUK library is supported for the nRF52840, nRF5340, and nRF54L platforms, but for :ref:`matter_samples` in the |NCS|, it is only enabled for the nRF5340 and nRF54L platforms:
85
85
86
-
* For the nRF5340 and nRF54L15 platforms, the HUK is generated at first boot and stored in the Key Management Unit (KMU).
86
+
* For the nRF5340, nRF54L platforms, the HUK is generated at first boot and stored in the Key Management Unit (KMU).
87
87
No changes to the existing partition layout are needed for products in the field.
88
88
* For the nRF54L15 NS platform, the HUK generation and management is handled by the Trusted Firmware-M (TF-M) library.
89
89
* For the nRF52840 platform, AEAD keys are derived with a SHA-256 hash (:kconfig:option:`CONFIG_TRUSTED_STORAGE_BACKEND_AEAD_KEY_HASH_UID`).
@@ -143,6 +143,13 @@ This is a reference configuration that can be modified in the production firmwar
143
143
- CRACEN
144
144
- Yes
145
145
- Trusted Firmware-M (TF-M) + Key Management Unit (KMU)
If you migrate the DAC private key to storage based on Zephyr Settings storage, you cannot use the :kconfig:option:`CONFIG_CHIP_FACTORY_RESET_ERASE_SETTINGS` Kconfig option.
198
210
This is because the factory reset feature will erase the secure storage, including the DAC private key, which has been removed from the factory data.
Copy file name to clipboardExpand all lines: doc/nrf/protocols/matter/getting_started/hw_requirements.rst
+46-11Lines changed: 46 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,6 +20,7 @@ Currently the following SoCs from Nordic Semiconductor are supported for use wit
20
20
* :ref:`nRF5340 + nRF7002 <programming_board_names>` (Matter over Thread and Matter over Wi-Fi)
21
21
* :ref:`nRF52840 <programming_board_names>` (Matter over Thread)
22
22
* :ref:`nRF54L15 <programming_board_names>` (Matter over Thread)
23
+
* :ref:`nRF54L10 <programming_board_names>` (Matter over Thread)
23
24
24
25
Front-End Modules
25
26
=================
@@ -32,9 +33,13 @@ For more information about the FEM support in the |NCS|, see :ref:`ug_radio_fem`
32
33
External flash
33
34
**************
34
35
35
-
For the currently supported SoCs, you must use an external memory with at least 1 MB of flash for nRF52840 and 1.5MB for nRF5340.
36
+
For the currently supported SoCs, you must use an external memory with at least 1 MB of flash for nRF52840 and nRF54L10, and 1.5 MB for nRF5340 and nRF54L15.
36
37
This is required to perform the DFU operation.
37
38
39
+
.. note::
40
+
The nRF54L15 supports DFU with image compression, which may eliminate the need for external flash.
41
+
For more details, see :ref:`mcuboot_image_compression`.
42
+
38
43
The development kits for the supported SoCs from Nordic Semiconductor are supplied with the MX25R64 type of external flash that meets these memory requirements.
39
44
However, it is possible to configure the SoCs with different QSPI or SPI memory if it is supported by Zephyr.
40
45
For this purpose, check the reference design for Nordic DKs for information about how to connect the external memory with SoC, specifically whether the pins are designed for the QSPI or the high-speed SPIM operations.
@@ -214,6 +219,7 @@ Values are provided in kilobytes (KB).
214
219
.. tab:: nRF54L15 DK
215
220
216
221
The following table lists memory requirements for samples running on the :ref:`nRF54L15 DK <programming_board_names>` (:ref:`nrf54l15dk/nrf54l15/cpuapp <zephyr:nrf54l15dk_nrf54l15>`).
222
+
You can use the table as a reference for the :ref:`nRF54L15 DK (emulating nRF54L10) <programming_board_names>` (:ref:`nrf54l15dk/nrf54l10/cpuapp <zephyr:nrf54l15dk_nrf54l15>`).
The following memory map is valid for Matter applications running on the :ref:`nRF54L15 DK (emulating nRF54L10) <programming_board_names>` (:ref:`nrf54l15dk/nrf54l10/cpuapp <zephyr:nrf54l15dk_nrf54l15>`).
You can generate :ref:`Partition Manager's ASCII representation <pm_partition_reports>` of these tables by running the following command for your respective *board_target*:
Copy file name to clipboardExpand all lines: samples/matter/template/README.rst
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,7 @@ IPv6 network support
32
32
33
33
The development kits for this sample offer the following IPv6 network support for Matter:
34
34
35
-
* Matter over Thread is supported for ``nrf52840dk/nrf52840``, ``nrf5340dk/nrf5340/cpuapp``, ``nrf21540dk/nrf52840``, ``nrf54l15dk/nrf54l15/cpuapp``, and ``nrf54h20dk/nrf54h20/cpuapp``.
35
+
* Matter over Thread is supported for ``nrf52840dk/nrf52840``, ``nrf5340dk/nrf5340/cpuapp``, ``nrf21540dk/nrf52840``, ``nrf54l15dk/nrf54l15/cpuapp``, ``nrf54l15dk/nrf54l10/cpuapp``, and ``nrf54h20dk/nrf54h20/cpuapp``.
36
36
* Matter over Wi-Fi is supported for ``nrf5340dk/nrf5340/cpuapp`` or ``nrf54h20dk/nrf54h20/cpuapp`` with the ``nrf7002ek`` shield attached, or for ``nrf7002dk/nrf5340/cpuapp``.
0 commit comments