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 3 – Setting up an HTTP Server

Setting up an HTTP Server

In this exercise, we will learn how to set up and run an HTTP server on the nRF70 Series device. Then, we will communicate with the HTTP server by sending HTTP requests from an HTTP client running on a web browser or through a command line interface to control the LEDs on the board.

Exercise steps

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

1. Enable and configure the network interface.

1.1 Enable the necessary DNS configurations.

Enable the following DNS configurations in the prj.conf file

Copy
CONFIG_MDNS_RESPONDER=y
CONFIG_DNS_SD=y
CONFIG_MDNS_RESPONDER_DNS_SD=y
CONFIG_NET_HOSTNAME_ENABLE=y
CONFIG_NET_HOSTNAME_UNIQUE=n
CONFIG_NET_HOSTNAME="academyserver"
Kconfig
  • CONFIG_MDNS_RESPONDER: Enables the server to respond to local <hostname> inquiries, which we will use in this exercise. This Kconfig symbol requires setting the CONFIG_NET_HOSTNAME symbol to a meaningful value, as seen in the last line of the above code snippet.
  • CONFIG_DNS_SD: Enables DNS service discovery, which the server uses to advertise its service on a local network.
  • CONFIG_MDNS_RESPONDER_DNS_SD: Enables service discovery via the MDNS responder enabled in the lines above.
  • CONFIG_NET_HOSTNAME_ENABLE: Used to enable responding to a hostname.
  • CONFIG_NET_HOSTNAME_UNIQUE: Disable the condition of having a unique hostname.
  • CONFIG_NET_HOSTNAME: Hostname of the device, we will use academyserver.

1.2 Configure the network library.

Copy
CONFIG_NET_CONFIG_SETTINGS=y
CONFIG_NET_CONFIG_INIT_TIMEOUT=0
CONFIG_NET_CONFIG_NEED_IPV4=y
CONFIG_NET_LOG=y
Kconfig
  • CONFIG_NET_CONFIG_SETTINGS: This option controls whether the network system is configured or initialized at all, see the Network Configuration Library
  • CONFIG_NET_CONFIG_INIT_TIMEOUT: Seconds to wait for networking to be ready and available, set to 0 to disable timeout
  • CONFIG_NET_CONFIG_NEED_IPV4: Indicates that the application needs IPv4 support, this will make sure the network application is initialized properly in order to use IPv4.
  • CONFIG_NET_LOG: Enabling logging in the network stack

2. Enable Zephyr’s HTTP parser functionality.

HTTP parsing is important for the correct handling and interpreting of HTTP messages. The nRF Connect SDK includes an HTTP parser library that we will use.

2.1 Enable the HTTP parser library.

Copy
CONFIG_HTTP_PARSER=y
Kconfig

2.2 Include the header file for the HTTP parser library.

Add the following line in main.c

Copy
#include <zephyr/net/http/parser.h>
C

3. Define the Kconfig for the server port number

Define a Kconfig for the server port. We designate port number 80 to be the port where the HTTP server listens for incoming messages.

Copy
config HTTP_SERVER_SAMPLE_PORT
    int "HTTP server port"
    default 80
Kconfig

4. Register the service to be advertised via DNS.

We want to register a TCP service for DNS service discovery, so that we can connect to the HTTP server from a client using the hostname that we defined in CONFIG_NET_HOSTNAME (academyserver). For this to be possible, we need to register for DNS service discovery.

We can do this by using the API call DNS_SD_REGISTER_TCP_SERVICE(), from the DNS Service Discovery API, which takes the following parameters

DNS_SD_REGISTER_TCP_SERVICE() parameters

We will pass CONFIG_NET_HOSTNAME as the instance and CONFIG_HTTP_SERVER_SAMPLE_PORT as the port.

Copy
DNS_SD_REGISTER_TCP_SERVICE(http_server_sd, CONFIG_NET_HOSTNAME, "_http", "local",
			    DNS_SD_EMPTY_TXT, CONFIG_HTTP_SERVER_SAMPLE_PORT);
C

5. Define a struct to represent the structure of HTTP requests.

Define a struct named http_req to represent the structure of HTTP requests.

