Exercise 1 – Connecting to Wi-Fi using the Wi-Fi shell
In this exercise, we will flash the Wi-Fi: Shell sample to your board. This sample allows you to send commands to the Wi-Fi chipset on your board through a command-line interface (see Supported CLI commands).
We will use the CLI to do various common Wi-Fi operations, such as a Wi-Fi scan, connection and disconnection. Afterwards, we will learn how to securely store your Wi-Fi credentials on your device. In the last section, we will test out the commands for managing Target Wake Time (TWT) on your device. This requires you to have a Wi-Fi 6 Access Point with TWT enabled, and this portion of the exercise is, therefore, optional.
Exercise steps
1. Build and flash the Wi-Fi Shell sample to your board.
1.1 In the nRF Connect window in Visual Studio Code, select Create a new application under the WELCOME menu.
1.2 Select Copy a sample, then select the nRF Connect SDK version you are using.
Search for and select the sample “Wi-Fi shell“.
In the next step, you will input the path to where you want to store this exercise. Save the application to wherever you cloned the code base for this course, as <wifi_fund_repo>\l2\l2_e1_sol.
In VS Code, under Connected Devices, connect to the COM port of your board by clicking the electric plug icon as shown in the image below, then choose the default COM port settings 115200 8n1 rtscts:off
1. Install the Serial Terminal app.
Open nRF Connect for Desktop, navigate to the Serial Terminal app and click Install.
2. Launch the Serial Terminal app.
3. Connect to your board and find the COM ports.
In the upper right hand corner, Select Device.
Select your board, in the example below we are using the nRF7002 DK. This will automatically connect to one of the COM ports on the device.
Observe the following log output
[00:00:00.315,429] <inf> wifi_nrf: Management buffer offload enabled[00:00:00.448,486] <inf> fs_nvs: 2 Sectors of 4096 bytes[00:00:00.448,486] <inf> fs_nvs: alloc wra: 0, fe8[00:00:00.448,516] <inf> fs_nvs: data wra: 0, 0*** Booting nRF Connect SDK ****** Using Zephyr OS ***Starting nrf7002dk with CPU frequency: 128 MHz[00:00:00.449,951] <inf> wifi_supplicant: wpa_supplicant initialized
Terminal
2. Scan for access points in your vicinity.
Before we connect to a network, let’s do a passive scan to see all available access points.
Type the following command into the terminal.
Copy
wifi scan
You should see something similar to the following output (this might take a few seconds). This is the scan result list.
The Wi-Fi chip outputs the acquired information about each available access point. As you can see in the output, this information includes the SSID, the length of the SSID, the channel where the AP was broadcasting its beacon, the band the AP operates on, the RSSI as perceived by your device, the security protocol implemented by the AP, the BSSID, and finally the presence or absence of MFP security.
3. Connect to an access point.
Now we can use the command wifi connect to connect to an access point.
wifi connect takes many parameters, a few of them are listed below (run wifi connect -help in the terminal for the full list)
-t <timeout>: Duration after which connection attempt needs to fail.
-h <help>: Print out the help for the connect command.
Entering only the SSID, password (PSK), and key management of the access point you want to connect to will suffice. You can use the results from the wifi scan command to know which key management parameter to enter, see the Security column.
For the <key-mgmt> parameter, entering “0” only works with open APs.
Issue the following command in the terminal to connect to the AP.
Copy
wifi connect -s "<SSID>" -p "<psk>" -k <key-mgmt>
If the connection is successful, you should see a similar log output
wifi connect -s "<SSID>" -p "<psk>" -k <key-mgmt>wifi connect -s "<SSID>" -p "<psk>" -k <key-mgmt>Connection requestedConnectedwpa_supp: wlan0: SME: Trying to authenticate with aa:aa:aa:aa:aa:aa (SSID='<SSID>' freq=5180 MHz)<inf> wifi_nrf: wifi_nrf_wpa_supp_authenticate:Authentication request sent successfully<inf> wpa_supp: wlan0: Trying to associate with aa:aa:aa:aa:aa:aa (SSID='<SSID>' freq=5180 MHz)<inf> wifi_nrf: wifi_nrf_wpa_supp_associate: Association request sent successfully<inf> wpa_supp: wlan0: Associated with aa:aa:aa:aa:aa:aa<inf> wpa_supp: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0<inf> wpa_supp: wlan0: WPA: Key negotiation completed with aa:aa:aa:aa:aa:aa [PTK=CCMP GTK=CCMP]<inf> wpa_supp: wlan0: CTRL-EVENT-CONNECTED - Connection to aa:aa:aa:aa:aa:aa completed [id=0 id_str=]<inf> net_dhcpv4: Received: 192.00.00.00
Terminal
4. Get the status of the network interface.
The command wifi status lets us read out extra information about the access point we are connected to that we didn’t get during the scan procedure, such as the beacon interval, DTIM and whether TWT is supported or not.
The command wifi statistics gives us additional information about the Wi-Fi connection, such as the bytes being sent and received, and the errors.
Issue the following command in the terminal
Copy
wifi statistics
Observe the following output
Statistics for Wi-Fi interface 0x200016a8 [1]Bytes received : 109247Bytes sent : 5458Packets received : 346Packets sent : 39Receive errors : 0Send errors : 0Bcast received : 371Bcast sent : 11Mcast received : 218Mcast sent : 8Beacons received : 138Beacons missed : 46Unicast received : 50Unicast sent : 17Overrun count : 16
Terminal
6. Configure device wakeup mode
The command wifi ps_wakeup_mode is used to configure your Wi-Fi device wakeup mode when using power save mode. It takes the following parameters.
<dtim>: Wakeup mode for the DTIM interval
<listen_interval>: Wakeup mode for the Listen interval
Issue the following command in the terminal to set it to wakeup for the DTIM interval for example. Power save modes, DTIM intervals and the Listen interval will be explained in detail in Lesson 6 of this course.
Copy
wifi ps_wakeup_mode dtim
7. Storing the Wi-Fi credentials.
Using the wifi connect command mentioned above, you will have to re-enter your SSID and password upon device reset to re-establish the connection. To mitigate this, we can use the Wi-Fi credentials shell subcommands, which interact with the Wi-Fi credentials library to add the network credentials to credentials storage.
7.1 Store the Wi-Fi credentials using wifi cred add.
To store the credentials, we will be using the Wi-Fi credentials shell, which are identified as wifi cred, as specifically the subcommand add.
We will be using the following parameters from wifi cred add
<-s –ssid "<SSID>">: SSID.
[-p, –passphrase]: Passphrase (valid only for secure SSIDs)
For the last command, refer to the output from wifi scan, specifically the security column. Then replace <key-mgmt> with whichever number corresponds to the security for the Wi-Fi network you wish to connect to.
For a full list of key management types, you can use the following command
Copy
wifi cred add help
7.2 Connect to Wi-Fi using the auto_connect subcommand.
Now that we have stored the credentials on the device, we will use the auto-connect subcommand which automatically connects to any stored network
7.3 The wifi cred command also has the subcommands list and delete.
list will list all the networks in credential storage and delete "<SSID>" will remove that network from credentials storage.
Copy
wifi cred listwifi cred delete "<SSID>"
(Optional) 8. Set up a Target Wake Time flow.
This step is optional as it only works if you are using a Wi-Fi 6 router that supports Target Wake Time. In some cases, you will need to enable TWT functionality in the router configurations. Consult your router’s user manual for more information.
The command wifi twt is used to manage TWT flows.
It has five different subcommands: quick_setup, setup, btwt_setup, teardown,and teardown_all.
To easily setup a TWT flow, we will use the quick_setup subcommand, which takes the following two parameters
<twt_wake_interval>: 1 – 262144 µs, TWT Wake Duration, for how long will the device be awake (in µs)
<twt_interval>: 1 µs – 2^31 µs, TWT Wake Interval, the interval between successive TWT wake periods
Let’s say we want the device to wakeup for 20 ms, every minute. Then twt_wake_interval would be 20 ms (20000 µs) and the twt_interval will be 1 minute (60000000 µS).
Issue the following command in the terminal
wifi twt quick_setup 20000 60000000
Terminal
More on this
twt quick_setup uses twt setup, but sets all the other parameters to default values.
twt setup takes the following parameters
<negotiation_type>: 0 – Individual, 1 – Broadcast, 2 – Wake TBTT <setup_cmd>: 0 – Request, 1 – Suggest, 2 – Demand <dialog_token>: 1-255, used to match action requests with action responses <flow_id>: 0-7, gives an ID to the flow being created <responder>: 0 – Requester, 1 – Responder <trigger>: 0 – Trigger mode enabled, 1 – Trigger mode disabled <implicit>: 0 – Explicit TWT operation, 1 – Implicit <announce>: 0 – Announce mode enabled, 1 – Announce mode disabled <twt_wake_interval>: 1 – 262144 µs, TWT Wake Duration, for how long will the device be awake (in µs) <twt_interval>: 1 µs – 2^31 µs, TWT Wake Interval, the interval between successive TWT wake periods <wake-ahead-duration>: 1 µs – 2^31 µs, <info-disable>: 0 or 1 <exponent>: 0-31 <mantissa>: 1 – 2^16
Negotiation type is used to determine the target STA of this TWT schedule. When set to “Individual”, it means that this TWT schedule will be set to the STA individually. Whereas, when set to “Broadcast”, it means the AP broadcasts TWT schedules to multiple STAs.
(Optional) 9. Tear down the Target Wake Time flow.
To tear down the TWT flow, we will use the teardown subcommand, which takes the following parameters
<negotiation_type>: 0 – Individual, 1 – Broadcast, 2 – Wake TBTT (0 when using twt_
<setup_cmd>: 0 – Request, 1 – Suggest, 2 – Demand
<dialog_token>: 1-255, used to match action requests with action responses
<flow_id>: 0-7, gives an ID to the flow being created
When using wifi twt quick_setup, the TWT flow
Use the flow_id parameter to indicate which TWT flow to tear down.
We want to tear down the flow that was set up in the previous step, which we assigned flow_id 2.
Issue the following command in the terminal
Copy
wifi twt teardown 0 0 1 0
Alternatively, teardown_all can be used to tear down all TWT flows, by sending the following command.
Copy
wifi twt teardown_all
Nordic Developer Academy Privacy Policy
1. Introduction
In this Privacy Policy you will find information on Nordic Semiconductor ASA (“Nordic Semiconductor”) processes your personal data when you use the Nordic Developer Academy.
References to “we” and “us” in this document refers to Nordic Semiconductor.
2. Our processing of personal data when you use the Nordic Developer Academy
2.1 Nordic Developer Academy
Nordic Semiconductor processes personal data in order to provide you with the features and functionality of the Nordic Developer Academy. Creating a user account is optional, but required if you want to track you progress and view your completed courses and obtained certificates. If you choose to create a user account, we will process the following categories of personal data:
Email
Name
Password (encrypted)
Course progression (e.g. which course you have completely or partly completed)
Certificate information, which consists of name of completed course and the validity of the certificate
Course results
During your use of the Nordic Developer Academy, you may also be asked if you want to provide feedback. If you choose to respond to any such surveys, we will also process the personal data in your responses in that survey.
The legal basis for this processing is GDPR article 6 (1) b. The processing is necessary for Nordic Semiconductor to provide the Nordic Developer Academy under the Terms of Service.
2.2 Analytics
If you consent to analytics, Nordic Semiconductor will use Google Analytics to obtain statistics about how the Nordic Developer Academy is used. This includes collecting information on for example what pages are viewed, the duration of the visit, the way in which the pages are maneuvered, what links are clicked, technical information about your equipment. The information is used to learn how Nordic Developer Academy is used and how the user experience can be further developed.
2.2 Newsletter
You can consent to receive newsletters from Nordic from within the Nordic Developer Academy. How your personal data is processed when you sign up for our newsletters is described in the Nordic Semiconductor Privacy Policy.
3. Retention period
We will store your personal data for as long you use the Nordic Developer Academy. If our systems register that you have not used your account for 36 months, your account will be deleted.
4. Additional information
Additional information on how we process personal data can be found in the Nordic Semiconductor Privacy Policy and Cookie Policy.
Nordic Developer Academy Terms of Service
1. Introduction
These terms and conditions (“Terms of Use”) apply to the use of the Nordic Developer Academy, provided by Nordic Semiconductor ASA, org. nr. 966 011 726, a public limited liability company registered in Norway (“Nordic Semiconductor”).
Nordic Developer Academy allows the user to take technical courses related to Nordic Semiconductor products, software and services, and obtain a certificate certifying completion of these courses. By completing the registration process for the Nordic Developer Academy, you are agreeing to be bound by these Terms of Use.
These Terms of Use are applicable as long as you have a user account giving you access to Nordic Developer Academy.
2. Access to and use of Nordic Developer Academy
Upon acceptance of these Terms of Use you are granted a non-exclusive right of access to, and use of Nordic Developer Academy, as it is provided to you at any time. Nordic Semiconductor provides Nordic Developer Academy to you free of charge, subject to the provisions of these Terms of Use and the Nordic Developer Academy Privacy Policy.
To access select features of Nordic Developer Academy, you need to create a user account. You are solely responsible for the security associated with your user account, including always keeping your login details safe.
You will able to receive an electronic certificate from Nordic Developer Academy upon completion of courses. By issuing you such a certificate, Nordic Semiconductor certifies that you have completed the applicable course, but does not provide any further warrants or endorsements for any particular skills or professional qualifications.
Nordic Semiconductor will continuously develop Nordic Developer Academy with new features and functionality, but reserves the right to remove or alter any existing functions without notice.
3. Acceptable use
You undertake that you will use Nordic Developer Academy in accordance with applicable law and regulations, and in accordance with these Terms of Use. You must not modify, adapt, or hack Nordic Developer Academy or modify another website so as to falsely imply that it is associated with Nordic Developer Academy, Nordic Semiconductor, or any other Nordic Semiconductor product, software or service.
You agree not to reproduce, duplicate, copy, sell, resell or in any other way exploit any portion of Nordic Developer Academy, use of Nordic Developer Academy, or access to Nordic Developer Academy without the express written permission by Nordic Semiconductor. You must not upload, post, host, or transmit unsolicited email, SMS, or \”spam\” messages.
You are responsible for ensuring that the information you post and the content you share does not;
contain false, misleading or otherwise erroneous information
infringe someone else’s copyrights or other intellectual property rights
contain sensitive personal data or
contain information that might be received as offensive or insulting.
Such information may be removed without prior notice.
Nordic Semiconductor reserves the right to at any time determine whether a use of Nordic Developer Academy is in violation of its requirements for acceptable use.
Violation of the at any time applicable requirements for acceptable use may result in termination of your account. We will take reasonable steps to notify you and state the reason for termination in such cases.
4. Routines for planned maintenance
Certain types of maintenance may imply a stop or reduction in availability of Nordic Developer Academy. Nordic Semiconductor does not warrant any level of service availability but will provide its best effort to limit the impact of any planned maintenance on the availability of Nordic Developer Academy.
5. Intellectual property rights
Nordic Semiconductor retains all rights to all elements of Nordic Developer Academy. This includes, but is not limited to, the concept, design, trademarks, know-how, trade secrets, copyrights and all other intellectual property rights.
Nordic Semiconductor receives all rights to all content uploaded or created in Nordic Developer Academy. You do not receive any license or usage rights to Nordic Developer Academy beyond what is explicitly stated in this Agreement.
6. Liability and damages
Nothing within these Terms of Use is intended to limit your statutory data privacy rights as a data subject, as described in the Nordic Developer Academy Privacy Policy. You acknowledge that errors might occur from time to time and waive any right to claim for compensation as a result of errors in Nordic Developer Academy. When an error occurs, you shall notify Nordic Semiconductor of the error and provide a description of the error situation.
You agree to indemnify Nordic Semiconductor for any loss, including indirect loss, arising out of or in connection with your use of Nordic Developer Academy or violations of these Terms of Use. Nordic Semiconductor shall not be held liable for, and does not warrant that (i) Nordic Developer Academy will meet your specific requirements, (ii) Nordic Developer Academy will be uninterrupted, timely, secure, or error-free, (iii) the results that may be obtained from the use of Nordic Developer Academy will be accurate or reliable, (iv) the quality of any products, services, information, or other material purchased or obtained by you through Nordic Developer Academy will meet your expectations, or that (v) any errors in Nordic Developer Academy will be corrected.
You accept that this is a service provided to you without any payment and hence you accept that Nordic Semiconductor will not be held responsible, or liable, for any breaches of these Terms of Use or any loss connected to your use of Nordic Developer Academy. Unless otherwise follows from mandatory law, Nordic Semiconductor will not accept any such responsibility or liability.
7. Change of terms
Nordic Semiconductor may update and change the Terms of Use from time to time. Nordic Semiconductor will seek to notify you about significant changes before such changes come into force and give you a possibility to evaluate the effects of proposed changes. Continued use of Nordic Developer Academy after any such changes shall constitute your acceptance of such changes. You can review the current version of the Terms of Use at any time at https://academy.nordicsemi.com/terms-of-service/
8. Transfer of rights
Nordic Semiconductor is entitled to transfer its rights and obligation pursuant to these Terms of Use to a third party as part of a merger or acquisition process, or as a result of other organizational changes.
9. Third Party Services
To the extent Nordic Developer Academy facilitates access to services provided by a third party, you agree to comply with the terms governing such third party services. Nordic Semiconductor shall not be held liable for any errors, omissions, inaccuracies, etc. related to such third party services.
10. Dispute resolution
The Terms of Use and any other legally binding agreement between yourself and Nordic Semiconductor shall be subject to Norwegian law and Norwegian courts’ exclusive jurisdiction.
Switch language?
Progress is tracked separately for each language. Switching will continue from your progress in that language or start fresh if you haven't begun.
Your current progress is saved, and you can switch back anytime.
•Support for WPA3-SAE using PSA APIs. •Support for Wi-Fi Direct® operation mode on the nRF7002 DK, with support for Wi-Fi Direct added to the Wi-Fi: WFA QuickTrack control application. •Updated Zperf to enable Raw TX throughput testing and throughput improvements. •(Experimental) Support for the nRF54LM20B SoC combined with the nRF7002-EB II shield.
MCUboot & Partition Manager
•Single-Slot DFU and RAM Load mode are both promoted to fully supported •Partition Manager is officially deprecated in favor of Zephyr's devicetree-based partitioning.
