Feedback
Feedback

If you are having issues with the exercises, please create a ticket on DevZone: devzone.nordicsemi.com
Click or drag files to this area to upload. You can upload up to 2 files.

nRF Connect SDK structure and content

Navigation

When progressing through the lessons, make sure to complete all the topics, before taking a quiz. The quiz is considered to be the last step in lesson completion. If the lesson is completed in a different order, make sure to re-take the quiz to mark the lesson as completed.

nRF Connect SDK is a scalable and unified software development kit for building low-power wireless applications based on the Nordic Semiconductor nRF54, nRF53, nRF52, nRF70, or nRF91 Series wireless devices. It offers an extensible framework for building size-optimized software for memory-constrained devices as well as powerful and complex software for more advanced devices and applications.

It integrates the Zephyr Real-Time Operating System (RTOS) and a wide range of complete applications, samples, and protocol stacks such as Bluetooth Low Energy, Bluetooth mesh, Wi-Fi, Matter, Thread/Zigbee and LTE-M/NB-IoT/GPS, TCP/IP. It also includes middleware such as CoAP, MQTT, LwM2M, various libraries, hardware drivers, Trusted Firmware-M for security, and a secure bootloader (MCUBoot).

Architecture of the nRF Connect SDK

Zephyr RTOS and third-party components (Ex: MCUBoot, Trusted Firmware-M) are shown in dark blue in the above diagram.

Zephyr RTOS is an open-source real-time operating system for connected and resource-constrained embedded devices. It includes a scheduler that ensures predictable/deterministic execution patterns and abstracts out the timing requirements. It also comes with a rich set of fundamental libraries and middleware that simplifies development and helps reduce a product’s time to market. Zephyr RTOS is highly configurable and enables scalable configurations from very small configurations for memory-constrained devices (minimum 8 kilobytes, for example, simple LED blinking application) to powerful, feature-rich, high-processing power devices (multiple MBs of memory) with large memory configurations.

The nRF Connect SDK offers a single code base for all of Nordic’s devices and software components. It simplifies porting modules, libraries, and drivers from one application to another, thus reducing development time. By enabling developers to pick and choose the essential software components for their application, high memory efficiency is guaranteed. The nRF Connect SDK is publicly hosted on GitHub.

Internally, the nRF Connect SDK code is organized into four main repositories:

  • nrf – Applications, samples, connectivity protocols (Nordic)
  • nrfxlib – Common libraries and stacks (Nordic)
  • Zephyr – RTOS & Board configurations (open source)
  • MCUBoot – Secure Bootloader (open source)

In addition to the four main repositories, there are also other repositories like the TrustedFirmware-M repository and the Matter repository.

The figure below visualizes the toolchain in the nRF Connect SDK, which is based on the Zephyr toolchain. You can see a set of different tools, each playing a role in the creation of an application, from configuring the system to building it.

nRF Connect SDK tools and configuration methods

Kconfig (covered in Lesson 3) generates definitions that configure the whole system, for example, which wireless protocol or which libraries to include in your application. Devicetree (covered in Lesson 2) describes the hardware. CMake then uses the information from Kconfig and the devicetree to generate build files, which Ninja (comparable to make) will use to build the program. The GCC compiler system is used to create the executables.

This high decoupling of the source code (*.c) and the configuration system through Kconfig (*.conf) and the hardware description system through devicetree (*.dts) makes it easy to use the same application source code on different hardware and with different configurations with minimal changes. This has a huge impact on the ease of portability and maintainability.

Build process for nRF Connect SDK

Now that we have an understanding of the content and structure of the nRF Connect SDK, let’s move to the hands-on part of this lesson where we install the nRF Connect SDK through some high-level tools that simplify the process of obtaining the repositories and setting up the needed toolchains.

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.