Wi-Fi Fundamentals

Changing the version will not affect your certificate
Lesson 1 – Introduction to Wi-Fi
 5 Topics | 1 Quiz
What is Wi-Fi?
Key features of Wi-Fi 6
Security in Wi-Fi
nRF70 Series
Exercise 1 – Provisioning a Wi-Fi device over the phone
Lesson 1 quiz
Lesson 2 – Connecting to Wi-Fi
 5 Topics | 1 Quiz
Network Management API
Wi-Fi Provisioning
Exercise 1 – Connecting to Wi-Fi using the Wi-Fi shell
Exercise 2 – Connecting to Wi-Fi using the Network Management API
Exercise 3 – Provisioning the device over Bluetooth LE
Lesson 2 quiz
Lesson 3 – Networking & sockets
 4 Topics | 1 Quiz
Network protocol stack
Socket API
Exercise 1 – Pinging an echo server
Exercise 2 – Measuring the throughput of a Wi-Fi connection
Lesson 3 quiz
Lesson 4 – MQTT over Wi-Fi
 4 Topics | 1 Quiz
MQTT protocol
MQTT library
Exercise 1 – Connecting to an MQTT broker
Exercise 2 – Securing the MQTT connection with TLS
Lesson 4 quiz
Lesson 5 – HTTP over Wi-Fi
 5 Topics | 1 Quiz
HTTP protocol
HTTP library
Exercise 1 – Connecting to an HTTP server
Exercise 2 – Adding TLS to the HTTP connection
Exercise 3 – Setting up an HTTP Server
Lesson 5 quiz
Lesson 6 – Power save modes
 5 Topics | 1 Quiz
Beacon frames: TIM and DTIM
Power save modes
Target Wake Time
Exercise 1 – Enabling power save modes
Exercise 2 – (Optional) Enabling TWT with notification
Lesson 6 quiz
Get your Certificate!
Feedback
Feedback

If you are having issues with the exercises, please create a ticket on DevZone: devzone.nordicsemi.com
Drag & Drop Files, Choose Files to Upload You can upload up to 2 files.
Loading
RegisterLog in

Exercise 2 – (Optional) Enabling TWT with notification

In this exercise, we will use Target Wake Time (TWT) to reduce power consumption further. Additionally, we will use the TWT sleep status notification to be notified of when the device goes to sleep and when it wakes up, and use this to send and check for received packets during the awake time. To show that the device can send and receive packets, the device connects to a simple echo UDP server that we will run on a PC.

When the device starts up, it will be configured to use legacy power saving mode. Pressing button 1 on the board will enable TWT, or if TWT is already enabled it will instead be disabled. Pressing button 2 will enable sending packets. When this is enabled, the device will send a packet every TWT period when it wakes up.

Important

To test TWT, you need a Wi-Fi 6 router that supports TWT.

Exercise steps

In the GitHub repository for this course, go to the base code for this exercise, found in l6/l6_e2.

1. Define macros and global variables

1.1 Define IPv4 address and port for the server.

The IPv4 address is the address oTo test TWT, you need a Wi-Fi 6 router that supports TWT.f the PC running the UDP server, so this address must be changed to reflect the IPv4 address of your PC.

Note

You can find the IPv4 of your computer by typing ipconfig in your command prompt on Windows or ifconfig in your terminal on Linux and macOS.

Copy
#define SERVER_IPV4_ADDR "<your_IP_address>"
#define SERVER_PORT 7777
C

1.2 Define macros for wake up time and interval for TWT.

Copy
#define TWT_WAKE_INTERVAL_MS 65
#define TWT_INTERVAL_MS      7000
C

These variables will be used when configuring TWT later. The TWT interval is the total interval between TWT wake periods: TWT interval = wake up time + sleeping time.

1.3 Create variables to keep track of TWT status, flow ID, and if sending packets is enabled.

Copy
bool nrf_wifi_twt_enabled = 0;
static uint32_t twt_flow_id = 1;
bool sending_packets_enabled = 0;
C

2. Configure the TWT request.

2.1 Define the TWT parameters struct.

Define the TWT parameters struct wifi_twt_params and fill the parameters that are common for both TWT setup and TWT teardown.