Copy
struct http_req {
	struct http_parser parser;
	int socket;
	bool received_all;
	enum http_method method;
	const char *url;
	size_t url_len;
	const char *body;
	size_t body_len;
};
C

6. Define HTTP server response strings.

Our demo implementation of the HTTP server will only respond to HTTP requests in 3 ways:

  • 200 OK: This means the server approves the request and will respond by sending the required data.
  • 403 Forbidden: This means the server understands the request but does not authorize it.
  • 404 Not found: This means the server could not find the resource requested by the client.

In this step, we define strings for standard HTTP server responses. These responses will be printed on the HTTP client’s terminal, and they show the server’s response to the client’s request.

Copy
static const char response_200[] = "HTTP/1.1 200 OK\r\n";
static const char response_403[] = "HTTP/1.1 403 Forbidden\r\n\r\n";
static const char response_404[] = "HTTP/1.1 404 Not Found\r\n\r\n";
C

7. Set up threads for handling multiple incoming TCP connections simultaneously.

To handle multiple incoming TCP connections, each connection will need its own thread, and each thread needs its own stack to store its temporary data.

Copy
K_THREAD_STACK_ARRAY_DEFINE(tcp4_handler_stack, MAX_CLIENT_QUEUE, STACK_SIZE);
static struct k_thread tcp4_handler_thread[MAX_CLIENT_QUEUE];
static k_tid_t tcp4_handler_tid[MAX_CLIENT_QUEUE];
K_THREAD_DEFINE(tcp4_thread_id, STACK_SIZE,
		process_tcp4, NULL, NULL, NULL,
		THREAD_PRIORITY, 0, -1);
C

By using the macro K_THREAD_STACK_ARRAY_DEFINE, we define an array of stacks for handling TCP connections.

tcp4_handler_stack is the name of the array. MAX_CLIENT_QUEUE is the number of threads (and their corresponding stacks) we want to create. STACK_SIZE is the size of each stack.

The struct k_thread is defined by zephyr. We just declare the tcp4_handler_thread array of structs of size MAX_CLIENT_QUEUE. This array of structs will hold each thread’s temporary data of type k_thread.

To manage those threads, we will need to refer to them with their thread IDs. Therefore, we create a similar array of thread IDs of type k_tid_t with a maximum size of MAX_CLIENT_QUEUE.

Lastly, to start a thread, we use the macro K_THREAD_DEFINE to start the thread named tcp4_thread_id.

8. Declare and initialize structs and variables used in network management.

Copy
static int tcp4_listen_sock;
static int tcp4_accepted[MAX_CLIENT_QUEUE];
C

9. Define a function to update the LED state.

Define the function handle_led_update(), that takes in the HTTP request, and the target LED and updates the LED state accordingly.

Copy
static bool handle_led_update(struct http_req *request, size_t led_id)
{
	char new_state_tmp[2] = {0};
	uint8_t new_state;
	size_t led_index = led_id - 1;

	if (request->body_len < 1) {
		return false;
	}

	memcpy(new_state_tmp, request->body, 1);

	new_state = atoi(request->body);

	if (new_state <= 1) {
		led_states[led_index] = new_state;
	} else {
		LOG_WRN("Attempted to update LED%d state to illegal value %d",
			led_id, new_state);
		return false;
	}

	(void)dk_set_led(led_index, led_states[led_index]);
	LOG_INF("LED%d turned %s", led_id, new_state == 1 ? "on" : "off");

	return true;
}
C

10. Define a function to handle HTTP requests.

This function receives the HTTP request, checks whether it’s a PUT or GET, processes the requests, and responds accordingly.

