|
| 1 | +--- |
| 2 | +title: Introducing nRF Connect SDK |
| 3 | +date: 2025-08-22 |
| 4 | +authors: |
| 5 | + - makerdiary |
| 6 | +cover: cover.png |
| 7 | +description: > |
| 8 | + nRF Connect SDK is a scalable and unified software development kit for building low-power wireless applications based on the Nordic Semiconductor wireless devices. |
| 9 | +--- |
| 10 | + |
| 11 | +{ loading=lazy } |
| 12 | + |
| 13 | +# Introducing nRF Connect SDK |
| 14 | + |
| 15 | +## Overview |
| 16 | + |
| 17 | +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. |
| 18 | + |
| 19 | +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). |
| 20 | + |
| 21 | +The following figure illustrates the architecture of the nRF Connect SDK, where Zephyr RTOS and third-party components (Ex: MCUBoot, Trusted Firmware-M) are shown in dark blue: |
| 22 | + |
| 23 | +{ loading=lazy } |
| 24 | + |
| 25 | +## About Zephyr RTOS |
| 26 | + |
| 27 | +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. |
| 28 | + |
| 29 | +[Zephyr RTOS](https://www.zephyrproject.org/){ .md-button .md-button--primary } |
| 30 | + |
| 31 | +## How nRF Connect SDK code is organized |
| 32 | + |
| 33 | +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. |
| 34 | + |
| 35 | +Internally, the nRF Connect SDK code is organized into four __`main`__ repositories: |
| 36 | + |
| 37 | +- `nrf` – Applications, samples, connectivity protocols (Nordic) |
| 38 | +- `nrfxlib` – Common libraries and stacks (Nordic) |
| 39 | +- `Zephyr` – RTOS & Board configurations (open source) |
| 40 | +- `MCUBoot` – Secure Bootloader (open source) |
| 41 | + |
| 42 | +In addition to the four main repositories, there are also other repositories like the TrustedFirmware-M repository and the Matter repository. |
| 43 | + |
| 44 | +## Tools and configuration |
| 45 | + |
| 46 | +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. |
| 47 | + |
| 48 | +{ loading=lazy } |
| 49 | + |
| 50 | +Kconfig generates definitions that configure the whole system, for example which wireless protocol or which libraries to include in your application. Devicetree describes the hardware. CMake then uses the information from Kconfig and the devicetree to generate build files, which Ninja will use to build the program. The GCC compiler system is used to create the executables. |
| 51 | + |
| 52 | +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. |
| 53 | + |
| 54 | +{ loading=lazy } |
| 55 | + |
| 56 | +## Next steps |
| 57 | + |
| 58 | +Now that we have an understanding of the content and structure of the nRF Connect SDK, let’s move to the developer guides which will step you through the basics of nRF Connect SDK development and show you how to implement typical use cases with Nordic Semiconductor libraries and drivers on the nRF54L15 Connect Kit. |
| 59 | + |
| 60 | +[nRF Connect SDK Developer Guides](https://wiki.makerdiary.com/nrf54l15-connectkit/guides/ncs/){ .md-button .md-button--primary } |
0 commit comments