To learn how to set up I2C in nRF Connect SDK, we will focus on the I2C controller API.
Enabling driver
1. Enable the I2C driver by adding the following line into the application configuration file prj.conf.
Copy
CONFIG_I2C=y
Kconfig
2. Include the header file of the I2C API in your source code file.
Copy
#include<zephyr/drivers/i2c.h>
C
Initializing the device
Just like the GPIO driver covered in lesson 2, the generic I2C driver in Zephyr has an API-specific struct i2c_dt_spec, with the following signature:
This structure contains the device pointer for the I2C bus const struct device*bus and the target address uint16_t addr.
To retrieve this structure, we need to use the API-specific function I2C_DT_SPEC_GET(), which has the following signature:
3. Specify which I2C controller your device (sensor) is connected to and its I2C address.
If the sensor is not already defined in the board’s devicetree, you need to manually add your sensor as a child devicetree node to the i2c controller, using a devicetree overlay file.
Important
This step depends on whether the I2C target device is already defined in your board’s files or not. In the case of the Thingy:91 and Thingy:91 X, the sensors are already defined as child nodes of their I2C controller. See for example the devicetree file of the Thingy:91, available in <install_path>\nrf\boards\nordic\thingy91\thingy91_nrf9160_common.dts. The BME680 and BH1749 sensors are already added as child nodes in the i2c2-controller they are connected to.
3.1 Create overlay files. As we learned in Lesson 3, from the details view, expand Config files->Devicetree and create an overlay file.
This will create an empty overlay file in your application root directory.
You can also create your overlay files manually. The files must end with the .overlay extension, and the name should match the board target of your device. It’s recommended to store your overlay files in a dedicated subfolder called “boards” in your application folder. However, saving them in the root directory of your application is also acceptable.
For example, if your board target is nrf52840dk/nrf52840, the corresponding overlay should be named nrf52840dk_nrf52840.overlay . Basically / is substituted with _ .
3.2 In the overlay file, specify the I2C controller that your sensor is connected to and its address.
Depending on the Nordic chip used, there can be more than one I2C controller, so make sure to select the controller that is connected to your sensor.
This can be confirmed by checking the schematic of your board or development kit to locate the pins connected to SDA and SCL. We will examine this in the exercise section of this lesson. You can use the DeviceTree viewer in VS Code to display the devicetree nodes for the available I2C controllers, which will tell you which pins are used by the controller
In the below illustration, we are assuming that the sensor is connected to the i2c0 controller and it has the target address 0x4a (from the sensor datasheet), and we are labeling it mysensor.
At a minimum, you need to specify the compatible, the address of the i2c target device, and its label.
Note, for the compatible member you could specify the driver for the sensor if one exists in the SDK. However, the focus of this lesson is on raw I2C transactions.
4. Define the node identifier
The line below uses the devicetree macro DT_NODELABEL() to get the node identifier symbol I2C0_NODE, which will represent the I2C hardware controller i2c0.
Copy
#define I2C0_NODE DT_NODELABEL(mysensor)
C
I2C0_NODE contains information about the pins used for SDA and SCL, a memory map of the I2C controller, the default I2C frequency, and the address of the target device.
DeviceTree View in nRF Connect for VS Code
SDA and SCL pins for &i2c0 node
5. Retrieve the API-specific device structure.
The macro call I2C_DT_SPEC_GET() returns the structure i2c_dt_spec, which contains the device pointer for the I2C bus, as well as the target address.
6. Use device_is_ready() to verify that the device is ready to use.
Copy
if (!device_is_ready(dev_i2c.bus)) {printk("I2C bus %s is not ready!\n\r",dev_i2c.bus->name);return;}
C
We now have a device struct i2c_dt_spec *dev_i2c that we can pass to the I2C generic API interface to perform read/write operations.
I2C Write
The simplest way to write to a target device is through the function i2c_write_dt(), which has the following signature:
For example, the following code snippet writes 2 bytes to an I2C target device.
Specifically, we are writing the value 0x8C to the internal register 0x03 on the I2C device.
Copy
uint8_tconfig[2] = {0x03,0x8C};ret = i2c_write_dt(&dev_i2c, config, sizeof(config));if(ret != 0){printk("Failed to write to I2C device address %x at reg. %x\n\r", dev_i2c.addr,config[0]);}
C
I2C Read
The simplest way to read from an I2C target device is through the function i2c_read_dt(), which has the following signature:
This function requires that you first call i2c_write_dt() to the internal register you want to read from.
For example, the following code snippet reads 1 byte from the internal register 0x03 from the I2C target device, assuming we called the previous write-code snippet prior to calling this one.
Copy
uint8_t data;ret = i2c_read_dt(&dev_i2c, &data, sizeof(data));if(ret != 0){printk("Failed to read from I2C device address %x at Reg. %x\n\r", dev_i2c.addr,config[0]);}
C
Alternatively, you can use i2c_reg_read_byte_dt() which combines the register address write and data read into one function call. This function is ideal for straightforward reads of a single byte from a device.
Another way to read from an I2C device is by using the i2c_burst_read_dt() function. This function reads data from multiple registers sequentially. It has the following signature:
For example, the following code snippet reads data from 3 registers/6 bytes starting from the 1st byte of the register pointed to by the address “BH1749_RED_DATA_LSB”.
Copy
uint8_trgb_value[6]= {0};//Do a burst read of 6 bytes as each color channel is 2 bytesret = i2c_burst_read_dt(&dev_i2c, BH1749_RED_DATA_LSB,rgb_value,sizeof(rgb_value));
C
This function is used and explained in more detail in exercise 2 of this lesson.
I2C Write/Read
With I2C devices, it is very common to perform a write and a read data back to back by using the function i2c_write_read_dt(), which has the following signature:
A common scenario for this is to first write the address of an internal register to be read, then directly follow with a read to get the content of that register. We will demonstrate this in more detail in the exercise section of this lesson.
For example, the following code snippet writes the value sensor_regs[0] = 0x02 to the I2C device at the address 0x4A and then reads 1 byte from that same device and saves it in the variable temp_reading[0].
Copy
uint8_tsensor_regs[2] ={0x02,0x00};uint8_ttemp_reading[2]= {0}; int ret = i2c_write_read_dt(&dev_i2c,&sensor_regs[0],1,&temp_reading[0],1);if(ret != 0){printk("Failed to write/read I2C device address %x at Reg. %x\n\r", dev_i2c.addr,sensor_regs[0]);}
C
v3.0.0
To learn how to set up I2C in nRF Connect SDK, we will focus on the I2C controller API.
Enabling driver
1. Enable the I2C driver by adding the following line into the application configuration file prj.conf.
Copy
CONFIG_I2C=y
Kconfig
2. Include the header file of the I2C API in your source code file.
Copy
#include<zephyr/drivers/i2c.h>
C
Initializing the device
Just like the GPIO driver covered in lesson 2, the generic I2C driver in Zephyr has an API-specific struct i2c_dt_spec, with the following signature:
This structure contains the device pointer for the I2C bus const struct device*bus and the target address uint16_t addr.
To retrieve this structure, we need to use the API-specific function I2C_DT_SPEC_GET(), which has the following signature:
3. Specify which I2C controller your device (sensor) is connected to and its I2C address.
If the sensor is not already defined in the board’s devicetree, you need to manually add your sensor as a child devicetree node to the i2c controller, using a devicetree overlay file.
Important
This step depends on whether the I2C target device is already defined in your board’s files or not. In the case of the Thingy:91 and Thingy:91 X, the sensors are already defined as child nodes of their I2C controller. See for example the devicetree file of the Thingy:91, available in <install_path>\nrf\boards\nordic\thingy91\thingy91_nrf9160_common.dts. The BME680 and BH1749 sensors are already added as child nodes in the i2c2-controller they are connected to.
3.1 Create overlay files. As we learned in Lesson 3, from the details view, expand Config files->Devicetree and create an overlay file.
This will create an empty overlay file in your application root directory.
You can also create your overlay files manually. The files must end with the .overlay extension, and the name should match the board target of your device. It’s recommended to store your overlay files in a dedicated subfolder called “boards” in your application folder. However, saving them in the root directory of your application is also acceptable.
For example, if your board target is nrf52840dk/nrf52840, the corresponding overlay should be named nrf52840dk_nrf52840.overlay . Basically / is substituted with _ .
3.2 In the overlay file, specify the I2C controller that your sensor is connected to and its address.
Depending on the Nordic chip used, there can be more than one I2C controller, so make sure to select the controller that is connected to your sensor.
This can be confirmed by checking the schematic of your board or development kit to locate the pins connected to SDA and SCL. We will examine this in the exercise section of this lesson. You can use the DeviceTree viewer in VS Code to display the devicetree nodes for the available I2C controllers, which will tell you which pins are used by the controller
In the below illustration, we are assuming that the sensor is connected to the i2c0 controller and it has the target address 0x4a (from the sensor datasheet), and we are labeling it mysensor.
At a minimum, you need to specify the compatible, the address of the i2c target device, and its label.
Note, for the compatible member you could specify the driver for the sensor if one exists in the SDK. However, the focus of this lesson is on raw I2C transactions.
4. Define the node identifier
The line below uses the devicetree macro DT_NODELABEL() to get the node identifier symbol I2C0_NODE, which will represent the I2C hardware controller i2c0.
Copy
#define I2C0_NODE DT_NODELABEL(mysensor)
C
I2C0_NODE contains information about the pins used for SDA and SCL, a memory map of the I2C controller, the default I2C frequency, and the address of the target device.
DeviceTree View in nRF Connect for VS Code
SDA and SCL pins for &i2c0 node
5. Retrieve the API-specific device structure.
The macro call I2C_DT_SPEC_GET() returns the structure i2c_dt_spec, which contains the device pointer for the I2C bus, as well as the target address.
6. Use device_is_ready() to verify that the device is ready to use.
Copy
if (!device_is_ready(dev_i2c.bus)) {printk("I2C bus %s is not ready!\n\r",dev_i2c.bus->name);return;}
C
We now have a device struct i2c_dt_spec *dev_i2c that we can pass to the I2C generic API interface to perform read/write operations.
I2C Write
The simplest way to write to a target device is through the function i2c_write_dt(), which has the following signature:
For example, the following code snippet writes 2 bytes to an I2C target device.
Specifically, we are writing the value 0x8C to the internal register 0x03 on the I2C device.
Copy
uint8_tconfig[2] = {0x03,0x8C};ret = i2c_write_dt(&dev_i2c, config, sizeof(config));if(ret != 0){printk("Failed to write to I2C device address %x at reg. %x\n\r", dev_i2c.addr,config[0]);}
C
I2C Read
The simplest way to read from an I2C target device is through the function i2c_read_dt(), which has the following signature:
This function requires that you first call i2c_write_dt() to the internal register you want to read from.
For example, the following code snippet reads 1 byte from the internal register 0x03 from the I2C target device, assuming we called the previous write-code snippet prior to calling this one.
Copy
uint8_t data;ret = i2c_read_dt(&dev_i2c, &data, sizeof(data));if(ret != 0){printk("Failed to read from I2C device address %x at Reg. %x\n\r", dev_i2c.addr,config[0]);}
C
Alternatively, you can use i2c_reg_read_byte_dt() which combines the register address write and data read into one function call. This function is ideal for straightforward reads of a single byte from a device.
Another way to read from an I2C device is by using the i2c_burst_read_dt() function. This function reads data from multiple registers sequentially. It has the following signature:
For example, the following code snippet reads data from 3 registers/6 bytes starting from the 1st byte of the register pointed to by the address “BH1749_RED_DATA_LSB”.
Copy
uint8_trgb_value[6]= {0};//Do a burst read of 6 bytes as each color channel is 2 bytesret = i2c_burst_read_dt(&dev_i2c, BH1749_RED_DATA_LSB,rgb_value,sizeof(rgb_value));
C
This function is used and explained in more detail in exercise 2 of this lesson.
I2C Write/Read
With I2C devices, it is very common to perform a write and a read data back to back by using the function i2c_write_read_dt(), which has the following signature:
A common scenario for this is to first write the address of an internal register to be read, then directly follow with a read to get the content of that register. We will demonstrate this in more detail in the exercise section of this lesson.
For example, the following code snippet writes the value sensor_regs[0] = 0x02 to the I2C device at the address 0x4A and then reads 1 byte from that same device and saves it in the variable temp_reading[0].
Copy
uint8_tsensor_regs[2] ={0x02,0x00};uint8_ttemp_reading[2]= {0}; int ret = i2c_write_read_dt(&dev_i2c,&sensor_regs[0],1,&temp_reading[0],1);if(ret != 0){printk("Failed to write/read I2C device address %x at Reg. %x\n\r", dev_i2c.addr,sensor_regs[0]);}
C
v3.0.0
To learn how to set up I2C in nRF Connect SDK, we will focus on the I2C controller API.
Enabling driver
1. Enable the I2C driver by adding the following line into the application configuration file prj.conf.
Copy
CONFIG_I2C=y
Kconfig
2. Include the header file of the I2C API in your source code file.
Copy
#include<zephyr/drivers/i2c.h>
C
Initializing the device
Just like the GPIO driver covered in lesson 2, the generic I2C driver in Zephyr has an API-specific struct i2c_dt_spec, with the following signature:
This structure contains the device pointer for the I2C bus const struct device*bus and the target address uint16_t addr.
To retrieve this structure, we need to use the API-specific function I2C_DT_SPEC_GET(), which has the following signature:
3. Specify which I2C controller your device (sensor) is connected to and its I2C address.
If the sensor is not already defined in the board’s devicetree, you need to manually add your sensor as a child devicetree node to the i2c controller, using a devicetree overlay file.
Important
This step depends on whether the I2C target device is already defined in your board’s files or not. In the case of the Thingy:91, the sensors are already defined as child nodes of their I2C controller and you can skip this step (step 3.1 and step 3.2). See the devicetree file of the Thingy:91, available in <install_path>\nrf\boards\arm\thingy91_nrf9160thingy91_nrf9160_common.dts.
Notice that the BME680 and BH1749 sensors are already added as child nodes in the i2c2-controller they are connected to.
3.1 Create overlay files. As we learned in Lesson 3, from the details panel, expand Input files and create an overlay file.
This will create an empty overlay file in your application root directory.
3.2 In the overlay file, specify the I2C controller that your sensor is connected to and its address.
Note
Depending on the Nordic chip used, there can be more than one I2C controller, so make sure to select the controller that is connected to your sensor.
This can be confirmed by checking the schematic of your board or development kit to locate the pins connected to SDA and SCL. We will examine this in the exercise section of this lesson. You can use the DeviceTree viewer in VS Code to display the devicetree nodes for the available I2C controllers, which will tell you which pins are used by the controller
In the below illustration, we are assuming that the sensor is connected to the i2c0 controller and it has the target address 0x4a (from the sensor datasheet), and we are labeling it mysensor.
At a minimum, you need to specify the compatible, the address of the i2c target device, and its label.
Note, for the compatible member you could specify the driver for the sensor if one exists in the SDK. However, the focus of this lesson is on raw I2C transactions.
4. Define the node identifier
The line below uses the devicetree macro DT_NODELABEL() to get the node identifier symbol I2C0_NODE, which will represent the I2C hardware controller i2c0.
Copy
#define I2C0_NODE DT_NODELABEL(mysensor)
C
I2C0_NODE contains information about the pins used for SDA and SCL, a memory map of the I2C controller, the default I2C frequency, and the address of the target device.
5. Retrieve the API-specific device structure.
The macro call I2C_DT_SPEC_GET() returns the structure i2c_dt_spec, which contains the device pointer for the I2C bus, as well as the target address.
6. Use device_is_ready() to verify that the device is ready to use.
Copy
if (!device_is_ready(dev_i2c.bus)) {printk("I2C bus %s is not ready!\n\r",dev_i2c.bus->name);return;}
C
We now have a device struct i2c_dt_spec *dev_i2c that we can pass to the I2C generic API interface to perform read/write operations.
I2C Write
The simplest way to write to a target device is through the function i2c_write_dt(), which has the following signature:
For example, the following code snippet writes 2 bytes to an I2C target device.
Copy
uint8_tconfig[2] = {0x03,0x8C};ret = i2c_write_dt(&dev_i2c, config, sizeof(config));if(ret != 0){printk("Failed to write to I2C device address %x at reg. %x\n\r", dev_i2c.addr,config[0]);}
C
I2C Read
1. The simplest way to read from an I2C target device is through the function i2c_read_dt(), which has the following signature:
For example, the following code snippet reads 1 byte from an I2C target device.
Copy
uint8_t data;ret = i2c_read_dt(&dev_i2c, &data, sizeof(data));if(ret != 0){printk("Failed to read from I2C device address %x at Reg. %x\n\r", dev_i2c.addr,config[0]);}
C
2. Another way to read from an I2C device is by using the i2c_burst_read_dt()function. This function reads data from multiple registers sequentially. It has the following signature:
For example, the following code snippet reads data from 3 registers/6 bytes starting from the 1st byte of the register pointed to by the address “BH1749_RED_DATA_LSB”.
Copy
uint8_trgb_value[6]= {0};//Do a burst read of 6 bytes as each color channel is 2 bytesret = i2c_burst_read_dt(&dev_i2c, BH1749_RED_DATA_LSB,rgb_value,sizeof(rgb_value));
C
This function is used and explained in more detail in exercise 2 of this lesson.
I2C Write/Read
With I2C devices, it is very common to perform a write and a read data back to back by using the function i2c_write_read_dt(), which has the following signature:
A common scenario for this is to first write the address of an internal register to be read, then directly follow with a read to get the content of that register. We will demonstrate this in more detail in the exercise section of this lesson.
For example, the following code snippet writes the value sensor_regs[0] = 0x02 to the I2C device at the address 0x4A and then reads 1 byte from that same device and saves it in the variable temp_reading[0].
Copy
uint8_tsensor_regs[2] ={0x02,0x00};uint8_ttemp_reading[2]= {0}; int ret = i2c_write_read_dt(&dev_i2c,&sensor_regs[0],1,&temp_reading[0],1);if(ret != 0){printk("Failed to write/read I2C device address %x at Reg. %x\n\r", dev_i2c.addr,sensor_regs[0]);}
C
v3.0.0
To learn how to set up I2C in nRF Connect SDK, we will focus on the I2C controller API. In order to use the I2C API we need to perform the following steps in order.
Enabling driver
1. Enable the I2C driver by adding the following line into the application configuration file prj.conf.
CONFIG_I2C=y
2. Include the header file of the I2C API in your source code file.
#include <drivers/i2c.h>
3. Get the label property of the I2C controller devicetree node and make sure that the controller is enabled. The label is an important parameter that we will pass to generate the binding of the device driver through the device_get_binding() function.
DeviceTree View in nRF Connect for VS Code
SDA and SCL pins for i2c0 node
3.1 Get a node identifier for the I2C controller devicetree node. This is done using the macro DT_NODELABEL().
#define I2C0_NODE DT_NODELABEL(i2c0)
The line above creates the node identifier symbol I2C0_NODE from the devicetree node i2c0 . The I2C0_NODE is now representing the I2C hardware controller. I2C0_NODE contains information about the pins used for SDA and SCL, a memory map of the controller, the default I2C frequency, and the label property associated with the node.
3.2 Make sure that the status of the node is set to okay, meaning that the device is enabled. This is done through the macro DT_NODE_HAS_STATUS().
DT_NODE_HAS_STATUS(I2C0_NODE, okay)
3.3 Get the label property of the node. The label is an important parameter that we will pass to the device_get_binding() function. This is done through the micro DT_LABEL().
#define I2C0 DT_LABEL(I2C0_NODE)
It is recommended to place the code that checks for the status of the node inside a conditional compilation, as shown below:
/* The devicetree node identifier for the "i2c0" */
#define I2C0_NODE DT_NODELABEL(i2c0)
#if DT_NODE_HAS_STATUS(I2C0_NODE, okay)
#define I2C0 DT_LABEL(I2C0_NODE)
#else
/* A build error here means your board does not have I2C enabled. */
#error "i2c0 devicetree node is disabled"
#define I2C0 ""
#endif
An error will be generated (i2c0 devicetree node is disabled) and the code will not compile if i2c0 node’s status is not set to "okay" .
4. Now that we have the label property of the I2C controller devicetree node, we can simply get the binding through the function device_get_binding():
const struct device *dev_i2c = device_get_binding(I2C0);
if (dev_i2c == NULL) {
printk("Could not find %s!\n\r",I2C0);
return;
}
We now have a pointer dev_i2c of type struct device that we can pass to the I2C generic API interface to perform read/write operations.
I2C Write
The simplest way to write to a slave device is through the function i2c_write(), which has the following signature:
For example, the following code snippet writes 2 bytes to an I2C slave device at the address 0x4A.
uint8_t config[2] = {0x03,0x8C};
ret = i2c_write(dev_i2c, config, sizeof(config), 0x4A);
if(ret != 0){
printk("Failed to write to I2C device address %x at Reg. %x \n", 0x4A,config[0]);
}
I2C Read
The simplest way to read from an I2C slave device is through the function i2c_read(), which has the following signature:
For example, the following code snippet reads 1 byte from an I2C slave device at the address 0x4A.
uint8_t data;
ret = i2c_read(dev_i2c, &data, sizeof(data), 0x4A);
if(ret != 0){
printk("Failed to read from I2C device address %x at Reg. %x \n", 0x4A,config[0]);
}
I2C Write/Read
With I2C devices, it is very common to perform a write and a read data back to back by using the function i2c_write_read(), which has the following signature:
A common scenario for this is to first write the address of an internal register to be read, then directly follow with a read to get the content of that register. We will demonstrate this in more detail in the exercise section of this lesson.
For example, the following code snippet writes the value sensor_regs[0] = 0x02 to the I2C device at the address 0x4A and then reads 1 byte from that same device and saves it in the variable temp_reading[0].
uint8_t sensor_regs[2] ={0x02,0x00};
uint8_t temp_reading[2]= {0};
int ret = i2c_write_read(dev_i2c,0x4A,&sensor_regs[0],1,&temp_reading[0],1);
if(ret != 0){
printk("Failed to write/read I2C device address %x at Reg. %x \n", 0x4A,sensor_regs[0]);
}
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.