Copy
	struct wifi_twt_params twt_params = {0};

	twt_params.negotiation_type = WIFI_TWT_INDIVIDUAL;
	twt_params.flow_id = twt_flow_id;
	twt_params.dialog_token = 1;
C

2.2 Fill in the rest of the wifi_twt_params parameters.

When TWT is not enabled we want to send a TWT setup request, and if it is enabled we want to send a TWT teardown request.

2.2.1 Fill in the TWT setup specific parameters.

Fill in the TWT setup specific parameters of the wifi_twt_params struct.

Copy
twt_params.operation = WIFI_TWT_SETUP;
twt_params.setup_cmd = WIFI_TWT_SETUP_CMD_REQUEST;
twt_params.setup.responder = 0;
twt_params.setup.trigger = 0;
twt_params.setup.implicit = 1;
twt_params.setup.announce = 0;
twt_params.setup.twt_wake_interval = TWT_WAKE_INTERVAL_MS * USEC_PER_MSEC;
twt_params.setup.twt_interval = TWT_INTERVAL_MS * USEC_PER_MSEC;
C

We are using the TWT setup operation to enable TWT. Since our device is the one requesting to setup TWT we send a Request TWT command to the AP with the responder parameter indicating that we are a requester.

We want to reduce the power consumption as much as possible, which we do by reducing the amount of messages sent. Therefore, we disable trigger frames, and configure TWT to be implicit and unannounced. With this configuration, the device does not have to send a trigger frame to the AP to inform that it is awake and ready to receive packets.

2.2.2 Fill in the TWT teardown specific parameters.

Fill in the TWT teardown specific parameters of the wifi_twt_params struct.

Copy
twt_params.operation = WIFI_TWT_TEARDOWN;
twt_params.setup_cmd = WIFI_TWT_TEARDOWN;
twt_flow_id = twt_flow_id < WIFI_MAX_TWT_FLOWS ? twt_flow_id + 1 : 1;
nrf_wifi_twt_enabled = 0;
C

We are using the TWT teardown operation to disable TWT by sending a TWT teardown command to the AP.

2.3 Send the TWT request with net_mgmt().

Send a TWT request using NET_REQUEST_WIFI_TWT.

Copy
if (net_mgmt(NET_REQUEST_WIFI_TWT, iface, &twt_params, sizeof(twt_params))) {
		LOG_ERR("%s with %s failed, reason : %s",
		  wifi_twt_operation_txt(twt_params.operation),
			wifi_twt_negotiation_type_txt(twt_params.negotiation_type),
			wifi_twt_get_err_code_str(twt_params.fail_reason));
		return -1;
	}
C

3. Add the TWT events.

3.1 Define a mask for the TWT events we are interested in.

Copy
#define TWT_MGMT_EVENTS (NET_EVENT_WIFI_TWT | NET_EVENT_WIFI_TWT_SLEEP_STATE)
C

3.2 Handle the two events in the event handler.

3.2.1 Upon a TWT event, call handle_wifi_twt_event() to handle the response.

In twt_mgmt_event_handler(), add the following code to handle the TWT event

Copy
case NET_EVENT_WIFI_TWT:
	handle_wifi_twt_event(cb);
	break;
C

3.2.2 Upon TWT sleep state event, inform the user of the current sleep state. When the device is in the awake state, send a packet to the server and check for any received packets if sending packets is enabled.

Copy
case NET_EVENT_WIFI_TWT_SLEEP_STATE:
	int *twt_state;
	twt_state = (int *)(cb->info);
	LOG_INF("TWT sleep state: %s", *twt_state ? "awake" : "sleeping" );
	if ((*twt_state == WIFI_TWT_STATE_AWAKE) & sending_packets_enabled) {
		send_packet();
		receive_packet();
	}
	break;
C

3.3 Initialize and add the TWT event handler

Copy
net_mgmt_init_event_callback(&twt_mgmt_cb, twt_mgmt_event_handler, TWT_MGMT_EVENTS);
net_mgmt_add_event_callback(&twt_mgmt_cb);
C

4. Implement the TWT event callback function.

4.1 Create a struct for the received TWT events.

Create a wifi_twt_params struct for the received TWT event and fill it with the event information.

Copy
const struct wifi_twt_params *resp = (const struct wifi_twt_params *)cb->info;
C