Copy
static void handle_http_request(struct http_req *request)
{
	size_t len;
	const char *resp_ptr = response_403;
	char dynamic_response_buf[100];
	char url[100];
	size_t url_len = MIN(sizeof(url) - 1, request->url_len);

	memcpy(url, request->url, url_len);

	url[url_len] = '\0';

	if (request->method == HTTP_PUT) {
		size_t led_id;
		int ret = sscanf(url, "/led/%u", &led_id);

		LOG_INF("Received PUT request to %s", url);

		/* Handle PUT requests to the "led" resource */
		if ((ret == 1) && (led_id > 0) && (led_id < (ARRAY_SIZE(led_states) + 1))) {
			if (handle_led_update(request, led_id)) {
				(void)snprintk(dynamic_response_buf, sizeof(dynamic_response_buf),
						"%s\r\n", response_200);
				resp_ptr = dynamic_response_buf;
			}
		} else {
			LOG_INF("Attempt to update unsupported resource '%s'", url);
			resp_ptr = response_403;
		}
	}

	if (request->method == HTTP_GET) {
		size_t led_id;
		int ret = sscanf(url, "/led/%u", &led_id);

		LOG_INF("Received GET request to %s", url);

		/* Handle GET requests to the "led" resource */
		if ((ret == 1) && (led_id > 0) && (led_id < (ARRAY_SIZE(led_states) + 1))) {
			char body[2];
			size_t led_index = led_id - 1;

			(void)snprintk(body, sizeof(body), "%d", led_states[led_index]);

			(void)snprintk(dynamic_response_buf,      sizeof(dynamic_response_buf),
				       "%sContent-Length: %d\r\n\r\n%s",
				       response_200, strlen(body), body);

			resp_ptr = dynamic_response_buf;
		} else {
			LOG_INF("Attempt to fetch unknown resource '%.*s'",
				request->url_len, request->url);

			resp_ptr = response_404;
		}
	}

	/* Get the total length of the HTTP response */
	len = strlen(resp_ptr);

	while (len) {
		ssize_t out_len;

		out_len = send(request->socket, resp_ptr, len, 0);

		if (out_len < 0) {
			LOG_ERR("Error while sending: %d", -errno);
			return;
		}

		resp_ptr = (const char *)resp_ptr + out_len;
		len -= out_len;
	}
}
C

11. Define and initialize callbacks for the HTTP parser.

11.1 Define the variable parser_settings of type struct http_parser_setting.

Copy
static struct http_parser_settings parser_settings;
C

11.2 Define the callbacks for the HTTP parser

The first five functions in this code snippet are callbacks to be called when different parts of the HTTP message are being parsed. Each function stores information retrieved from the parsed part in its corresponding part of the http_req struct.

The void parser_init() function at the end of the code snippet initializes the HTTP parser settings.

Copy
static int on_body(struct http_parser *parser, const char *at, size_t length)
{
	struct http_req *req = CONTAINER_OF(parser, struct http_req, parser);

	req->body = at;
	req->body_len = length;

	LOG_DBG("on_body: %d", parser->method);
	LOG_DBG("> %.*s", length, at);

	return 0;
}

static int on_headers_complete(struct http_parser *parser)
{
	struct http_req *req = CONTAINER_OF(parser, struct http_req, parser);

	req->method = parser->method;

	LOG_DBG("on_headers_complete, method: %s", http_method_str(parser->method));

	return 0;
}

static int on_message_begin(struct http_parser *parser)
{
	struct http_req *req = CONTAINER_OF(parser, struct http_req, parser);

	req->received_all = false;

	LOG_DBG("on_message_begin, method: %d", parser->method);

	return 0;
}

static int on_message_complete(struct http_parser *parser)
{
	struct http_req *req = CONTAINER_OF(parser, struct http_req, parser);

	req->received_all = true;

	LOG_DBG("on_message_complete, method: %d", parser->method);

	return 0;
}

static int on_url(struct http_parser *parser, const char *at, size_t length)
{
	struct http_req *req = CONTAINER_OF(parser, struct http_req, parser);

	req->url = at;
	req->url_len = length;

	LOG_DBG("on_url, method: %d", parser->method);
	LOG_DBG("> %.*s", length, at);

	return 0;
}
C

11.3 Define parser_init() to initialize the HTTP parser and the callbacks.

Copy
static void parser_init(void)
{
	http_parser_settings_init(&parser_settings);

	parser_settings.on_body = on_body;
	parser_settings.on_headers_complete = on_headers_complete;
	parser_settings.on_message_begin = on_message_begin;
	parser_settings.on_message_complete = on_message_complete;
	parser_settings.on_url = on_url;
}
C

12. Set up the HTTP server.

This function creates a TCP socket, calls zsock_bind() to bind the socket to the server address then listens for incoming requests on the socket.

