This sample can perform Wi-Fi operations such as connect and disconnect in the 2.4GHz and 5GHz bands depending on the capabilities of an access point.
The sample also adds LED support to map with connection and disconnection events:
LED1 starts blinking when the sample is connected to the access point.
LED1 stops blinking when the sample is disconnected from the access point.
Using this sample, the development kit can connect to the specified access point in STA mode.
This sample demonstrates QSPI encryption API usage, the key can be set by the CONFIG_NRF700X_QSPI_ENCRYPTION_KEY Kconfig option.
If encryption of the QSPI traffic is required for the production devices, then matching keys must be programmed in both the nRF7002 OTP and non-volatile storage associated with the host.
The key from non-volatile storage must be set as the encryption key using the APIs.
This sample also enables Zephyr’s power management policy by default, which puts the nRF5340 System on Chip (SoC) into low-power mode whenever it is idle.
See Power Management in the Zephyr documentation for more information on power management.
The sample uses DHCP to obtain an IP address for the Wi-Fi interface. It starts with a default static IP address to handle networks without DHCP servers, or if the DHCP server is not available.
Successful DHCP handshake will override the default static IP configuration.
The following static configuration is by default and can be changed in the prj.conf file:
This sample can be found under samples/wifi/sta in the nRF Connect SDK folder structure.
When built as firmware image for the _ns build target, the sample has Cortex-M Security Extensions (CMSE) enabled and separates the firmware between Non-Secure Processing Environment (NSPE) and Secure Processing Environment (SPE).
Because of this, it automatically includes the Trusted Firmware-M (TF-M).
To read more about CMSE, see Processing environments.
After programming the sample to your development kit, complete the following steps to test it:
Connect the kit to the computer using a USB cable.
The kit is assigned a COM port (Windows) or ttyACM device (Linux), which is visible in the Device Manager.
Connect to the kit with a terminal emulator (for example, PuTTY).
See How to connect with PuTTY for the required settings.
This sample can be used to measure current consumption of both the nRF5340 SoC and nRF7002 device independently by using two separate Power Profiler Kit II’s (PPK2’s).
The nRF5340 SoC is connected to the first PPK2 and the nRF7002 DK is connected to the second PPK2.