4.2 Upon a TWT teardown initiated by the AP, toggle the state.

If the event is a TWT teardown initiated by the AP, change the value of nrf_wifi_twt_enabled and exit the function.

Copy
if (resp->operation == WIFI_TWT_TEARDOWN) {
	LOG_INF("TWT teardown received for flow ID %d\n",
	      resp->flow_id);
	nrf_wifi_twt_enabled = 0;
	return;
}
C

4.3 Update the flow ID received in the TWT response.

Update twt_flow_id to reflect the flow ID received in the TWT response.

Copy
twt_flow_id = resp->flow_id;
C

4.4 Check if a TWT response was received.

If not, the TWT request timed out.

Copy
if (resp->resp_status == WIFI_TWT_RESP_RECEIVED) {
	LOG_INF("TWT response: %s",
	      wifi_twt_setup_cmd_txt(resp->setup_cmd));		
} 
else {
	LOG_INF("TWT response timed out\n");
	return;
}
C

4.5 Upon an accepted TWT setup, log the negotiated parameters.

If the TWT setup was accepted, change the value of nrf_wifi_twt_enabled and print the negotiated parameters.

Copy
if (resp->setup_cmd == WIFI_TWT_SETUP_CMD_ACCEPT) {
	nrf_wifi_twt_enabled = 1;

	LOG_INF("== TWT negotiated parameters ==");
	LOG_INF("TWT Dialog token: %d",
	      resp->dialog_token);
	LOG_INF("TWT flow ID: %d",
	      resp->flow_id);
	LOG_INF("TWT negotiation type: %s",
	      wifi_twt_negotiation_type_txt(resp->negotiation_type));
	LOG_INF("TWT responder: %s",
	       resp->setup.responder ? "true" : "false");
	LOG_INF("TWT implicit: %s",
	      resp->setup.implicit ? "true" : "false");
	LOG_INF("TWT announce: %s",
	      resp->setup.announce ? "true" : "false");
	LOG_INF("TWT trigger: %s",
	      resp->setup.trigger ? "true" : "false");
	LOG_INF("TWT wake interval: %d ms (%d us)",
	      resp->setup.twt_wake_interval/USEC_PER_MSEC,
		  resp->setup.twt_wake_interval);
	LOG_INF("TWT interval: %lld s (%lld us)",
		  resp->setup.twt_interval/USEC_PER_SEC,
	      resp->setup.twt_interval);
	LOG_INF("===============================");
}
C

5. Modify the button handler.

5.1 Call wifi_set_twt() to enable or disable TWT when button 1 is pressed.

Copy
if (button & DK_BTN1_MSK) {
	wifi_set_twt();
}
C

5.2 Enable or disable sending packets during TWT awake when button 2 is pressed.

Copy
if (button & DK_BTN2_MSK) {
	sending_packets_enabled = !sending_packets_enabled;
	LOG_INF("Sending packets %s", sending_packets_enabled ? "enabled" : "disabled" );
}
C

Testing

6. Start the UDP server.

The UDP server is a Python script located in l6_e2_sol/scripts. Open the scripts directory in a terminal or command-line windows and enter the following command to start the server

Copy
python3 simple_udp_server.py

You should see Starting UDP server in the window running the server.

7. Build and flash the application to your device.

This exercise uses the PSA backend for storing the Wi-Fi credentials. Therefore, you must build with TF-M.

BoardBuild with TF-MExtra CMake arguments
nRF7002 DKnrf7002dk/nrf5340/cpuapp/nsN/A
nRF5340 DK + nRF7002 EKnrf5340dk/nrf5340/cpuapp/ns-DSHIELD=nrf7002ek

If necessary, input the commands to connect to Wi-Fi, as we have done in previous exercises.

You should see the following log when the device has started

*** Booting nRF Connect SDK ***
*** Using Zephyr OS ***
[00:00:00.651,214] <inf> wifi_supplicant: wpa_supplicant initialized
[00:00:01.490,509] <inf> Lesson6_Exercise2: Waiting to connect to Wi-Fi
[00:00:08.100,097] <inf> Lesson6_Exercise2: Network connected
[00:00:08.154,968] <inf> Lesson6_Exercise2: Connected to server
[00:00:08.154,968] <inf> Lesson6_Exercise2: Press button 1 on your DK to enable or disable TWT
[00:00:08.156,280] <inf> Lesson6_Exercise2: Successfully sent message: Hello from nRF70 Series! 0
[00:00:09.653,778] <inf> Lesson6_Exercise2: Data received from the server: (Hello from nRF70 Series! 0)
Terminal

