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 6 – FOTA over LTE-M/NB-IoT

For documentation on nRF91 Series FOTA updates, see the page Configuring and building with nRF91 Series: FOTA.

There are multiple ways to create applications for the nRF91 Series. Two of the main choices a developer must make are:

  • Which cloud provider to use, for example nRF Cloud, AWS, or Azure.
  • Which communication protocol to use, for example MQTT, CoAP, or HTTP.

Important

This exercise assumes that you have already completed Cellular IoT Fundamentals, Lesson 1 – Exercise 1 to provision the nRF91 Series DK to nRF Cloud.

With this in mind, in this exercise we will learn how to update the firmware of an nRF9160 DK or nRF91x1 DK over a cellular connection (LTE-M or NB-IoT). MCUboot and the swapping of firmware is the same here as we learned in the theory part of this section, so all we need to do is move the new firmware to the mcuboot_secondary slot in the flash memory of the nRF91 Series.

We will split the “travel” of the firmware package into two steps:

  • Download firmware into the mcuboot_secondary slot
  • Hosting the firmware in the cloud

Download firmware into the mcuboot_secondary slot

The nRF Connect SDK FOTA Download library is used to download firmware from a URL. If this update is an MCUboot update, it will automatically be downloaded into the mcuboot_secondary slot. After the download is complete, it is automatically tagged as “test” by the library.

The FOTA Download library may be called directly from our application. However, several of the cloud libraries in the nRF Connect SDK has FOTA support built-in where FOTA Download is called automatically from the cloud library. See specific documentation for each cloud library for how they handle FOTA.

Hosting the firmware in the cloud

To download the firmware to the device, we must have uploaded the firmware somewhere. As with the previous exercises, we will use build/<project>/zephyr/<project>.signed.bin as our new firmware image. The FOTA Download library does not really care where this file is, as long as it has an URL and a filename. Because of this, it is possible to upload <project>.signed.bin to a public page and download it directly from this page, as done by our HTTP Update sample.

However, this solution does not scale very well. With multiple different devices connected to the internet, we want a way to get an overview over our devices and a way to push updates to subsets of the devices. The different cloud providers have FOTA solutions which give us such functionality. Because of this, we will learn how to use the Device Management in nRF Cloud to host our FOTA firmware updates in this exercise. Other cloud providers will have similar functionality.

Exercise steps

 Create a new application in the nRF Connect for VS Code extension, select Copy a sample, and search for nRF Cloud MQTT FOTA

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

Build the sample for nrf9160dk_nrf9160_ns, nrf9161dk_nrf9161_ns or nrf9151dk_nrf9151_ns and flash it to the board. Observe that the sample successfully connects to nRF Cloud from the logs.

Important

The nRF9160 SoC supports IMEI-based client ID when connecting to the nRF Cloud. By default the nRF Cloud FOTA example uses internal UUID.

When using nRF9160DK board  set CONFIG_NRF_CLOUD_CLIENT_ID_SRC_INTERNAL_UUID=n in the prj.conf.

You should see the following:

*** 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: 0x10000
*** Booting My Application v1.0.0-f921fb9635f4 ***
*** Using nRF Connect SDK ***
*** Using Zephyr OS ***
[00:00:00.266,357] <inf> cloud_connection: Enabling connectivity...
[00:00:00.607,543] <inf> cloud_connection: Setting up nRF Cloud library...
[00:00:00.616,363] <inf> nrf_cloud_info: Device ID: nrf-3...........
[00:00:00.623,870] <inf> nrf_cloud_info: IMEI:      35........
[00:00:00.630,981] <inf> nrf_cloud_info: Modem FW:  mfw_nrf91x1_2.0.2
[00:00:00.637,878] <inf> nrf_cloud_info: Protocol:          MQTT
[00:00:00.644,409] <inf> nrf_cloud_info: Download protocol: HTTPS
[00:00:00.651,000] <inf> nrf_cloud_info: Sec tag:           16842753
[00:00:00.657,867] <inf> nrf_cloud_info: Host name:         mqtt.nrfcloud.com
[00:00:00.665,557] <inf> cloud_connection: Waiting for network ready...
+CGEV: EXCE STATUS 0
+CEREG: 2,"CEAF","037CD90C",7
%MDMEV: PRACH CE-LEVEL 0
+CSCON: 1
+CGEV: ME PDN ACT 0,0
+CNEC_ESM: 50,0
%MDMEV: SEARCH STATUS 2
+CEREG: 5,"CEAF","037CD90C",7,,,"11100000","11100000"
%XTIME: ,"52208121125140","00"
%XTIME: ,"52208121126140",
[00:00:06.843,780] <inf> cloud_connection: Network connectivity gained!
[00:00:07.850,982] <inf> cloud_connection: Network is ready
[00:00:07.856,994] <inf> cloud_connection: Connecting to nRF Cloud
[00:00:07.863,708] <inf> cloud_connection: Device ID: nrf-35......
[00:00:07.871,032] <dbg> cloud_connection: cloud_event_handler: NRF_CLOUD_EVT_TRANSPORT_CONNECTING
[00:00:09.891,601] <dbg> cloud_connection: cloud_event_handler: NRF_CLOUD_EVT_TRANSPORT_CONNECTED
[00:00:09.900,939] <inf> cloud_connection: Connected to nRF Cloud
[00:00:09.907,592] <dbg> cloud_connection: cloud_connection_thread_fn: Awaiting disconnection from nRF Cloud
Hello World! nrf9151dk
Terminal

