nRF Connect SDK Intermediate

Changing the version will not affect your certificate
Lesson 1 – Zephyr RTOS: Beyond the basics
7 Topics | 1 Quiz
Boot-up sequence & execution context
Thread life cycle
Scheduler in-depth
Data passing
Exercise 1 – Exploring threads and ISRs
Exercise 2 – Kernel options
Summary
Lesson 1 quiz
Lesson 2 – Debugging and troubleshooting
8 Topics | 1 Quiz
Debugging in nRF Connect for VS Code
Build errors and fatal errors
Troubleshooting the devicetree
Physical debugging
Exercise 1 – Advanced debugging in nRF Connect for VS Code
Exercise 2 – Debugging with core dump and addr2line
Exercise 3 – Debugging the devicetree
Exercise 4 – Remote debugging with Memfault
Lesson 2 quiz
Lesson 3 – Adding custom board support
5 Topics | 1 Quiz
Board definition
Creating board files
Board files for multi-core hardware & TF-M
Exercise 1 – Custom board for single-core SoC
Exercise 2 – Custom board for a multi-core & TF-M capable SoC/SiP
Lesson 3 quiz
Lesson 4 – Pulse Width Modulation (PWM)
4 Topics | 1 Quiz
Pulse Width Modulation (PWM)
Zephyr PWM API
Exercise 1 – Controlling an LED with PWM
Exercise 2 – Using PWM to control a servo motor
Lesson 4 quiz
Lesson 5 – Serial Peripheral Interface (SPI)
3 Topics | 1 Quiz
Serial Peripheral Interface (SPI)
Zephyr SPI API
Exercise 1 – Interfacing with a sensor over SPI
Lesson 5 quiz
Lesson 6 – Analog-to-digital converter (ADC)
5 Topics | 1 Quiz
ADC peripheral on Nordic devices
Choosing between Zephyr ADC API and nrfx SAADC driver API
Exercise 1 – Interfacing with ADC using Zephyr API
Exercise 2 – Interfacing with ADC using nrfx driver and software timers
Exercise 3 – Interfacing with ADC using nrfx drivers and TIMER/PPI
Lesson 6 quiz
Lesson 7 – Device driver development
6 Topics | 1 Quiz
Device driver model
Device driver implementation
Device power management
Exercise 1 – Creating a custom driver using the sensor API
Exercise 2 – Adding power management to a custom driver
Exercise 3 – Creating a custom driver with a custom API
Lesson 7 quiz
Lesson 8 – Sysbuild
5 Topics | 1 Quiz
Sysbuild explained
Sysbuild configuration
Sysbuild – Partition Manager
Exercise 1 – Configuring extra image
Exercise 2 – Adding custom image
Lesson 8 quiz
Lesson 9 – Bootloaders and DFU/FOTA
12 Topics | 1 Quiz
Bootloader basics
Application verification
Device Firmware Update (DFU) essentials
MCUboot, and relevant libraries
DFU for the nRF5340 SoC
Exercise 1 – DFU over UART
Exercise 2 – DFU with custom keys
Exercise 3 – DFU with external flash
Exercise 4 – DFU over USB
Exercise 5 – FOTA over Bluetooth LE
Exercise 6 – FOTA over LTE-M/NB-IoT
Exercise 7 – FOTA over Wi-Fi
Lesson 9 quiz
Get your Certificate!
Feedback
Feedback

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

Exercise 1 – Configuring extra image

In this exercise, you learn how to enable and configure one of the default images provided by the nRF Connect SDK. You also learn how to verify configurations for the various images within an nRF Connect SDK project and for sysbuild itself.

This exercise uses MCUboot because it works for most SoCs and SiPs. However, the procedure is the same for any other default image, so you can try it with a different image.

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 8 – Exercise 1.

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

1. Build and flash the exercise base to your board.

Build the exercise for whichever board you are using and flash it to the device.

Verify that you get logs that look similar to this:

*** Booting nRF Connect SDK ***
*** Using Zephyr OS ***
Hello from DevAcademy Intermediate, Lesson 8, Exercise 1
Terminal

If you look at the APPLICATIONS view in nRF Connect for VS Code, you should notice that there is only one image under the build folder: the application image.

The application root directory name for this exercise is l8_e1. Therefore, the image name is also l8_e1.