8. Interact with the buttons on the board.

8.1 Press button 1 on the board to enable TWT.

You should see a log that TWT setup has been requested. If the router accepts the TWT setup request the device will print the negotiated TWT parameters.

[00:00:15.703,460] <inf> Lesson6_Exercise2: -------------------------------
[00:00:15.703,491] <inf> Lesson6_Exercise2: TWT operation TWT setup requested
[00:00:15.703,491] <inf> Lesson6_Exercise2: -------------------------------
[00:00:15.799,896] <inf> Lesson6_Exercise2: TWT response: TWT accept
[00:00:15.799,896] <inf> Lesson6_Exercise2: == TWT negotiated parameters ==
[00:00:15.799,896] <inf> Lesson6_Exercise2: TWT Dialog token: 1
[00:00:15.799,926] <inf> Lesson6_Exercise2: TWT flow ID: 0
[00:00:15.799,957] <inf> Lesson6_Exercise2: TWT negotiation type: TWT individual negotiation
[00:00:15.799,957] <inf> Lesson6_Exercise2: TWT responder: true
[00:00:15.799,987] <inf> Lesson6_Exercise2: TWT implicit: true
[00:00:15.800,018] <inf> Lesson6_Exercise2: TWT announce: false
[00:00:15.800,048] <inf> Lesson6_Exercise2: TWT trigger: false
[00:00:15.800,048] <inf> Lesson6_Exercise2: TWT wake interval: 65 ms (65024 us)
[00:00:15.800,079] <inf> Lesson6_Exercise2: TWT interval: 7 s (7004000 us)
[00:00:15.800,079] <inf> Lesson6_Exercise2: ===============================
Terminal

Once TWT is enabled, the sleep state will be printed to the log.

[00:00:15.800,720] <inf> Lesson6_Exercise2: TWT sleep state: sleeping
[00:00:18.435,821] <inf> Lesson6_Exercise2: TWT sleep state: awake
[00:00:18.501,220] <inf> Lesson6_Exercise2: TWT sleep state: sleeping
[00:00:25.440,124] <inf> Lesson6_Exercise2: TWT sleep state: awake
[00:00:25.506,378] <inf> Lesson6_Exercise2: TWT sleep state: sleeping
Terminal

8.2 Press button 2 to enable sending packets during TWT awake periods.

The device will start sending and receiving UDP packets, which will be printed to logs.

[00:00:28.442,779] <inf> Lesson6_Exercise2: Sending packets enabled
[00:00:32.443,939] <inf> Lesson6_Exercise2: TWT sleep state: awake
[00:00:32.446,105] <inf> Lesson6_Exercise2: Successfully sent message: Hello from nRF70 Series! 1
[00:00:39.451,538] <inf> Lesson6_Exercise2: Data received from the server: (Hello from nRF70 Series! 1)
[00:00:39.451,568] <inf> Lesson6_Exercise2: TWT sleep state: sleeping
[00:00:39.451,599] <inf> Lesson6_Exercise2: TWT sleep state: awake
[00:00:39.452,392] <inf> Lesson6_Exercise2: Successfully sent message: Hello from nRF70 Series! 2
[00:00:46.454,589] <inf> Lesson6_Exercise2: Data received from the server: (Hello from nRF70 Series! 2)
[00:00:46.454,620] <inf> Lesson6_Exercise2: TWT sleep state: sleeping
[00:00:46.454,681] <inf> Lesson6_Exercise2: TWT sleep state: awake
[00:00:46.455,444] <inf> Lesson6_Exercise2: Successfully sent message: Hello from nRF70 Series! 3
[00:00:53.458,801] <inf> Lesson6_Exercise2: Data received from the server: (Hello from nRF70 Series! 3)
[00:00:53.458,831] <inf> Lesson6_Exercise2: TWT sleep state: sleeping
[00:00:53.458,892] <inf> Lesson6_Exercise2: TWT sleep state: awake
[00:00:53.459,655] <inf> Lesson6_Exercise2: Successfully sent message: Hello from nRF70 Series! 4
[00:01:00.463,195] <inf> Lesson6_Exercise2: Data received from the server: (Hello from nRF70 Series! 4)
Terminal

