Feedback

Exercise 2 – Interfacing with ADC using nrfx driver and software timers

v3.2.0
v3.1.0 – v3.0.0

v3.2.0

In this exercise, we will explore the simple mode of the nrfx SAADC driver to measure a voltage source (e.g., a battery) at a regular interval using a software timer.

Exercise steps

Open the code base of the exercise by navigating to Create a new application in the nRF Connect for VS Code extension, select Copy a sample, and search for Lesson 6 – Exercise 2.

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

1. Enable the SAADC driver.

Let’s enable the SAADC driver by adding the following line in the application configuration file prj.conf.

CONFIG_NRFX_SAADC=y

Copy

CONFIG_NRFX_SAADC=y

Kconfig

2. Include the SAADC header file.

Add SAADC-related header file by including the following line to main.c

#include <nrfx_saadc.h>

Copy

#include <nrfx_saadc.h>

3. Declare objects to be used later in the initialization process.

We need to declare some objects that will be used later in the initialization process.

3.1 Declare the struct to hold the configuration for the SAADC channel used to sample the battery voltage. The macro will assign default configuration parameters for a single-ended input. The configuration can be changed later.

All other DKs
nRF54L Series DK

#define SAADC_INPUT_PIN NRFX_ANALOG_EXTERNAL_AIN0
static nrfx_saadc_channel_t channel = NRFX_SAADC_DEFAULT_CHANNEL_SE(SAADC_INPUT_PIN, 0);

Copy

#define SAADC_INPUT_PIN NRFX_ANALOG_EXTERNAL_AIN0
static nrfx_saadc_channel_t channel = NRFX_SAADC_DEFAULT_CHANNEL_SE(SAADC_INPUT_PIN, 0);

#de#define SAADC_INPUT_PIN NRFX_ANALOG_EXTERNAL_AIN4
static nrfx_saadc_channel_t channel = NRFX_SAADC_DEFAULT_CHANNEL_SE(SAADC_INPUT_PIN, 0);

Copy

#de#define SAADC_INPUT_PIN NRFX_ANALOG_EXTERNAL_AIN4
static nrfx_saadc_channel_t channel = NRFX_SAADC_DEFAULT_CHANNEL_SE(SAADC_INPUT_PIN, 0);

We are using AIN4 for nRF54L Series since the GPIO shared with AIN0 by default is used for one of the UARTE instances on the nRF54L Series DK.

Connect a battery between GND and the analog input (AIN0 or AIN4, depending on your target). Check the Hardware and Layout ->Pin assignment chapter in the Product specification to know which Pin is connected to the analog inputs on your choice of SoC/SiP. You can also connect a jumper wire between the analog input and VDD if you do not have a battery available.

3.2 Declare the buffer where the SAADC sample value will be stored during sampling. Add this line below code from the last point:

static int16_t sample;

Copy

static int16_t sample;

4. We will use a software timer (k_timer) to trigger the sampling.

4.1 Define the sample interval by adding this line close to the top of main.c:

#define BATTERY_SAMPLE_INTERVAL_MS 2000

Copy

#define BATTERY_SAMPLE_INTERVAL_MS 2000

4.2 Define the timer instance that will be used for sampling:

K_TIMER_DEFINE(battery_sample_timer, battery_sample_timer_handler, NULL);

Copy

K_TIMER_DEFINE(battery_sample_timer, battery_sample_timer_handler, NULL);

4.3 Add forward declaration of timer callback handler right before the previous timer definition:

static void battery_sample_timer_handler(struct k_timer * timer);

Copy

static void battery_sample_timer_handler(struct k_timer * timer);

5. Configure the SAADC driver.

5.1 We will reference the ADC defined in the Zephyr devicetree, to make the code more portable. To connect the SAADC interrupt to SAADC interrupt handler, add these lines:

IRQ_CONNECT(DT_IRQN(DT_NODELABEL(adc)),
            DT_IRQ(DT_NODELABEL(adc), priority),
            nrfx_isr, nrfx_saadc_irq_handler, 0);

Copy

IRQ_CONNECT(DT_IRQN(DT_NODELABEL(adc)),
            DT_IRQ(DT_NODELABEL(adc), priority),
            nrfx_isr, nrfx_saadc_irq_handler, 0);

By default, the ADC is enabled in the board DTS file for all DKs supported by this course, but for custom boards you may have to enable it in your DTS or overlay file using the following code snippet:

&adc {
	status = "okay";
};

Copy

&adc {
	status = "okay";
};

Devicetree

5.2 Before using the nrfx SAADC driver, the driver instance must be initialized. We will again refer to the devicetree to get the configured priority of the ADC node and use this for the driver:

