NRF9160-SIBA-R datasheet(18/400 Pages) NORDIC

18 / 400 page

Product overview

A task is triggered when firmware writes '1' to the task register, or when the peripheral itself or another

peripheral toggles the corresponding task signal. See the figure Peripheral interface on page 16.

3.3.6 Events

Events are used to notify peripherals and the CPU about events that have happened, for example a state

change in a peripheral. A peripheral may generate multiple events, where each event has a separate

An event is generated when the peripheral itself toggles the corresponding event signal, and the event

16. An event register is cleared when a '0' is written to it by firmware. Events can be generated by the

peripheral even when the event register is set to '1'.

3.3.7 Publish and subscribe

Events and tasks from different peripherals can be connected together through the DPPI system using the

PUBLISH and SUBSCRIBE registers in each peripheral. See Peripheral interface on page 16. An event

can be published onto a DPPI channel by configuring the event's PUBLISH register. Similarly, a task can

subscribe to a DPPI channel by configuring the task's SUBSCRIBE register.

See DPPI - Distributed programmable peripheral interconnect on page 86 for details.

3.3.8 Shortcuts

A shortcut is a direct connection between an event and a task within the same peripheral. If a shortcut is

enabled, the associated task is automatically triggered when its associated event is generated.

Using shortcuts is equivalent to making the connection outside the peripheral and through the DPPI.

However, the propagation delay when using shortcuts is usually shorter than the propagation delay

through the DPPI.

Shortcuts are predefined, which means that their connections cannot be configured by firmware. Each

shortcut can be individually enabled or disabled through the shortcut register, one bit per shortcut, giving

a maximum of 32 shortcuts for each peripheral.

3.3.9 Interrupts

All peripherals support interrupts which are generated by events.

A peripheral only occupies one interrupt, and the interrupt number follows the peripheral ID. For example,

the peripheral with ID=4 is connected to interrupt number 4 in the nested vectored interrupt controller

(NVIC).

Using registers INTEN, INTENSET, and INTENCLR, every event generated by a peripheral can be

configured to generate that peripheral's interrupt. Multiple events can be enabled to generate interrupts

simultaneously. To resolve the correct interrupt source, the event registers in the event group of

peripheral registers will indicate the source.

Some peripherals implement only INTENSET and INTENCLR registers, and the INTEN register is not

available on those peripherals. See the individual peripheral chapters for details. In all cases, reading back

the INTENSET or INTENCLR register returns the same information as in INTEN.

Each event implemented in the peripheral is associated with a specific bit position in the INTEN, INTENSET,

and INTENCLR registers.

The relationship between tasks, events, shortcuts, and interrupts is illustrated in figure Peripheral interface

on page 16.

4418_1315 v2.0

NRF9160-SIBA-R Datasheet(PDF) 18 Page - Nordic Semiconductor