2. Add an extra image (MCUboot) using Sysbuild.

The nRF Connect SDK provides the MCUboot extra image source code and default sysbuild configuration. The MCUboot source code is located in <install_path>\<SDK version>\bootloader\mcuboot. The sysbuild configurations for the MCUboot image and other images are available in <install_path>\<SDK version>\nrf\sysbuild.

2.1 Create sysbuild.conf in the exercise project folder and insert the following comment:

Copy
# STEP 2.1 - Add MCUboot
Kconfig

2.2 Enable MCUboot in the project by enabling it in sysbuild.conf:

Copy
# STEP 2.1 - Add MCUboot
SB_CONFIG_BOOTLOADER_MCUBOOT=y
Kconfig

Important

On the nRF7002 DK only, ensure that the SPI NOR driver is disabled by default by adding the following lines in sysbuild/mcuboot.conf

CONFIG_SPI=n

CONFIG_SPI_NOR=n

3. Build and flash the project again.

Make sure to do a Pristine build.

Observe the terminal output from the application.

You should be seeing log output from MCUboot and then from the project after that:

*** Booting MCUboot ***
*** Using nRF Connect SDK ***
*** Using Zephyr OS ***
I: Starting bootloader
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Image index: 0, Swap type: none
I: Bootloader chainload address offset: 0xc000
*** Booting nRF Connect SDK v2.9.0-7787b2649840 ***
*** Using Zephyr OS v3.7.99-1f8f3dc29142 ***
Hello from DevAcademy Intermediate, Lesson 8, Exercise 1
Terminal

In the APPLICATIONS view of nRF Connect for VS Code, you should now see two images listed under the build folder: the application image and the MCUboot image. Thanks to Sysbuild, both images are managed within a single project. It’s important to note that both images run sequentially on the same CPU core, which is why the same board target appears.

4. Configure the MCUboot image.

Next, configure the MCUboot image. First, create the sysbuild/ folder in the exercise project. Then create a file named mcuboot.conf inside the sysbuild/ folder. The project should now look like this:

Add the following comment to mcuboot.conf:

Copy
# STEP 4.1 - Disable anything on UART in MCUboot
Kconfig

4.1 Disable the serial in MCUboot so you no longer get logs over UART.

Copy
# STEP 4.1 - Disable anything on UART in MCUboot
CONFIG_SERIAL=n
Kconfig

5. Build and flash the project again.

Make sure to do a Pristine build since the input Kconfig files have changed.

The UART should now only print the application logs.

*** Booting nRF Connect SDK ***
*** Using Zephyr OS ***
Hello from DevAcademy Intermediate, Lesson 8, Exercise 1
Terminal

6. Now learn how to verify configurations for the different images and sysbuild configuration itself. For example, confirm that the CONFIG_SERIAL Kconfig symbol was set correctly for the MCUboot image.

You can check the MCUboot configuration in the generated build/mcuboot/zephyr/.config file.

You can check the application configuration in the generated build/l8_e1/zephyr/.config file.

You can check the sysbuild configuration in the generated build/zephyr/.config file.

Alternatively, use the nRF Kconfig GUI. First, select the active context in nRF Connect for VS Code from the APPLICATIONS view, as shown below for MCUboot:

Notice that the build folder and image name are reflected in the other views in VS Code, as highlighted in red in the screenshot above.

After you select the active context, click nRF Kconfig GUI and search for CONFIG_SERIAL. You should see it as unselected. This confirms that the Kconfig configuration (CONFIG_SERIAL=n) set in mcuboot.conf propagated correctly in the build system and the generated image .config file reflects that.

The same is true for device tree source (DTS) files in build/<image_name>/zephyr/zephyr.dts. These files help you verify that the hardware overlays you set in your project propagated correctly throughout the build.

Make sure to Log in or Register to save your progress

Back
Next

Nordic Developer Academy Privacy Policy

 

1. Introduction 

In this Privacy Policy you will find information on Nordic Semiconductor ASA (“Nordic Semiconductor”) processes your personal data when you use the Nordic Developer Academy.

References to “we” and “us” in this document refers to Nordic Semiconductor.

 

2. Our processing of personal data when you use the Nordic Developer Academy 

2.1 Nordic Developer Academy 