Copy
static int setup_server(int *sock, struct sockaddr *bind_addr, socklen_t bind_addrlen)
{
	int ret;

		*sock = zsock_socket(bind_addr->sa_family, SOCK_STREAM, IPPROTO_TCP);

	if (*sock < 0) {
		LOG_ERR("Failed to create TCP socket: %d", errno);
		return -errno;
	}

	ret = zsock_bind(*sock, bind_addr, bind_addrlen);
	if (ret < 0) {
		LOG_ERR("Failed to bind TCP socket %d", errno);
		return -errno;
	}

	ret = zsock_listen(*sock, MAX_CLIENT_QUEUE);
	if (ret < 0) {
		LOG_ERR("Failed to listen on TCP socket %d", errno);
		ret = -errno;
	}

	return ret;
}
C

13. Set up the TCP client connection handler.

This function is responsible for receiving, processing, and parsing HTTP messages sent over TCP.

Note that this connection handler blocks indefinitely. There is no timeout or mechanism to handle a client that goes silent in the middle of an HTTP request, and errors such as incomplete or wrongly-formatted requests are not handled.

Copy
static void client_conn_handler(void *ptr1, void *ptr2, void *ptr3)
{
	ARG_UNUSED(ptr1);
	int *sock = ptr2;
	k_tid_t *in_use = ptr3;
	int received;
	int ret;
	char buf[1024];
	size_t offset = 0;
	size_t total_received = 0;
	struct http_req request = {
		.socket = *sock,
	};

	http_parser_init(&request.parser, HTTP_REQUEST);

	while (1) {
  	/* Receive TCP fragment */
		received = zsock_recv(request.socket, buf + offset, sizeof(buf) - offset, 0);
		if (received == 0) {
			/* Connection closed */
			LOG_INF("[%d] Connection closed by peer", request.socket);
			break;
		} else if (received < 0) {
			/* Socket error */
			ret = -errno;
			LOG_ERR("[%d] Connection error %d", request.socket, ret);
			break;
		}

		/* Parse the received data as HTTP request */
		(void)http_parser_execute(&request.parser,
					  &parser_settings, buf + offset, received);

		total_received += received;
		offset += received;

		if (offset >= sizeof(buf)) {
			offset = 0;
		}

   /* If HTTP request completely received, process the request */
		if (request.received_all) {
			handle_http_request(&request);
			break;
		}
	};

	(void)zsock_close(request.socket);

	*sock = -1;
	*in_use = NULL;
}
C

14. Setup functions to handle incoming TCP connections

14.1 Define a function that handles incoming TCP connections.

Define the function process_tcp() that accepts incoming TCP connections and creates a new thread to handle that connection.

Copy
static int process_tcp(int *sock, int *accepted)
{
	static int counter;
	int client;
	int slot;
	struct sockaddr_in client_addr;
	socklen_t client_addr_len = sizeof(client_addr);
	char addr_str[INET_ADDRSTRLEN];

	client = zsock_accept(*sock, (struct sockaddr *)&client_addr,
			&client_addr_len);
	if (client < 0) {
		LOG_ERR("Error in accept %d, stopping server", -errno);
		return -errno;
	}

	slot = get_free_slot(accepted);
	if (slot < 0 || slot >= MAX_CLIENT_QUEUE) {
		LOG_ERR("Cannot accept more connections");
		zsock_close(client);
		return 0;
	}

	accepted[slot] = client;

	if (client_addr.sin_family == AF_INET) {
		tcp4_handler_tid[slot] = k_thread_create(
			&tcp4_handler_thread[slot], tcp4_handler_stack[slot],
			K_THREAD_STACK_SIZEOF(tcp4_handler_stack[slot]),
			(k_thread_entry_t)client_conn_handler, INT_TO_POINTER(slot),
			&accepted[slot], &tcp4_handler_tid[slot],	THREAD_PRIORITY, 0, K_NO_WAIT);
	}

	net_addr_ntop(client_addr.sin_family, &client_addr.sin_addr, addr_str, sizeof(addr_str));

	LOG_DBG("[%d] Connection #%d from %s", client, ++counter, addr_str);

	return 0;
}
C

14.2 Define a function to process incoming IPv4 clients

Define the function process_tcp4() that calls the setup_server() function to initialize the TCP server.

