MPSL timeslot

This sample demonstrates how to use Multiprotocol Service Layer and basic MPSL Timeslot functionality.

Requirements

The sample supports any one of the following development kits:

Hardware platforms

PCA

Board name

Board target

nRF54L15 PDK

PCA10156

nrf54l15pdk

nrf54l15pdk/nrf54l15/cpuapp

nRF54H20 DK

PCA10175

nrf54h20dk

nrf54h20dk/nrf54h20/cpurad

nRF5340 DK

PCA10095

nrf5340dk

nrf5340dk/nrf5340/cpunet

nRF52 DK

PCA10040

nrf52dk

nrf52dk/nrf52832

nRF52840 DK

PCA10056

nrf52840dk

nrf52840dk/nrf52840

Note

For the nRF5340 DK, this sample is only supported on the network core (nrf5340dk_nrf5340_cpunet), and the nRF5340: Empty firmware for application core sample must be programmed to the application core. For the nRF54H20 DK, this sample is only supported on the radio core (nrf54h20dk_nrf4h20_cpurad).

Overview

The sample opens a timeslot session and starts requesting timeslots when a key is pressed in the terminal.

  • If a is pressed, the callback for the first timeslot requests a new timeslot.

  • If b is pressed, the callback for the first timeslot ends the timeslot.

The first timeslot is always of type “earliest”. Any following timeslots are of type “normal”. In each timeslot callback, the signal type of the callback is posted to a message queue. Upon reception of the timeslot start signal, mpsl timer0 is configured to be triggered before the timeslot ends. A separate thread reads the message queue and prints the timeslot signal type. The timeslot session is closed when any key is pressed in the terminal.

Note

For the nRF52 and nRF53 Series mpsl_timer0 is the timer0 instance. For the nRF54L Series mpsl_timer0 is the timer10 instance. For the nRF54H Series mpsl_timer0 is the timer020 instance.

Building and running

This sample can be found under samples/mpsl/timeslot in the nRF Connect SDK folder structure.

To build the sample, follow the instructions in Building an application for your preferred building environment. See also Programming an application for programming steps and Testing and optimization for general information about testing and debugging in the nRF Connect SDK.

Note

When building repository applications in the SDK repositories, building with sysbuild is enabled by default. If you work with out-of-tree freestanding applications, you need to manually pass the --sysbuild parameter to every build command or configure west to always use it.

Note

When using the nRF54H20 DK Engineering B (from v0.8.0 to 0.8.2), you must build samples and applications using the board revision 0.8.0 with the <board>@<revision> syntax. For example, nrf54h20dk@0.8.0/nrf54h20/cpuapp when building for the application core, or nrf54h20dk@0.8.0/nrf54h20/cpurad when building for the radio core.

Testing

After programming the sample to your development kit, complete the following steps to test it:

  1. Connect to the kit with a terminal emulator (for example, nRF Connect Serial Terminal). See Testing and optimization for the required settings and steps.

  2. Follow the instructions in the terminal to open a session and start requesting timeslots. The terminal then prints the signal type for each timeslot callback:

    • If you press a, the timeslot callback requests a new timeslot. Observe that Timeslot start and Timer0 signal are printed until the session is closed.

    • If you press b, the timeslot callback ends the timeslot. Observe that Timeslot start and Timer0 signal are printed, followed by Session idle.

Dependencies

This sample uses the following sdk-nrfxlib libraries:

In addition, it uses the following Zephyr libraries:

  • include/console.h

  • Kernel Services:

    • include/kernel.h

    • include/irq.h

  • include/sys/printk.h

  • include/zephyr/types.h