Nordic Semiconductor processes personal data in order to provide you with the features and functionality of the Nordic Developer Academy. Creating a user account is optional, but required if you want to track you progress and view your completed courses and obtained certificates. If you choose to create a user account, we will process the following categories of personal data:

  • Email
  • Name
  • Password (encrypted)
  • Course progression (e.g. which course you have completely or partly completed)
  • Certificate information, which consists of name of completed course and the validity of the certificate
  • Course results

During your use of the Nordic Developer Academy, you may also be asked if you want to provide feedback. If you choose to respond to any such surveys, we will also process the personal data in your responses in that survey.

The legal basis for this processing is GDPR article 6 (1) b. The processing is necessary for Nordic Semiconductor to provide the Nordic Developer Academy under the Terms of Service.

 

2.2 Analytics 

If you consent to analytics, Nordic Semiconductor will use Google Analytics to obtain statistics about how the Nordic Developer Academy is used. This includes collecting information on for example what pages are viewed, the duration of the visit, the way in which the pages are maneuvered, what links are clicked, technical information about your equipment. The information is used to learn how Nordic Developer Academy is used and how the user experience can be further developed.

 

2.2 Newsletter 

You can consent to receive newsletters from Nordic from within the Nordic Developer Academy. How your personal data is processed when you sign up for our newsletters is described in the Nordic Semiconductor Privacy Policy.

 

3. Retention period 

We will store your personal data for as long you use the Nordic Developer Academy. If our systems register that you have not used your account for 36 months, your account will be deleted.

 

4. Additional information 

Additional information on how we process personal data can be found in the Nordic Semiconductor Privacy Policy and Cookie Policy.

‍‍ 

Nordic Developer Academy Terms of Service

 

1. Introduction

‍These terms and conditions (“Terms of Use”) apply to the use of the Nordic Developer Academy, provided by Nordic Semiconductor ASA, org. nr. 966 011 726, a public limited liability company registered in Norway (“Nordic Semiconductor”). ‍

Nordic Developer Academy allows the user to take technical courses related to Nordic Semiconductor products, software and services, and obtain a certificate certifying completion of these courses. By completing the registration process for the Nordic Developer Academy, you are agreeing to be bound by these Terms of Use.

These Terms of Use are applicable as long as you have a user account giving you access to Nordic Developer Academy.‍

‍2. Access to and use of Nordic Developer Academy

‍‍Upon acceptance of these Terms of Use you are granted a non-exclusive right of access to, and use of Nordic Developer Academy, as it is provided to you at any time. Nordic Semiconductor provides Nordic Developer Academy to you free of charge, subject to the provisions of these Terms of Use and the Nordic Developer Academy Privacy Policy.

To access select features of Nordic Developer Academy, you need to create a user account. You are solely responsible for the security associated with your user account, including always keeping your login details safe.

You will able to receive an electronic certificate from Nordic Developer Academy upon completion of courses. By issuing you such a certificate, Nordic Semiconductor certifies that you have completed the applicable course, but does not provide any further warrants or endorsements for any particular skills or professional qualifications.

Nordic Semiconductor will continuously develop Nordic Developer Academy with new features and functionality, but reserves the right to remove or alter any existing functions without notice.

‍3. Acceptable use

You undertake that you will use Nordic Developer Academy in accordance with applicable law and regulations, and in accordance with these Terms of Use.‍ You must not modify, adapt, or hack Nordic Developer Academy or modify another website so as to falsely imply that it is associated with Nordic Developer Academy, Nordic Semiconductor, or any other Nordic Semiconductor product, software or service.

You agree not to reproduce, duplicate, copy, sell, resell or in any other way exploit any portion of Nordic Developer Academy, use of Nordic Developer Academy, or access to Nordic Developer Academy without the express written permission by Nordic Semiconductor. You must not upload, post, host, or transmit unsolicited email, SMS, or \”spam\” messages.

You are responsible for ensuring that the information you post and the content you share does not;

  • contain false, misleading or otherwise erroneous information
  • infringe someone else’s copyrights or other intellectual property rights
  • contain sensitive personal data or
  • contain information that might be received as offensive or insulting.
  • Such information may be removed without prior notice.

‍Nordic Semiconductor reserves the right to at any time determine whether a use of Nordic Developer Academy is in violation of its requirements for acceptable use.

