Matter integration in the nRF Connect SDK
Matter is included in the nRF Connect SDK as one of the submodule repositories managed with the West (Zephyr’s meta-tool) tool, using a dedicated Matter fork. That is, the code used for the nRF Connect SDK and Matter integration is stored in the Matter repository (nRF Connect platform) and is compiled when building one of the available Matter samples.
The nRF Connect SDK repository structure
Both instances depend on each other, but their development is independent to ensure that they both support the latest stable version of one another. The fork is maintained and verified as a part of the nRF Connect SDK release process as an OSS repository.
The Matter repository fetched into the fork also includes documentation files. A selection of these pages is included in the nRF Connect SDK documentation under the Matter documentation tab.
Matter stack in the nRF Connect SDK
Matter is located on the top application layer of the integration model, looking from the networking point of view. The nRF Connect SDK and Zephyr provide the Bluetooth® LE, Thread, and Wi-Fi® stacks, which must be integrated with the Matter stack using a special intermediate layer. In case of Matter over Thread, the nRF Connect SDK’s Multiprotocol Service Layer (MPSL) driver allows running Bluetooth LE and Thread concurrently on the same radio chip.
nRF Connect platform in Matter
For detailed description, see the nRF Connect platform overview page in the Matter documentation.
Matter platform designs (System-on-Chip, multiprotocol)
Matter in the nRF Connect SDK supports the System-on-Chip, multiprotocol platform designs, available with the related network stack on Nordic Semiconductor devices in the nRF Connect SDK. For more information about the multiprotocol feature, see Multiprotocol support.
Matter over Thread
In this design, the Matter stack, the OpenThread stack, and the Bluetooth LE stack run on a single SoC.
This platform design is suitable for the following development kits:
Hardware platforms |
PCA |
Board name |
|
|---|---|---|---|
PCA10056 |
|
||
PCA10095 |
|
||
PCA10156 |
|
||
PCA10184 |
|
||
PCA10184 |
|
The design differences between the supported SoCs are the following:
On the nRF5340, SoC the network core runs both the Bluetooth LE Controller and the 802.15.4 IEEE Radio Driver.
On the nRF52840, nRF54L15 and nRF54LM20 SoCs, all components are located on the application core.
Multiprotocol Thread and Bluetooth LE architecture on nRF52 Series and nRF54L Series devices
Multiprotocol Thread and Bluetooth LE architecture on nRF53 Series devices
Matter over Wi-Fi
In this design, the Matter stack, the Wi-Fi stack, and the Bluetooth LE stack run on a single SoC.
This platform design is suitable for the following development kits:
Hardware platforms |
PCA |
Board name |
|
|---|---|---|---|
PCA10184 |
|
||
PCA10184 |
|
For this design, the Wi-Fi driver on the application core communicates with the external nRF7002 Wi-Fi 6 Companion IC over SPI:
For the
nrf54lm20dk/nrf54lm20b/cpuapp(nrf54lm20aSoC is also supported), nRF7002 support is added using thenrf7002eb2shield connected through SPI.
Multiprotocol Wi-Fi and Bluetooth LE architecture (nRF54LM20 with the nRF7002)
Switchable Matter over Wi-Fi and Matter over Thread
In this design, the Matter stack, the OpenThread stack, the Wi-Fi stack, and the Bluetooth LE stack run on a single SoC. For an example of how this design works, see the nRF Door Lock and Access Control Add-on. This platform design is suitable for the following development kits:
Hardware platforms |
PCA |
Board name |
|
|---|---|---|---|
PCA10184 |
|
||
PCA10184 |
|
This design is only available for the nrf54lm20dk/nrf54lm20b/cpuapp board target (nrf54lm20a is also supported).
The Wi-Fi driver on the application core communicates through SPI with the external nRF7002-EB II shield, which works as the Wi-Fi 6 Companion IC.
Multiprotocol Wi-Fi/Thread and Bluetooth LE architecture (nRF54LM20 with the nRF7002-EB II shield as the Wi-Fi 6 Companion IC)