int err = nrfx_saadc_init(DT_IRQ(DT_NODELABEL(adc), priority));
if (err != 0) {
  printk("nrfx_saadc_mode_trigger error: %08x", err);
  return;
}

Copy

int err = nrfx_saadc_init(DT_IRQ(DT_NODELABEL(adc), priority));
if (err != 0) {
  printk("nrfx_saadc_mode_trigger error: %08x", err);
  return;
}

5.3 Configure the SAADC channel using the previously defined channel configuration structure. The default configuration uses GAIN=1, which is too high to support supply voltage measurements. We need to change the gain config before configuring the channel.

All other DKs
nRF54L Series DK

channel.channel_config.gain = NRF_SAADC_GAIN1_6;
err = nrfx_saadc_channels_config(&channel, 1);
if (err != 0) {
  printk("nrfx_saadc_channels_config error: %08x", err);
  return;
}

Copy

channel.channel_config.gain = NRF_SAADC_GAIN1_6;
err = nrfx_saadc_channels_config(&channel, 1);
if (err != 0) {
  printk("nrfx_saadc_channels_config error: %08x", err);
  return;
}

The GAIN steps are different for nRF54L15 compared to previous SoCs.

channel.channel_config.gain = NRF_SAADC_GAIN1_4;
err = nrfx_saadc_channels_config(&channel, 1);
if (err != 0) {
  printk("nrfx_saadc_channels_config error: %08x", err);
  return;
}

Copy

channel.channel_config.gain = NRF_SAADC_GAIN1_4;
err = nrfx_saadc_channels_config(&channel, 1);
if (err != 0) {
  printk("nrfx_saadc_channels_config error: %08x", err);
  return;
}

5.4 Configure SAADC driver in simple mode on channel 0. Passing NULL to the last argument will make the driver operate in blocking mode:

err = nrfx_saadc_simple_mode_set(BIT(0),
                                 NRF_SAADC_RESOLUTION_12BIT,
                                 NRF_SAADC_OVERSAMPLE_DISABLED,
                                 NULL);
if (err != 0) {
  printk("nrfx_saadc_simple_mode_set error: %08x", err);
  return;
}

Copy

err = nrfx_saadc_simple_mode_set(BIT(0),
                                 NRF_SAADC_RESOLUTION_12BIT,
                                 NRF_SAADC_OVERSAMPLE_DISABLED,
                                 NULL);
if (err != 0) {
  printk("nrfx_saadc_simple_mode_set error: %08x", err);
  return;
}

Note

The SAADC has a temperature-dependent offset. It is advisable to perform offset calibration before starting the first sample and then at regular intervals or whenever the ambient temperature changes by more than 5 to 10 °C; this recommendation is highly dependent on the specific application.

To start calibration, call nrfx_saadc_offset_calibrate(nrfx_saadc_event_handler_t calib_event_handler)) when the driver is in an idle state (you can call nrfx_saadc_abort() to abort any ongoing or buffered conversions first). It will notify the application in the provided calib_event_handler when calibration is completed. if no handler is provided, the calibration procedure will be blocking. There are some SAADC examples in the SDK where you can see how these APIs are used.

5.5 Set buffer where the sample will be stored. Since the sample interval is quite long and we only sample one channel, a buffer of one sample is sufficient:

err = nrfx_saadc_buffer_set(&sample, 1);
if (err != 0) {
  printk("nrfx_saadc_buffer_set error: %08x", err);
  return;
}

Copy

err = nrfx_saadc_buffer_set(&sample, 1);
if (err != 0) {
  printk("nrfx_saadc_buffer_set error: %08x", err);
  return;
}

6. Start the periodic timer for battery sampling at the interval given by BATTERY_SAMPLE_INTERVAL_MS.

Add the following line to the end of the function configure_saadc():

k_timer_start(&battery_sample_timer, K_NO_WAIT, K_MSEC(BATTERY_SAMPLE_INTERVAL_MS));

Copy

k_timer_start(&battery_sample_timer, K_NO_WAIT, K_MSEC(BATTERY_SAMPLE_INTERVAL_MS));

7. We will now implement the timer callback handler where sampling is triggered and results are printed.

7.1 Add the empty function structure to the main.c file

void battery_sample_timer_handler(struct k_timer *timer)
{

  /* Step 7.2 - Trigger the sampling */

  /* STEP 7.3 - Calculate and print voltage */


}

Copy

void battery_sample_timer_handler(struct k_timer *timer)
{

  /* Step 7.2 - Trigger the sampling */

  /* STEP 7.3 - Calculate and print voltage */


}