The UDP server will print the packets it receives from the device.

Starting UDP server
Data received from client: Hello from nRF70 Series! 1
Data received from client: Hello from nRF70 Series! 2
Data received from client: Hello from nRF70 Series! 3
Data received from client: Hello from nRF70 Series! 4
Terminal

8.3 Press button one on the board once more to disable TWT.

[00:01:04.898,895] <inf> Lesson6_Exercise2: -------------------------------
[00:01:04.898,956] <inf> Lesson6_Exercise2: TWT operation TWT teardown requested
[00:01:04.898,956] <inf> Lesson6_Exercise2: -------------------------------
Terminal

9. Start the power measurement

9.1 Connect the PPK2 to the device as shown below

PPK2DK
VOUTP23 VBAT
GNDP21

Note

The current is measured over only the nRF7002 IC in this exercise, not including the nRF5340 SoC. Guides for how to measure the total current or measuring the nRF7002 IC and nRF5340 SoC separately can be found at nRF7002 DK – Measuring current.

9.2 Open the Power Profiler app and select the PPK2 in the drop-down menu.

9.3 Select source meter mode, set the supply voltage to 3.6 volts, and enable power output.

9.4 Build and flash the application to your device.

9.5 Press ‘Start’ in the Power Profiler app to start the measurement.

9.6 Test the example as in step 8 and look at the power measurement.

When enabling TWT we see that the time between the wake up spikes increases compared to with legacy power saving. One of the big advantages of TWT is that it enables the device to be asleep for longer periods of time, which decreases the average power consumption.

Legacy power saving compared to TWT.

10. Play around with different TWT periods.

Modify TWT_INTERVAL_MS to see how the TWT interval affects the average power consumption.

The default TWT interval in the exercise is 7 seconds. Below we show the power consumption when the interval is 7 seconds and 20 seconds. The first image shows the 7 second interval where the device is only listening for packets during wake up, and the seconds shows the spikes when it is also sending a packet each time it wakes up. The second image shows when the TWT interval is 20 seconds.

TWT with 7 second TWT interval.
TWT with 7 second TWT interval and sending packets enabled.
TWT with 20 second TWT interval.

Increasing the TWT interval will increase the time the device is asleep, thus decreasing the average power consumption.

This is the complete log