Copy
static void process_tcp4(void)
{
	int ret;
	struct sockaddr_in addr4 = {
		.sin_family = AF_INET,
		.sin_port =  htons(CONFIG_HTTP_SERVER_SAMPLE_PORT),
	};

	ret = setup_server(&tcp4_listen_sock, (struct sockaddr *)&addr4, sizeof(addr4));
	if (ret < 0) {
		return;
	}

	LOG_INF("Waiting for IPv4 HTTP connections on port %d, sock %d", CONFIG_HTTP_SERVER_SAMPLE_PORT, tcp4_listen_sock);
  LOG_INF("Connect to %s.%s:%d", CONFIG_NET_HOSTNAME, "local", CONFIG_HTTP_SERVER_SAMPLE_PORT);

	while (ret == 0) {
		ret = process_tcp(&tcp4_listen_sock, tcp4_accepted);
	}
}
C

15. Start listening.

15.1 Define the function to listen on the TCP socket

Copy
void start_listener(void)
{
	for (size_t i = 0; i < MAX_CLIENT_QUEUE; i++) {
		tcp4_accepted[i] = -1;
		tcp4_listen_sock = -1;

	}
	k_thread_start(tcp4_thread_id);
}
C

15.2 Start listening on the TCP socket.

Once a Wi-Fi connection has been established, call the start_listener() function in main() to start lisetning on the TCP socket for incoming requests.

Copy
start_listener();
C

16. Build and flash the application to your board.

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.

When you have connected to Wi-Fi, observe the messages printed on the terminal.

*** Booting nRF Connect SDK ***
*** Using Zephyr OS v3.7.99-1f8f3dc29142 ***
[00:00:00.655,242] <inf> net_config: Initializing network
[00:00:00.655,242] <inf> net_config: Waiting interface 1 (0x2000cda8) to be up...
[00:00:00.655,273] <inf> net_config: Running dhcpv4 client...
[00:00:00.657,623] <inf> wifi_supplicant: wpa_supplicant initialized
[00:00:00.693,756] <inf> Lesson5_Exercise3: Waiting for network to be connected
[00:04:33.246,856] <inf> net_dhcpv4: Received: 172.20.10.6
[00:04:33.247,070] <inf> net_config: IPv4 address: 172.20.10.6
[00:04:33.247,070] <inf> net_config: Lease time: 3600 seconds
[00:04:33.247,131] <inf> net_config: Subnet: 255.255.255.240
[00:04:33.247,161] <inf> net_config: Router: 172.20.10.1
[00:04:33.247,344] <inf> Lesson5_Exercise3: Network connected
[00:04:33.248,077] <inf> Lesson5_Exercise3: Waiting for IPv4 HTTP connections on port 80, sock 14
[00:04:33.248,107] <inf> Lesson5_Exercise3: Connect to academyserver.local:80
Terminal

17. Setup an HTTP Client to send messages to the server we created

There are several ways to setup an HTTP client. In this exercise, we will use the Postman application.

Postman is free desktop application, supporting Windows, macOS, and Linux, which allows you test and develop various APIs. In this exercise, we will use it to send HTTP PUT and GET requests and view the response.

Important

This exercise assumes a local connection. Therefore, you must ensure your Nordic device and the device you are running the HTTP client from are connected to the same network.

17.1 Download the Postman desktop application.

17.2 Launch the Postman desktop application and create a user account.

17.3 Select a workspace, then click New, then choose HTTP, as shown below

18. Send a GET message inquiring about the state of LED 2.

  1. Make sure to send a GET request
  2. Send to the HTTP address http://academyserver.local:80/led/2
  3. Press the Send button to send the request
  4. Observe the body of the response being 0 which represents the OFF command, meaning LED 2 is off.

19. Send a PUT request to turn LED 2 on.

19.1 To change the HTTP request type, select the arrow next to the GET message, then select PUT.

19.2 Change the body of the request to send the value 1 to represent the On command.

  1. Select Body to change the Body of the HTTP request
  2. Select the drop down menu to switch the data type
  3. Select raw to send a raw value
  4. Write the value 1 to represent the ON command.
  5. Press the Send button to send the request

19.3 Observe that LED 2 on your board lights up.

20. Repeat steps 18 and 19 with LED 1 using http://academyserver:80/led/1 as the URL.

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.