7.2 Trigger the sampling. The SAADC driver was previously configured in blocking mode, so the sample will be ready when the function returns:

int err = nrfx_saadc_mode_trigger();
if (err != 0) {
	printk("nrfx_saadc_mode_trigger error: %08x", err);
	return;
}

Copy

int err = nrfx_saadc_mode_trigger();
if (err != 0) {
	printk("nrfx_saadc_mode_trigger error: %08x", err);
	return;
}

7.3 Calculate the battery voltage from the sample and print it on console. The calculation is different for nRF54L15 due to change in the internal reference voltage and GAIN steps.

All other DKs
nRF54L Series DK

For other targets than nRF54L Series, the formula is based on the Digital output formula in nRF52/nRF53/nRF91 SAADC peripheral chapter and converted to millivolts:

int battery_voltage = ((600*6) * sample) / ((1<<12));

printk("SAADC sample: %d\n", sample);
printk("Battery Voltage: %d mV\n", battery_voltage);

Copy

int battery_voltage = ((600*6) * sample) / ((1<<12));

printk("SAADC sample: %d\n", sample);
printk("Battery Voltage: %d mV\n", battery_voltage);

For the nRF54L Series targets, the formula is based on the Digital output formula in nRF54L Series SAADC peripheral chapter and converted to millivolts:

int battery_voltage = ((900*4) * sample) / ((1<<12));

printk("SAADC sample: %d\n", sample);
printk("Battery Voltage: %d mV\n", battery_voltage);

Copy

int battery_voltage = ((900*4) * sample) / ((1<<12));

printk("SAADC sample: %d\n", sample);
printk("Battery Voltage: %d mV\n", battery_voltage);

Testing

8. Build the application and flash it to your board.

9. Connect your analog input to a voltage source, just as you did in exercise 1.

Note

Make sure that the voltage applied to the analog input does not exceed VDD. If you have a battery with a higher voltage level than VDD, you need to use a voltage divider between the battery and the input.

If you want to measure battery voltage directly from VDD, you can replace NRFX_ANALOG_EXTERNAL_AIN0 with NRFX_ANALOG_INTERNAL_VDD.

This could be a dedicated power supply, a PPK2, a battery, or you can simply connect a wire between the analog input (AIN0) and VDD as shown below.

10. Using a serial terminal, you should see the below output:

*** Booting nRF Connect SDK ***
SAADC sample: 3245
Battery Voltage: 2852 mV
SAADC sample: 3237
Battery Voltage: 2845 mV
SAADC sample: 3252
Battery Voltage: 2858 mV

Terminal

The solution for this exercise can be found in the course repository, l6/l6_e2_sol.

v3.1.0 – v3.0.0

In this exercise, we will explore the simple mode of the nrfx SAADC driver to measure a voltage source (e.g., a battery) at a regular interval using a software timer.

Exercise steps

Open the code base of the exercise by navigating to Create a new application in the nRF Connect for VS Code extension, select Copy a sample, and search for Lesson 6 – Exercise 2.

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

1. Enable the SAADC driver.

Let’s enable the SAADC driver by adding the following line in the application configuration file prj.conf.

CONFIG_NRFX_SAADC=y

Copy

CONFIG_NRFX_SAADC=y

Kconfig

2. Include the SAADC header file.

Add SAADC-related header file by including the following line to main.c

#include <nrfx_saadc.h>

Copy

#include <nrfx_saadc.h>

3. Declare objects to be used later in the initialization process.

We need to declare some objects that will be used later in the initialization process.

All other DKs
nRF54L15 DK

#define SAADC_INPUT_PIN NRF_SAADC_INPUT_AIN0
static nrfx_saadc_channel_t channel = NRFX_SAADC_DEFAULT_CHANNEL_SE(SAADC_INPUT_PIN, 0);

Copy

#define SAADC_INPUT_PIN NRF_SAADC_INPUT_AIN0
static nrfx_saadc_channel_t channel = NRFX_SAADC_DEFAULT_CHANNEL_SE(SAADC_INPUT_PIN, 0);

The way of configuring pins for SAADC channels has changed for nRF54L15.

#define NRF_SAADC_INPUT_AIN4 NRF_PIN_PORT_TO_PIN_NUMBER(11U, 1)
#define SAADC_INPUT_PIN NRF_SAADC_INPUT_AIN4
static nrfx_saadc_channel_t channel = NRFX_SAADC_DEFAULT_CHANNEL_SE(SAADC_INPUT_PIN, 0);

Copy

