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
samples: matter: Change Lock Wi-Fi Thread Switching from 53 to 54LM
- Deprecated nRF5340 DK with the nRF7002 EK shield attached in
Matter Lock Thread and Wi-Fi switching variant.
- Added support for Thread and Wi-Fi switching for nRF54LM20 DK
with the nRF7002 EB2 shield attached.
- Updated sample.yml according these changes.
- Updated README.rst.
Signed-off-by: Arkadiusz Balys <[email protected]>
Copy file name to clipboardExpand all lines: samples/matter/lock/README.rst
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -96,14 +96,14 @@ Thread and Wi-Fi switching
96
96
97
97
.. toggle::
98
98
99
-
When built using the :ref:`switched Thread and Wi-Fi configuration <matter_lock_sample_custom_configs>` and programmed to the nRF5340 DK with the nRF7002 EK shield attached, the door lock sample supports a feature that allows you to :ref:`switch between Matter over Thread and Matter over Wi-Fi <ug_matter_overview_architecture_integration_designs_switchable>` at runtime.
99
+
When built using the :ref:`switched Thread and Wi-Fi configuration <matter_lock_sample_custom_configs>` and programmed to the nRF54LM20 DK with the nRF7002-EB II shield attached, the sample supports a feature that allows you to :ref:`switch between Matter over Thread and Matter over Wi-Fi <ug_matter_overview_architecture_integration_designs_switchable>` at runtime.
100
100
Due to Matter protocol limitations, a single Matter node can only use one transport protocol at a time.
101
101
102
102
The application is built with support for both Matter over Thread and Matter over Wi-Fi.
103
103
The device activates either Thread or Wi-Fi transport protocol on boot, based on a flag stored in the non-volatile memory on the device.
104
104
By default, Matter over Wi-Fi is activated.
105
105
106
-
You can trigger the switch from one transport protocol to the other using the **Button 3** on the nRF5340 DK.
106
+
You can trigger the switch from one transport protocol to the other using the **Button 3** on the nRF54LM20 DK.
107
107
This toggles the flag stored in the non-volatile memory, and then the device is factory reset and rebooted.
108
108
Because the flag is toggled, the factory reset does not switch the device back to the default transport protocol (Wi-Fi).
109
109
Instead, the factory reset and recommissioning to a Matter fabric allows the device to be provisioned with network credentials for the transport protocol that it was switched to, and to start operating in the selected network.
@@ -129,7 +129,7 @@ Matter Bluetooth LE with Nordic UART Service
129
129
130
130
If the device is already connected to the Matter network, the notification about changing the lock state will be sent to the Bluetooth controller.
131
131
132
-
Currently, the door lock's Bluetooth LE service extension with NUS is only available for the nRF52840 and the nRF5340 DKs in the :ref:`Matter over Thread <ug_matter_gs_testing>` network variant.
132
+
Currently, the door lock's Bluetooth LE service extension with NUS is only available for the sample in the :ref:`Matter over Thread <ug_matter_gs_testing>` network variant.
133
133
However, you can use the Bluetooth LE service extension regardless of whether the device is connected to a Matter over Thread network or not.
134
134
135
135
See `Enabling Matter Bluetooth LE with Nordic UART Service`_ and `Testing Bluetooth LE with Nordic UART Service`_ for more information about how to configure and test this feature with this sample.
@@ -208,7 +208,7 @@ The |matter_type| supports the following build configurations:
208
208
* - Switched Thread and Wi-Fi
209
209
- :file:`prj_thread_wifi_switched.conf`
210
210
- ``thread_wifi_switched``
211
-
- nRF5340 DK with the nRF7002 EK shield attached
211
+
- nRF54LM20 DK with the nRF7002-EB II shield attached
212
212
- Debug version of the application with the ability to :ref:`switch between Thread and Wi-Fi network support <matter_lock_sample_wifi_thread_switching>` in the field.
213
213
214
214
Advanced configuration options
@@ -292,7 +292,7 @@ Second Button:
292
292
* Changes the lock state to the opposite one.
293
293
294
294
Third Button:
295
-
* On the nRF5340 DK when using the :ref:`switched Thread and Wi-Fi configuration <matter_lock_sample_custom_configs>`: If pressed for more than ten seconds, it switches the Matter transport protocol from Thread or Wi-Fi to the other and factory resets the device.
295
+
* On the nRF54LM20 DK with the nRF7002-EB II shield attached when using the :ref:`switched Thread and Wi-Fi configuration <matter_lock_sample_custom_configs>`: If pressed for more than ten seconds, it switches the Matter transport protocol from Thread or Wi-Fi to the other and factory resets the device.
296
296
* On other platform or configuration: Not available.
You can only test :ref:`matter_lock_sample_wifi_thread_switching` on the nRF5340 DK with the nRF7002 EK shield attached, using the :ref:`switched Thread and Wi-Fi configuration <matter_lock_sample_custom_configs>`.
557
+
You can only test :ref:`matter_lock_sample_wifi_thread_switching` on the nRF54LM20 DK with the nRF7002-EB II shield attached, using the :ref:`switched Thread and Wi-Fi configuration <matter_lock_sample_custom_configs>`.
558
558
559
559
To test this feature, complete the following steps:
560
560
561
561
#. Build the door lock application using the switched Thread and Wi-Fi configuration:
562
562
563
563
.. code-block:: console
564
564
565
-
west build -b nrf5340dk/nrf5340/cpuapp -- -DFILE_SUFFIX=thread_wifi_switched -Dlock_SHIELD=nrf7002ek -DSB_CONFIG_WIFI_NRF70=y
565
+
west build -b nrf54lm20dk/nrf54lm20a/cpuapp -- -DFILE_SUFFIX=thread_wifi_switched -Dlock_SHIELD=nrf7002eb2 -DSB_CONFIG_WIFI_NRF70=y
566
566
567
567
#. Prepare the development kit for testing.
568
568
Refer to the :ref:`matter_lock_sample_testing_start` section for more information.
0 commit comments