Violation of the at any time applicable requirements for acceptable use may result in termination of your account. We will take reasonable steps to notify you and state the reason for termination in such cases.

‍4. Routines for planned maintenance

‍Certain types of maintenance may imply a stop or reduction in availability of Nordic Developer Academy. Nordic Semiconductor does not warrant any level of service availability but will provide its best effort to limit the impact of any planned maintenance on the availability of Nordic Developer Academy.

5. Intellectual property rights

‍Nordic Semiconductor retains all rights to all elements of Nordic Developer Academy. This includes, but is not limited to, the concept, design, trademarks, know-how, trade secrets, copyrights and all other intellectual property rights.

Nordic Semiconductor receives all rights to all content uploaded or created in Nordic Developer Academy. You do not receive any license or usage rights to Nordic Developer Academy beyond what is explicitly stated in this Agreement.

‍6. Liability and damages

‍Nothing within these Terms of Use is intended to limit your statutory data privacy rights as a data subject, as described in the Nordic Developer Academy Privacy Policy. ‍You acknowledge that errors might occur from time to time and waive any right to claim for compensation as a result of errors in Nordic Developer Academy. When an error occurs, you shall notify Nordic Semiconductor of the error and provide a description of the error situation.

You agree to indemnify Nordic Semiconductor for any loss, including indirect loss, arising out of or in connection with your use of Nordic Developer Academy or violations of these Terms of Use. ‍Nordic Semiconductor shall not be held liable for, and does not warrant that (i) Nordic Developer Academy will meet your specific requirements, (ii) Nordic Developer Academy will be uninterrupted, timely, secure, or error-free, (iii) the results that may be obtained from the use of Nordic Developer Academy will be accurate or reliable, (iv) the quality of any products, services, information, or other material purchased or obtained by you through Nordic Developer Academy will meet your expectations, or that (v) any errors in Nordic Developer Academy will be corrected.

You accept that this is a service provided to you without any payment and hence you accept that Nordic Semiconductor will not be held responsible, or liable, for any breaches of these Terms of Use or any loss connected to your use of Nordic Developer Academy. Unless otherwise follows from mandatory law, Nordic Semiconductor will not accept any such responsibility or liability.

‍7. Change of terms

‍Nordic Semiconductor may update and change the Terms of Use from time to time. Nordic Semiconductor will seek to notify you about significant changes before such changes come into force and give you a possibility to evaluate the effects of proposed changes. Continued use of Nordic Developer Academy after any such changes shall constitute your acceptance of such changes. You can review the current version of the Terms of Use at any time at https://academy.nordicsemi.com/terms-of-service/

‍8. Transfer of rights

‍Nordic Semiconductor is entitled to transfer its rights and obligation pursuant to these Terms of Use to a third party as part of a merger or acquisition process, or as a result of other organizational changes.

‍9. Third Party Services

‍‍To the extent Nordic Developer Academy facilitates access to services provided by a third party, you agree to comply with the terms governing such third party services. Nordic Semiconductor shall not be held liable for any errors, omissions, inaccuracies, etc. related to such third party services.

‍10. Dispute resolution

‍‍The Terms of Use and any other legally binding agreement between yourself and Nordic Semiconductor shall be subject to Norwegian law and Norwegian courts’ exclusive jurisdiction.

 

Switch language?

Progress is tracked separately for each language. Switching will continue from your progress in that language or start fresh if you haven't begun.

Your current progress is saved, and you can switch back anytime.

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

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

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

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

Back to Log in

Insert/edit link

Enter the destination URL

Or link to existing content

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

      Change summary

      What's new in the latest version

      General updates

      General updates

      •Support for nRF54LS05 DK (Available through the early access sampling program)
      •Support for the nRF54LM20B with Axon NPU for Edge AI applications
      Bluetooth LE updates

      Bluetooth LE updates

      •Quality of Service module is now production-ready.
      •New experimental features for RF testing (Direct Test Mode) and low-latency packet handling (LE Flushable ACL).
      MCUboot & Partition Manager

      MCUboot & Partition Manager

      •Single-Slot DFU and RAM Load mode are both promoted to fully supported
      •Partition Manager is officially deprecated in favor of Zephyr's devicetree-based partitioning.