#define NRF_SAADC_INPUT_AIN4 NRF_PIN_PORT_TO_PIN_NUMBER(11U, 1)
#define SAADC_INPUT_PIN NRF_SAADC_INPUT_AIN4
static nrfx_saadc_channel_t channel = NRFX_SAADC_DEFAULT_CHANNEL_SE(SAADC_INPUT_PIN, 0);

We are using AIN4 for nRF54L15 since the GPIO shared with AIN0 by default is used for one of the UARTE instances on the nRF54L15 DK.

3.2 Declare the buffer where the SAADC sample value will be stored during sampling. Add this line below code from the last point:

static int16_t sample;

Copy

static int16_t sample;

4. We will use a software timer (k_timer) to trigger the sampling.

4.1 Define the sample interval by adding this line close to the top of main.c:

#define BATTERY_SAMPLE_INTERVAL_MS 2000

Copy

#define BATTERY_SAMPLE_INTERVAL_MS 2000

4.2 Define the timer instance that will be used for sampling:

K_TIMER_DEFINE(battery_sample_timer, battery_sample_timer_handler, NULL);

Copy

K_TIMER_DEFINE(battery_sample_timer, battery_sample_timer_handler, NULL);

4.3 Add forward declaration of timer callback handler right before the previous timer definition:

static void battery_sample_timer_handler(struct k_timer * timer);

Copy

static void battery_sample_timer_handler(struct k_timer * timer);

5. Configure the SAADC driver.

5.1 We will reference the ADC defined in the Zephyr devicetree, to make the code more portable. To connect the SAADC interrupt to SAADC interrupt handler, add these lines:

IRQ_CONNECT(DT_IRQN(DT_NODELABEL(adc)),
            DT_IRQ(DT_NODELABEL(adc), priority),
            nrfx_isr, nrfx_saadc_irq_handler, 0);

Copy

IRQ_CONNECT(DT_IRQN(DT_NODELABEL(adc)),
            DT_IRQ(DT_NODELABEL(adc), priority),
            nrfx_isr, nrfx_saadc_irq_handler, 0);

&adc {
	status = "okay";
};

Copy

&adc {
	status = "okay";
};

Devicetree

5.2 Before using the nrfx SAADC driver, the driver instance must be initialized. We will again refer to the devicetree to get the configured priority of the ADC node and use this for the driver:

nrfx_err_t err = nrfx_saadc_init(DT_IRQ(DT_NODELABEL(adc), priority));
if (err != NRFX_SUCCESS) {
  printk("nrfx_saadc_mode_trigger error: %08x", err);
  return;
}

Copy

nrfx_err_t err = nrfx_saadc_init(DT_IRQ(DT_NODELABEL(adc), priority));
if (err != NRFX_SUCCESS) {
  printk("nrfx_saadc_mode_trigger error: %08x", err);
  return;
}

All other DKs
nRF54L15 DK

channel.channel_config.gain = NRF_SAADC_GAIN1_6;
err = nrfx_saadc_channels_config(&channel, 1);
if (err != NRFX_SUCCESS) {
  printk("nrfx_saadc_channels_config error: %08x", err);
  return;
}

Copy

channel.channel_config.gain = NRF_SAADC_GAIN1_6;
err = nrfx_saadc_channels_config(&channel, 1);
if (err != NRFX_SUCCESS) {
  printk("nrfx_saadc_channels_config error: %08x", err);
  return;
}

The GAIN steps are different for nRF54L15 compared to previous SoCs.

channel.channel_config.gain = NRF_SAADC_GAIN1_4;
err = nrfx_saadc_channels_config(&channel, 1);
if (err != NRFX_SUCCESS) {
  printk("nrfx_saadc_channels_config error: %08x", err);
  return;
}

Copy

channel.channel_config.gain = NRF_SAADC_GAIN1_4;
err = nrfx_saadc_channels_config(&channel, 1);
if (err != NRFX_SUCCESS) {
  printk("nrfx_saadc_channels_config error: %08x", err);
  return;
}

5.4 Configure SAADC driver in simple mode on channel 0. Passing NULL to the last argument will make the driver operate in blocking mode:

err = nrfx_saadc_simple_mode_set(BIT(0),
                                 NRF_SAADC_RESOLUTION_12BIT,
                                 NRF_SAADC_OVERSAMPLE_DISABLED,
                                 NULL);
if (err != NRFX_SUCCESS) {
  printk("nrfx_saadc_simple_mode_set error: %08x", err);
  return;
}

Copy

