diff --git a/doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst b/doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst index dce887f095b3..ab216445e54a 100644 --- a/doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst +++ b/doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst @@ -788,6 +788,10 @@ Wi-Fi samples that used :ref:`zephyr:bluetooth-hci-ipc-sample` or :ref:`zephyr:n * Added the :ref:`wifi_promiscuous_sample` sample that demonstrates how to set Promiscuous mode, establish a connection to an Access Point (AP), analyze incoming Wi-Fi packets, and print packet statistics. +* :ref:`wifi_station_sample` sample: + + * Modified to verify Wi-Fi readiness using the :ref:`wifi_ready` library. + Other samples ------------- @@ -907,6 +911,12 @@ Libraries for networking * Function :c:func:`wifi_credentials_is_empty` to check if the Wi-Fi credentials storage is empty. * New parameter ``channel`` to the structure :c:struct:`wifi_credentials_header` to store the channel information of the Wi-Fi network. +* Added the :ref:`lib_wifi_ready` library that manages Wi-Fi readiness for applications by handling supplicant ready and not ready events. + +* :ref:`lib_wifi_ready` library: + + * Notifies applications of Wi-Fi readiness by managing supplicant events, indicating when Wi-Fi is available for use. + * :ref:`lib_nrf_cloud` library: * Added: diff --git a/samples/wifi/sta/README.rst b/samples/wifi/sta/README.rst index e6248490d329..96850036dc63 100644 --- a/samples/wifi/sta/README.rst +++ b/samples/wifi/sta/README.rst @@ -23,6 +23,9 @@ The sample can perform Wi-Fi operations such as connect and disconnect in the 2. Using this sample, the development kit can connect to the specified access point in :abbr:`STA (Station)` mode. +The sample uses the :ref:`wifi_ready` library to check Wi-Fi readiness. +To use the :ref:`wifi_ready` library, enable the :kconfig:option:`CONFIG_WIFI_READY_EVENT_HANDLING` Kconfig option. + User interface ************** @@ -105,7 +108,7 @@ Testing |test_sample| -#. |connect_kit| +1. |connect_kit| #. |connect_terminal| The sample shows the following output: @@ -180,6 +183,30 @@ Testing [00:00:07.720,245] sta: RSSI: -57 [00:00:07.720,245] sta: Static IP address: +RPU recovery +************ + +The RPU recovery mechanism is used to recover from the RPU (nRF70) hang. +This feature performs an interface reset (down and up), which triggers an RPU cold boot. +Application's network connection will be lost during the recovery process, and it is application's responsibility to re-establish the network connection. + +Testing +======= + +To test RPU recovery, build the sample with the :kconfig:option:`CONFIG_SHELL` and :kconfig:option:`CONFIG_NRF700X_UTIL` Kconfig options. + +Trigger RPU recovery using the following command: + +.. code-block:: console + + wifi_util rpu_recovery_test + +If RPU recovery is triggered, you should see an output similar to the following: + +.. code-block:: console + + RPU recovery triggered + Power management testing ************************