3. Change application version.

Change the application version so we can confirm that the firmware has been updated. Build the application again, but do not flash it to the DK.

3.1 Modify VERSION file to version 1.10

Copy
#Step 4.1 Change application version 
VERSION_MAJOR = 1
VERSION_MINOR = 1
PATCHLEVEL = 0
VERSION_TWEAK = 0
EXTRAVERSION =
C

4. Setup FOTA in nRF Cloud.

For this next step, we will set up the FOTA in nRF Cloud. Documentation on how to do this can be found at nRF Cloud docs: Updating device firmware.

4.1 First, we will have to add the nRF91 Series device to a group in the nRF Cloud. Since the device has already been provisioned to nRF Cloud, we should see it in the Devices tab:

4.2 Next up, we will add a new firmware bundle containing the firmware we will upload. Go to Device Management → Firmware Updates and select the “Add Bundle” button under Bundles:

In the following Create Update Bundle window, upload build/dfu_application.zip. This file is an automatically created zip containing DFU files such as nrf_cloud_mqtt_fota.signed.bin. nRF Cloud will have logic unzip dfu_application.zip, read the manifest and then FOTA the correct files to the nRF91.

Then fill out the rest of the fields. We can choose what we want for the name and version, but it is a good idea to make something that makes sense and that we can increment later.

4.3 We will now create an update. For this, we use the “Create FOTA Update” button at the top of the Firmware Updates page:

In the Create Update window, we fill in a name and description for the update. Then we choose the bundle that we just created and finally choose our DK:

Leave “Deploy now” unchecked and press “Create Update”.

4.4 Connect the nRF Terminal to the nRF91 device so we can watch the logs when the update starts.

4.5 After step 4.3, we get to a page for the Update:

Next up, we can deploy the update by pressing the “large “Deploy Update” button. Then we wait a little, and we should be able to see all device queued for the update:

When the update has been deployed, nRF Cloud will publish an MQTT message to the device to tell it to start the download. Then all we have to do is wait, and the update should happen automatically. You can see that the update happens both in the status bar at nRF Cloud and in the logs from the nRF91 device.

4.6 When the update is finished, we can see the following logs:

[00:01:11.930,450] <inf> download_client: Downloaded 231200/236991 bytes (97%)
[00:01:12.343,994] <inf> download_client: Downloaded 232900/236991 bytes (98%)
[00:01:12.673,156] <inf> download_client: Downloaded 234600/236991 bytes (98%)
[00:01:13.074,157] <inf> download_client: Downloaded 236300/236991 bytes (99%)
[00:01:13.341,613] <inf> download_client: Downloaded 236991/236991 bytes (100%)
[00:01:13.348,907] <inf> download_client: Download complete
[00:01:13.441,650] <inf> dfu_target_mcuboot: MCUBoot image-0 upgrade scheduled. Reset device to apply
[00:01:13.443,542] <inf> nrf_cloud_fota: Download complete
[00:01:13.511,993] <dbg> cloud_connection: cloud_event_handler: NRF_CLOUD_EVT_FOTA_DONE, FOTA type: Application
[00:01:13.729,125] <dbg> cloud_connection: cloud_event_handler: NRF_CLOUD_EVT_FOTA_DONE, FOTA type: Application
Terminal

As we can see, we must restart the device to apply the update. Reset the nRF91 Series DK and observe the swap. The nRF Cloud library will then see that it has a pending update again, but when it realizes that its update is already completed, it will confirm the update so as not to swap back on its next reboot.

[00:00:21.164,031] <inf> nrf_cloud_fota: Job 50371521-dbe1-40b0-9e1c-ffffffffffff already completed... skipping
Terminal

With this, we have successfully updated the nRF91 Series DK application with FOTA. We can confirm that by selecting our device in “Device Management -> Devices” page.

5. Update the modem firmware over FOTA.

5.1 First, we check the current modem firmware version. To do this in nRF Cloud, we select the device from the Devices menu:

Then we can find the modem version information under Device Info:

5.2 If the device needs updating, add a modem firmware update and deploy it, as we did in step 4.3.

This time, we won’t upload the dfu file. Please choose the MFW delta update file that fits your current modem firmware version and the target version you want to upgrade to.

5.3 As with the application update, an MQTT message should be received by the nRF91 Series device, automatically starting the modem delta update.

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.