err = nrfx_saadc_simple_mode_set(BIT(0),
                                 NRF_SAADC_RESOLUTION_12BIT,
                                 NRF_SAADC_OVERSAMPLE_DISABLED,
                                 NULL);
if (err != NRFX_SUCCESS) {
  printk("nrfx_saadc_simple_mode_set error: %08x", err);
  return;
}

Note

5.5 Set buffer where the sample will be stored. Since the sample interval is quite long and we only sample one channel, a buffer of one sample is sufficient:

err = nrfx_saadc_buffer_set(&sample, 1);
if (err != NRFX_SUCCESS) {
  printk("nrfx_saadc_buffer_set error: %08x", err);
  return;
}

Copy

err = nrfx_saadc_buffer_set(&sample, 1);
if (err != NRFX_SUCCESS) {
  printk("nrfx_saadc_buffer_set error: %08x", err);
  return;
}

6. Start the periodic timer for battery sampling at the interval given by BATTERY_SAMPLE_INTERVAL_MS.

Add the following line to the end of the function configure_saadc():

k_timer_start(&battery_sample_timer, K_NO_WAIT, K_MSEC(BATTERY_SAMPLE_INTERVAL_MS));

Copy

k_timer_start(&battery_sample_timer, K_NO_WAIT, K_MSEC(BATTERY_SAMPLE_INTERVAL_MS));

7. We will now implement the timer callback handler where sampling is triggered and results are printed.

7.1 Add the empty function structure to the main.c file

void battery_sample_timer_handler(struct k_timer *timer)
{

  /* Step 7.2 - Trigger the sampling */

  /* STEP 7.3 - Calculate and print voltage */


}

Copy

void battery_sample_timer_handler(struct k_timer *timer)
{

  /* Step 7.2 - Trigger the sampling */

  /* STEP 7.3 - Calculate and print voltage */


}

7.2 Trigger the sampling. The SAADC driver was previously configured in blocking mode, so the sample will be ready when the function returns:

nrfx_err_t err = nrfx_saadc_mode_trigger();
if (err != NRFX_SUCCESS) {
	printk("nrfx_saadc_mode_trigger error: %08x", err);
	return;
}

Copy

nrfx_err_t err = nrfx_saadc_mode_trigger();
if (err != NRFX_SUCCESS) {
	printk("nrfx_saadc_mode_trigger error: %08x", err);
	return;
}

7.3 Calculate the battery voltage from the sample and print it on console. The calculation is different for nRF54L15 due to change in the internal reference voltage and GAIN steps.

All other DKs
nRF54L15 DK

For other targets than nRF54L15, the formula is based on the Digital output formula in nRF52/nRF53/nRF91 SAADC peripheral chapter and converted to millivolts:

int battery_voltage = ((600*6) * sample) / ((1<<12));

printk("SAADC sample: %d\n", sample);
printk("Battery Voltage: %d mV\n", battery_voltage);

Copy

int battery_voltage = ((600*6) * sample) / ((1<<12));

printk("SAADC sample: %d\n", sample);
printk("Battery Voltage: %d mV\n", battery_voltage);

For the nRF54L15 target, the formula is based on the Digital output formula in nRF54L15 SAADC peripheral chapter and converted to millivolts:

int battery_voltage = ((900*4) * sample) / ((1<<12));

printk("SAADC sample: %d\n", sample);
printk("Battery Voltage: %d mV\n", battery_voltage);

Copy

int battery_voltage = ((900*4) * sample) / ((1<<12));

printk("SAADC sample: %d\n", sample);
printk("Battery Voltage: %d mV\n", battery_voltage);

Testing

8. Build the application and flash it to your board.

9. Connect your analog input to a voltage source, just as you did in exercise 1.

Note

If you want to measure battery voltage directly from VDD, you can replace NRF_SAADC_INPUT_AIN0 with NRF_SAADC_INPUT_VDD.

This could be a dedicated power supply, a PPK2, a battery, or you can simply connect a wire between the analog input (AIN0) and VDD as shown below.

10. Using a serial terminal, you should see the below output:

*** Booting nRF Connect SDK ***
SAADC sample: 3245
Battery Voltage: 2852 mV
SAADC sample: 3237
Battery Voltage: 2845 mV
SAADC sample: 3252
Battery Voltage: 2858 mV

Terminal

The solution for this exercise can be found in the course repository, l6/l6_e2_sol.

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.

nRF Connect SDK Intermediate

Exercise 2 – Interfacing with ADC using nrfx driver and software timers

Exercise steps

Note

Note

Exercise steps

Note

Note

Switch language?

Change summary

What's new in the latest version

General updates

Bluetooth LE updates

MCUboot & Partition Manager