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.

nRF54L development options

In developing firmware for the nRF54L Series, the nRF Connect SDK offers two distinct approaches:

  1. RTOS-based (Zephyr) firmware development.
  2. Bare Metal firmware development.

With the RTOS-based approach, you gain comprehensive support for the latest Bluetooth LE features along with other protocols like Matter, Thread, Zigbee, NFC, and proprietary 2.4GHz technologies, rich middleware, libraries, and driver support. On the other hand, the Bare Metal option only supports Bluetooth LE, NFC and comes with certain limitations. You should select the development path that best aligns with the specific requirements of your application.

FeatureRTOS-basedBare Metal
Supported ProtocolsBluetooth LE,
Bluetooth Mesh,
Thread, Zigbee, Matter,
Google Find Hub, Apple Find My, Amazon Sidewalk,
Proprietary 2.4 GHz Protocols,
NFC
Bluetooth LE and NFC only
Bluetooth LE SupportMulti-role support (Central & Peripheral)
Coded PHY
Extended Advertising
Periodic Advertising with Responses (PAwR)
Channel Sounding
Direction Finding
LE Audio
Shorter Connection Interval (SCI)
Multi-role support (Central & Peripheral) only
Supported hardwarenRF54L Series, as well as all other Nordic SoCs (nRF52, nRF53, nRF91, nRF70)Only for the nRF54L Series
Extensive middleware and librariesYesLimited to Bluetooth LE (Peripheral&Central) and NFC
Samples availableAn extensive set of samples and full-fledged applicationsSelected samples
Development EnvironmentnRF Connect for VS Code or Command line interface (CLI)nRF Connect for VS Code or Command line interface (CLI)
Single-bank DFUYes (In v3.2.0 and above)Yes
USB supportYes (for nRF54LM20A|nRF54LM20B)No
Driver supportExtensive driver support for components like sensors, etc..
In addition to low-level drivers (nrfx)
Only low-level drivers (nrfx) for the hardware peripherals

nRF Connect SDK

The nRF Connect SDK is a scalable and unified software development kit designed for building low-power wireless applications with Nordic Semiconductor’s 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, including Bluetooth Low Energy, Bluetooth mesh, Wi-Fi, Matter, Thread/Zigbee, 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, machine learning frameworks, and a bootloader (MCUboot).

Zephyr RTOS is an open-source real-time operating system designed for connected, resource-constrained embedded devices. It features a scheduler that guarantees predictable and deterministic execution patterns while abstracting 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, allowing for scalable configurations that range from minimal setups for memory-constrained devices (as little as 8 kilobytes for simple applications like LED blinking) to powerful, feature-rich setups for high-processing power devices requiring multiple megabytes of memory.

The nRF Connect SDK provides all core components, including the Zephyr RTOS, drivers, libraries (including DFU), bootloader, wireless protocol stacks, and samples needed for evaluation and development on the nRF54L Series. Additionally, the SDK offers two distinct firmware development pathways: RTOS-based and Bare Metal.

1. RTOS-based development

This pathway is the standard, default option that features a comprehensive Bluetooth LE stack, extensive libraries and middleware, and support for multiprotocol wireless connectivity. It is the recommended route for harnessing the full capabilities of the nRF54L Series.

Choosing this path is essential if your product requires access to the latest Bluetooth LE features, such as Periodic Advertising with Responses, Channel Sounding, LE Audio, Direction Finding, Shorter Connection Interval, and others.

It is also the appropriate choice if your project demands support for multiple protocols or integration with ecosystems like Google Find My, Apple Find My, and Amazon Sidewalk.

By following this option, you will leverage the full power of the nRF Connect SDK and Zephyr, gaining access to a rich array of middleware, libraries, and sensor drivers, thus maximizing the potential of your development efforts.

2. Bare Metal development (Bluetooth LE only)

The nRF Connect SDK also offers a Bare Metal configuration for the nRF54L Series for simple Bluetooth LE applications that do not benefit from an RTOS or advanced features. This option comes with two options of pre-compiled Bluetooth LE stack (SoftDevice):

  • S115 – Support for peripheral role only.
  • S145 – Support for both peripheral and central role, as well as more connections.

Currently supported features:

  • Peripheral role only (S115), or peripheral and central roles (S145).
  • Uses the same API as the latest nRF5 SDK SoftDevice (v17), including Timeslot API, Flash API, GATT and GAP APIs
  • Supports 1M and 2M PHY, ATT and SM, LE Secure connections, GATT client and server, custom UUID, Bluetooth LE RSSI QoS, configurable ATT MTU, long ATT MTU, and configurable attribute table size.
  • Includes Single-bank Device Firmware Upgrade (DFU)

The Bare Metal option has the following limitations:

  • It does not support Coded PHY, Extended Advertising, or advanced features such as Channel Sounding, LE Audio, SCI, and Bluetooth Mesh.

This option is ideal for projects requiring a simple Bluetooth LE application without the need for advanced features.

The architecture and APIs for the Bare Metal configuration are very similar to those of the older nRF5 SDK (using SoftDevice S113 and S140), including the use of low-level nrfx drivers directly, which facilitates an easy migration from an existing codebase on the nRF52 Series.

Both Bare Metal and Zephyr RTOS-based development are supported within the same SDK and VS Code development environment. This dual support allows you to choose the configuration that best fits your application needs and provides an easy pathway to upgrade to the full SDK feature set through Zephyr RTOS-based application development later.

Additionally, the Bare Metal option includes a single-bank Device Firmware Update (DFU) solution, optimizing Non-Volatile Memory usage for applications.

How to get started

RTOS-based development

To start development with RTOS-based firmware in nRF Connect SDK, we recommend following the Nordic DevAcademy learning path.

To begin mastering the nRF Connect SDK, start with the nRF Connect SDK Fundamentals course. This introductory course guides you through the installation of the nRF Connect SDK, and the processes of building and flashing an application. You’ll learn how to interact with GPIOs, understand the structure of an application, and work with logging, UART, and I2C. The course also covers essential aspects of the Zephyr RTOS, including multithreaded applications and thread synchronization.

For those focusing on protocol-specific development, we offer the Bluetooth Low Energy Fundamentals course. This is ideal if you’re developing a Bluetooth LE application. If not, you can skip this section.

Once completed, progress to the nRF Connect SDK Intermediate course to delve into more advanced topics. This course enhances your skills in debugging applications and adding support for custom boards. You’ll explore how to interact with PWM, SPI, and ADC peripherals, develop custom drivers, secure Device Firmware Updates over various transports, and deepen your understanding of RTOS-based development, including thread management.

Bare Metal development

To start developing with the Bare Metal environment, refer to the nRF Connect SDK Bare Metal documentation and read more about it in the A technical dive into the nRF Connect SDK Bare Metal option blog post.

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.

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.