*** Booting nRF Connect SDK ***
[00:00:01.490,509] <inf> Lesson6_Exercise2: Connecting to Wi-Fi
[00:00:08.100,097] <inf> Lesson6_Exercise2: Connected to Wi-Fi Network: <SSID>
[00:00:08.153,991] <inf> Lesson6_Exercise2: IPv4 address acquired
[00:00:08.154,968] <inf> Lesson6_Exercise2: Connected to server
[00:00:08.154,968] <inf> Lesson6_Exercise2: Press button 1 on your DK to enable or disable TWT
[00:00:08.156,280] <inf> Lesson6_Exercise2: Successfully sent message: Hello from nRF70 Series! 0
[00:00:09.653,778] <inf> Lesson6_Exercise2: Data received from the server: (Hello from nRF70 Series! 0)
[00:00:15.703,460] <inf> Lesson6_Exercise2: -------------------------------
[00:00:15.703,491] <inf> Lesson6_Exercise2: TWT operation TWT setup requested
[00:00:15.703,491] <inf> Lesson6_Exercise2: -------------------------------
[00:00:15.799,896] <inf> Lesson6_Exercise2: TWT response: TWT accept
[00:00:15.799,896] <inf> Lesson6_Exercise2: == TWT negotiated parameters ==
[00:00:15.799,896] <inf> Lesson6_Exercise2: TWT Dialog token: 1
[00:00:15.799,926] <inf> Lesson6_Exercise2: TWT flow ID: 0
[00:00:15.799,957] <inf> Lesson6_Exercise2: TWT negotiation type: TWT individual negotiation
[00:00:15.799,957] <inf> Lesson6_Exercise2: TWT responder: true
[00:00:15.799,987] <inf> Lesson6_Exercise2: TWT implicit: true
[00:00:15.800,018] <inf> Lesson6_Exercise2: TWT announce: false
[00:00:15.800,048] <inf> Lesson6_Exercise2: TWT trigger: false
[00:00:15.800,048] <inf> Lesson6_Exercise2: TWT wake interval: 65 ms (65024 us)
[00:00:15.800,079] <inf> Lesson6_Exercise2: TWT interval: 7 s (7004000 us)
[00:00:15.800,079] <inf> Lesson6_Exercise2: ===============================
[00:00:15.800,720] <inf> Lesson6_Exercise2: TWT sleep state: sleeping
[00:00:18.435,821] <inf> Lesson6_Exercise2: TWT sleep state: awake
[00:00:18.501,220] <inf> Lesson6_Exercise2: TWT sleep state: sleeping
[00:00:25.440,124] <inf> Lesson6_Exercise2: TWT sleep state: awake
[00:00:25.506,378] <inf> Lesson6_Exercise2: TWT sleep state: sleeping
[00:00:28.442,779] <inf> Lesson6_Exercise2: Sending packets enabled
[00:00:32.443,939] <inf> Lesson6_Exercise2: TWT sleep state: awake
[00:00:32.446,105] <inf> Lesson6_Exercise2: Successfully sent message: Hello from nRF70 Series! 1
[00:00:39.451,538] <inf> Lesson6_Exercise2: Data received from the server: (Hello from nRF70 Series! 1)
[00:00:39.451,568] <inf> Lesson6_Exercise2: TWT sleep state: sleeping
[00:00:39.451,599] <inf> Lesson6_Exercise2: TWT sleep state: awake
[00:00:39.452,392] <inf> Lesson6_Exercise2: Successfully sent message: Hello from nRF70 Series! 2
[00:00:46.454,589] <inf> Lesson6_Exercise2: Data received from the server: (Hello from nRF70 Series! 2)
[00:00:46.454,620] <inf> Lesson6_Exercise2: TWT sleep state: sleeping
[00:00:46.454,681] <inf> Lesson6_Exercise2: TWT sleep state: awake
[00:00:46.455,444] <inf> Lesson6_Exercise2: Successfully sent message: Hello from nRF70 Series! 3
[00:00:53.458,801] <inf> Lesson6_Exercise2: Data received from the server: (Hello from nRF70 Series! 3)
[00:00:53.458,831] <inf> Lesson6_Exercise2: TWT sleep state: sleeping
[00:00:53.458,892] <inf> Lesson6_Exercise2: TWT sleep state: awake
[00:00:53.459,655] <inf> Lesson6_Exercise2: Successfully sent message: Hello from nRF70 Series! 4
[00:01:00.463,195] <inf> Lesson6_Exercise2: Data received from the server: (Hello from nRF70 Series! 4)
[00:01:00.463,256] <inf> Lesson6_Exercise2: TWT sleep state: sleeping
[00:01:00.463,287] <inf> Lesson6_Exercise2: TWT sleep state: awake
[00:01:00.464,080] <inf> Lesson6_Exercise2: Successfully sent message: Hello from nRF70 Series! 5
[00:01:00.472,167] <inf> Lesson6_Exercise2: Data received from the server: (Hello from nRF70 Series! 5)
[00:01:00.532,867] <inf> Lesson6_Exercise2: TWT sleep state: sleeping
[00:01:04.898,895] <inf> Lesson6_Exercise2: -------------------------------
[00:01:04.898,956] <inf> Lesson6_Exercise2: TWT operation TWT teardown requested
[00:01:04.898,956] <inf> Lesson6_Exercise2: -------------------------------
Terminal

Make sure to Log in or Register to save your progress

Back
Next

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.

Log in
Don’t have an account? Register an account

Forgot your password?
Register an account
Already have an account? Log in
(All fields are required unless specified optional)

  • 8 or more characters
  • Upper and lower case letters
  • At least one number or special character

Forgot your password?
Enter the email associated with your account, and we will send you a link to reset your password.

Back to Log in

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.

      Change summary

      What's new in the latest version

      Wi-Fi

      Wi-Fi

      •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

      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.