The Network Management API is used to send network requests or receive notifications on network events. at any level in the IP stack. The API allows applications, as well as network layer code itself, to call defined network routines at any level in the IP stack, or receive notifications on relevant network events. Defined procedure handlers are registered by using a NET_MGMT_REGISTER_REQUEST_HANDLER macro, and procedure requests are done through a single net_mgmt() API that invokes the registered handler for the corresponding request.
Enabling the API
To enable the Network Management API in your application, we can enable the following Kconfigs
In addition, you need to include the header file for the API
Copy
#include<zephyr/net/net_mgmt.h>
C
Wi-Fi management API
The Wi-Fi management API is used to manage Wi-Fi networks and is implemented in the wifi_mgmt module as part of the network L2 stack (zephyr/subsys/net/l2).
It contains the Wi-Fi relevant procedure requests for the Network Management API, such as NET_REQUEST_WIFI_CONNECT to connect to Wi-Fi and NET_REQUEST_WIFI_CONNECT_STORED to connect to Wi-Fi using stored credentials. Invoking this request will automatically configure connection parameters from stored credentials on the device.
In this course, we will be using the Connection Manager, a feature of nRF Connect SDK, to listen to the network interface and IP events to verify whether the network interface is ready. The Connection Manager allows applications to control the connectivity without consideration for the underlying network technologies, making it easy to switch between for example Wi-Fi and cellular connectivity.
The Kconfig CONFIG_NET_CONNECTION_MANAGER will add and start the connection manager in the application, and will raise the L4 events “connected” and “disconnected”.
Copy
CONFIG_NET_CONNECTION_MANAGER=y
Kconfig
Then we must tell the Connection Manager which L2 connectivity we are using by enabling CONFIG_L2_WIFI_CONNECTIVITY.
Copy
CONFIG_L2_WIFI_CONNECTIVITY=y
Kconfig
This will automatically select the following Kconfigs
To ensure there’s sufficient stack space for the Connection Manager monitor thread to handle the new events, we must increase the stack size, by setting the following Kconfig.
To enable Wi-Fi support for the nRF70 Series devices, we must first enable it in Sysbuild.
Recall
Recall from the nRF Connect SDK Fundamentals course that Sysbuild (System build) is a higher-level build system that can combine multiple other build systems, and is used to configure, build and flash multiple images as part of a single project.
This is done with SB_CONFIG_WIFI_NRF=y by adding the following line to the sysbuild.conf file.
Copy
SB_CONFIG_WIFI_NRF70=y
Kconfig
Now that we’ve enabled Wi-Fi in our application at the Sysbuild level, we also want to configure the Wi-Fi stack at the application level, through the prj.conf file.
This is done by enabling the following Kconfigs
Copy
CONFIG_WIFI=yCONFIG_WIFI_NM_WPA_SUPPLICANT=y
Kconfig
CONFIG_WIFI: Enables the general Wi-Fi drivers in the application
CONFIG_WIFI_NM_WPA_SUPPLICANT: Enables WPA (Wi-Fi Protected Access) supplicant as the network management backend for WIFI_NM. The WPA supplicant is primarily responsible for implementing the authentication phase of WPA, as well as network scanning, key exchange and roaming support.
Configuring the Wi-Fi stack
The optimize the performance and memory usage of the Wi-Fi stack, there are many configuration options to tweak.
We won’t go into all of them, but there are specifically two parameters in the nRF Wi-Fi driver that we will adjust
CONFIG_NRF70_RX_NUM_BUFS [1 – unlimited*] specifies the number of RX buffers that can be used by the nRF Wi-Fi driver. The number of buffers must be enough to keep up with the RX traffic, otherwise packets might be dropped. We will set this to 16, which can handle moderate traffic without excessive memory usage. Reducing this will impact the memory of the application.
CONFIG_NRF70_MAX_TX_AGGREGATION [1 – unlimited*] specifies the maximum number of frames that can be coalesced into a single Wi-Fi frame. More frames imply more coalescing opportunities but can add latency to the TX path as we wait for more frames to arrive. We will set this to 4 which provides moderature frame aggregation without excessive latency. Reducing this will impact the memory of the application and tune the performance.
*based on available memory in the nRF70 Series device
When connecting to Wi-Fi, the parameters are passed in the structure struct wifi_connect_req_params. Below we see some of the relevant members of this structure
SSID – SSID of your Wi-Fi network
PSK – PSK, typically a passphrase or password
SAE password (sae_password) – SAE password, if using WPA3
Band (band) – Wi-Fi band you want to connect to
Channel (channel) – Wi-Fi channel to use
Security – The security type to use (NONE, PSK, PSK_SHA256, SAW, WAPI, EAP, WEP, WPA_SPK)
MFP – Management frame protection options
Timeout – Connection timeout in seconds
Here is an example of populating the Wi-Fi parameters
All network management requests are called using net_mgmt(), which has the following signature
mgmt_request: a bitmask to indicate which stack layer is targeted, if a net_if object is implied and the specific management procedure being requested
iface: network interface being used, use the helper function net_if_get_first_wifi() (gets the first Wi-Fi network interface) or net_if_get_default() (gets the default network interface).
data: the Wi-Fi configuration parameters, stored in struct wifi_connect_req_params
len: the length of data, i.e sizeof(struct wifi_connect_req_params)
To request the Wi-Fi connection, we will invoke the procedure request with NET_REQUEST_WIFI_CONNECT from the Wi-Fi management API, as shown below
After we have requested a Wi-Fi connection, we want to register a callback function to listen to network events so the application is notified when the Wi-Fi connection has been established.
The callback handler function net_mgmt_event_handler_t must have the following signature
It is important to note that the NET_EVENT_L4_CONNECTED event is only triggered once your device has received an IP address, so CONFIG_DHCPV4 must be enabled in the application.
Define the callback function
Define the callback function net_mgmt_event_handler()
The Wi-Fi credentials library provides means to load and store Wi-Fi network credentials in the device. We will take a closer look at how to do this in the next topic, Wi-Fi Provisioning and in Exercise 2 of this lesson.
v2.9.0 – v2.8.0 (copy)
The Network Management API is used to send network requests or receive notifications on network events. at any level in the IP stack. The API allows applications, as well as network layer code itself, to call defined network routines at any level in the IP stack, or receive notifications on relevant network events. Defined procedure handlers are registered by using a NET_MGMT_REGISTER_REQUEST_HANDLER macro, and procedure requests are done through a single net_mgmt() API that invokes the registered handler for the corresponding request.
Enabling the API
To enable the Network Management API in your application, we can enable the following Kconfigs
In addition, you need to include the header file for the API
Copy
#include<zephyr/net/net_mgmt.h>
C
Wi-Fi management API
The Wi-Fi management API is used to manage Wi-Fi networks and is implemented in the wifi_mgmt module as part of the network L2 stack (zephyr/subsys/net/l2).
It contains the Wi-Fi relevant procedure requests for the Network Management API, such as NET_REQUEST_WIFI_CONNECT to connect to Wi-FI.
In this course, we will be using the Connection Manager, a feature of nRF Connect SDK, to listen to the network interface and IP events to verify whether the network interface is ready. The Connection Manager allows applications to control the connectivity without consideration for the underlying network technologies, making it easy to switch between for example Wi-Fi and cellular connectivity.
The Kconfig CONFIG_NET_CONNECTION_MANAGER will add and start the connection manager in the application, and will raise the L4 events “connected” and “disconnected”.
Copy
CONFIG_NET_CONNECTION_MANAGER=y
Kconfig
Then we must tell the Connection Manager which L2 connectivity we are using by enabling CONFIG_L2_WIFI_CONNECTIVITY.
Copy
CONFIG_L2_WIFI_CONNECTIVITY=y
Kconfig
This will automatically select the following Kconfigs
To ensure there’s sufficient stack space for the Connection Manager monitor thread to handle the new events, we must increase the stack size, by setting the following Kconfig.
To enable Wi-Fi support for the nRF70 Series devices, we must first enable it in Sysbuild.
Recall
Recall from the nRF Connect SDK Fundamentals course that Sysbuild (System build) is a higher-level build system that can combine multiple other build systems, and is used to configure, build and flash multiple images as part of a single project.
This is done with SB_CONFIG_WIFI_NRF=y by adding the following line to the sysbuild.conf file.
Copy
SB_CONFIG_WIFI_NRF70=y
Kconfig
Now that we’ve enabled Wi-Fi in our application at the Sysbuild level, we also want to configure the Wi-Fi stack at the application level, through the prj.conf file.
This is done by enabling the following Kconfigs
Copy
CONFIG_WIFI=yCONFIG_WIFI_NM_WPA_SUPPLICANT=y
Kconfig
CONFIG_WIFI: Enables the general Wi-Fi drivers in the application
CONFIG_WIFI_NM_WPA_SUPPLICANT: Enables WPA (Wi-Fi Protected Access) supplicant as the network management backend for WIFI_NM. The WPA supplicant is primarily responsible for implementing the authentication phase of WPA, as well as network scanning, key exchange and roaming support.
Configuring the Wi-Fi stack
The optimize the performance and memory usage of the Wi-Fi stack, there are many configuration options to tweak.
We won’t go into all of them, but there are specifically two parameters in the nRF Wi-Fi driver that we will adjust
CONFIG_NRF70_RX_NUM_BUFS [1 – unlimited*] specifies the number of RX buffers that can be used by the nRF Wi-Fi driver. The number of buffers must be enough to keep up with the RX traffic, otherwise packets might be dropped. We will set this to 16, which can handle moderate traffic without excessive memory usage. Reducing this will impact the memory of the application.
CONFIG_NRF70_MAX_TX_AGGREGATION [1 – unlimited*] specifies the maximum number of frames that can be coalesced into a single Wi-Fi frame. More frames imply more coalescing opportunities but can add latency to the TX path as we wait for more frames to arrive. We will set this to 4 which provides moderature frame aggregation without excessive latency. Reducing this will impact the memory of the application and tune the performance.
*based on available memory in the nRF70 Series device
When connecting to Wi-Fi, the parameters are passed in the structure struct wifi_connect_req_params. Below we see some of the relevant members of this structure
SSID – SSID of your Wi-Fi network
PSK – PSK, typically a passphrase or password
SAE password (sae_password) – SAE password, if using WPA3
Band (band) – Wi-Fi band you want to connect to
Channel (channel) – Wi-Fi channel to use
Security – The security type to use (NONE, PSK, PSK_SHA256, SAW, WAPI, EAP, WEP, WPA_SPK)
MFP – Management frame protection options
Timeout – Connection timeout in seconds
Here is an example of populating the Wi-Fi parameters
All network management requests are called using net_mgmt(), which has the following signature
mgmt_request: a bitmask to indicate which stack layer is targeted, if a net_if object is implied and the specific management procedure being requested
iface: network interface being used, use the helper function net_if_get_first_wifi() (gets the first Wi-Fi network interface) or net_if_get_default() (gets the default network interface).
data: the Wi-Fi configuration parameters, stored in struct wifi_connect_req_params
len: the length of data, i.e sizeof(struct wifi_connect_req_params)
To request the Wi-Fi connection, we will invoke the procedure request with NET_REQUEST_WIFI_CONNECT from the Wi-Fi management API, as shown below
After we have requested a Wi-Fi connection, we want to register a callback function to listen to network events so the application is notified when the Wi-Fi connection has been established.
The callback handler function net_mgmt_event_handler_t must have the following signature
It is important to note that the NET_EVENT_L4_CONNECTED event is only triggered once your device has received an IP address, so CONFIG_DHCPV4 must be enabled in the application.
Define the callback function
Define the callback function net_mgmt_event_handler()
The Wi-Fi management extension library adds a procedure request for an automatic connection feature with NET_REQUEST_WIFI_CONNECT_STORED. Invoking this request will automatically configure connection parameters from stored credentials on the device.
Add the library to your application through the following Kconfig
Copy
CONFIG_WIFI_MGMT_EXT=y
Kconfig
Include the header file for the library in the main.c file of your application
Copy
#include<net/wifi_mgmt_ext.h>
C
The following code snippet is an example of how to invoke this procedure request with net_mgmt().
Notice that we are passing NULL to the data parameter, as opposed to when invoking NET_REQUEST_WIFI_CONNECT. This is because the Wi-Fi management extension library creates the connection parameters from credentials stored on the device.
More on this
The Wi-Fi credentials library provides means to load and store Wi-Fi network credentials in the device. We will take a closer look at how to do this in the next topic, Wi-Fi Provisioning and in Exercise 2 of this lesson.
v2.9.0 – v2.8.0 (copy)
The Network Management API is used to send network requests or receive notifications on network events. The API allows applications, as well as network layer code itself, to call defined network routines at any level in the IP stack, or receive notifications on relevant network events. Procedure requests are done through a single net_mgmt() API that invokes the registered handler for the corresponding request.
Enabling the API
To enable the Network Management API in your application, we can enable the following Kconfigs
wifi_mgmt.h: Header file for Wi-Fi specific Network Management API’s
net_mgmt.h: Header file for the Network Management API
In this course, we will be using the network connection manager, an experimental feature of nRF Connect SDK, to listen to the network interface and IP events to verify whether an interface is connected or not.
The Kconfig CONFIG_NET_CONNECTION_MANAGER will add and start the connection manager in the application, and will raise L4 events “connected” and “disconnected”,
Copy
CONFIG_NET_CONNECTION_MANAGER=y
Kconfig
Enabling Wi-Fi
To be able to use the Network Management API to connect to Wi-Fi, we also need to enable Wi-Fi in the application.
CONFIG_WPA_SUPP: Enables WPA (Wi-Fi Protected Access) supplicant support, primarily responsible for implementing the authentication phase of WPA, as well as network scanning, key exchange and roaming support.
Configure the Wi-Fi parameters
When connecting to Wi-Fi, the parameters are passed in the structure struct wifi_connect_req_params, which has the following signature
SSID – SSID of your Wi-Fi network
PSK – PSK, typically a passphrase or password
SAE password (sae_password) – SAE password, if using WPA3
Band (band) – Wi-Fi band you want to connect to
Channel (channel) – Wi-Fi channel to use
Security – The security type to use (NONE, PSK, PSK_SHA256, SAW, WAPI, EAP, WEP, WPA_SPK)
MFP – Management frame protection options
Timeout – Connection timeout in seconds
Here is an example of populating the Wi-Fi parameters
All network management requests are called using net_mgmt(), which has the following signature
mgmt_request: a bitmask to indicate which stack layer is targeted, if a net_if object is implied and the specific management procedure being requested
iface: network interface being used, use the helper function net_if_get_first_wifi() (gets the first Wi-Fi network interface) or net_if_get_default() (gets the default network interface).
data: the Wi-Fi configuration parameters, stored in struct wifi_connect_req_params
len: the length of data, i.e sizeof(struct wifi_connect_req_params)
To request the Wi-Fi connection, we will use the command NET_REQUEST_WIFI_CONNECT, as shown below
After we have requested a Wi-Fi connection, we want to register a callback function to listen to network events so the application is notified when the Wi-Fi connection has been established.
The callback handler function net_mgmt_event_handler_t must have the following signature
However, we will instead be using the events defined in the network connection manager: NET_EVENT_L4_CONNECTED and NET_EVENT_L4_DISCONNECTED. The network connection manager adds a layer of abstraction to your application to easily be able to port an application between different connection protocols, for example, Wi-Fi and cellular.
It is important to note that the NET_EVENT_L4_CONNECTED event is only triggered once your device has received an IP address, so CONFIG_DHCPV4 must be enabled in the application.
Define the callback function
Define the callback function net_mgmt_event_handler()
The Wi-Fi management extension library adds an automatic connect feature to the Wi-Fi stack, by using the NET_REQUEST_WIFI_CONNECT_STORED command in net_mgmt().
Add the library to your application through the following Kconfig
Copy
CONFIG_WIFI_MGMT_EXT=y
Kconfig
Include the header file for the library in the main.c file of your application
Please note that although this is the most configurable way to request a Wi-Fi connection, since you can configure struct wifi_connect_req_params, it requires inputting Wi-Fi credentials into the application firmware and is therefore not secure and not recommended in production, but rather for development purposes. We will take a look at a more secure way to provision the network credentials in Exercise 2 of this lesson.
v2.9.0 – v2.8.0 (copy)
The Network Management API is used to send network requests or receive notifications on network events. The API allows applications, as well as network layer code itself, to call defined network routines at any level in the IP stack, or receive notifications on relevant network events. Procedure requests are done through a single net_mgmt() API that invokes the registered handler for the corresponding request.
Enabling the API
To enable the Network Management API in your application, we can enable the following Kconfigs
wifi_mgmt.h: Header file for Wi-Fi specific Network Management API’s
net_mgmt.h: Header file for the Network Management API
In this course, we will be using the network connection manager, an experimental feature of nRF Connect SDK, to listen to the network interface and IP events to verify whether an interface is connected or not.
The Kconfig CONFIG_NET_CONNECTION_MANAGER will add and start the connection manager in the application, and will raise L4 events “connected” and “disconnected”,
Copy
CONFIG_NET_CONNECTION_MANAGER=y
Kconfig
Enabling Wi-Fi
To be able to use the Network Management API to connect to Wi-Fi, we also need to enable Wi-Fi in the application.
CONFIG_WPA_SUPP: Enables WPA (Wi-Fi Protected Access) supplicant support, primarily responsible for implementing the authentication phase of WPA, as well as network scanning, key exchange and roaming support.
Configure the Wi-Fi parameters
When connecting to Wi-Fi, the parameters are passed in the structure struct wifi_connect_req_params, which has the following signature
SSID – SSID of your Wi-Fi network
PSK – PSK, typically a passphrase or password
SAE password (sae_password) – SAE password, if using WPA3
Band (band) – Wi-Fi band you want to connect to
Channel (channel) – Wi-Fi channel to use
Security – The security type to use (NONE, PSK, PSK_SHA256, SAW, WAPI, EAP, WEP, WPA_SPK)
MFP – Management frame protection options
Timeout – Connection timeout in seconds
Here is an example of populating the Wi-Fi parameters
All network management requests are called using net_mgmt(), which has the following signature
mgmt_request: a bitmask to indicate which stack layer is targeted, if a net_if object is implied and the specific management procedure being requested
iface: network interface being used, use the helper function net_if_get_first_wifi() (gets the first Wi-Fi network interface) or net_if_get_default() (gets the default network interface).
data: the Wi-Fi configuration parameters, stored in struct wifi_connect_req_params
len: the length of data, i.e sizeof(struct wifi_connect_req_params)
To request the Wi-Fi connection, we will use the command NET_REQUEST_WIFI_CONNECT, as shown below
After we have requested a Wi-Fi connection, we want to register a callback function to listen to network events so the application is notified when the Wi-Fi connection has been established.
The callback handler function net_mgmt_event_handler_t must have the following signature
However, we will instead be using the events defined in the network connection manager: NET_EVENT_L4_CONNECTED and NET_EVENT_L4_DISCONNECTED. The network connection manager adds a layer of abstraction to your application to easily be able to port an application between different connection protocols, for example, Wi-Fi and cellular.
It is important to note that the NET_EVENT_L4_CONNECTED event is only triggered once your device has received an IP address, so CONFIG_DHCPV4 must be enabled in the application.
Define the callback function
Define the callback function net_mgmt_event_handler()
The Wi-Fi management extension library adds an automatic connect feature to the Wi-Fi stack, by using the NET_REQUEST_WIFI_CONNECT_STORED command in net_mgmt().
Add the library to your application through the following Kconfig
Copy
CONFIG_WIFI_MGMT_EXT=y
Kconfig
Include the header file for the library in the main.c file of your application
Please note that although this is the most configurable way to request a Wi-Fi connection, since you can configure struct wifi_connect_req_params, it requires inputting Wi-Fi credentials into the application firmware and is therefore not secure and not recommended in production, but rather for development purposes. We will take a look at a more secure way to provision the network credentials in Exercise 2 of this lesson.
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.