NRF52810-QFAA-R datasheet(95/483 Pages) NORDIC

95 / 483 page

Peripherals

6.1.2 Peripherals with shared ID

In general, and with the exception of ID 0, peripherals sharing an ID and base address may not be used

simultaneously. The user can only enable one at the time on this specific ID.

When switching between two peripherals that share an ID, the user should do the following to prevent

unwanted behavior:

• Disable the previously used peripheral

• Remove any PPI connections set up for the peripheral that is being disabled

• Clear all bits in the INTEN register, i.e. INTENCLR = 0xFFFFFFFF.

• Explicitly configure the peripheral that you enable and do not rely on configuration values that may be

inherited from the peripheral that was disabled.

• Enable the now configured peripheral.

See Instantiation on page 17 to see which peripherals are sharing ID.

6.1.3 Peripheral registers

Most peripherals feature an ENABLE register. Unless otherwise specified in the relevant chapter, the

peripheral registers (in particular the PSEL registers) must be configured before enabling the peripheral.

Note that the peripheral must be enabled before tasks and events can be used.

6.1.4 Bit set and clear

Registers with multiple single-bit bit fields may implement the "set-and-clear" pattern. This pattern

enables firmware to set and clear individual bits in a register without having to perform a read-modify-

write operation on the main register.

This pattern is implemented using three consecutive addresses in the register map where the main

The SET register is used to set individual bits in the main register while the CLR register is used to clear

individual bits in the main register. Writing a '1' to a bit in the SET or CLR register will set or clear the same

bit in the main register respectively. Writing a '0' to a bit in the SET or CLR register has no effect. Reading

the SET or CLR registers returns the value of the main register.

Restriction: The main register may not be visible and hence not directly accessible in all cases.

6.1.5 Tasks

Tasks are used to trigger actions in a peripheral, for example, to start a particular behavior. A peripheral

can implement multiple tasks with each task having a separate register in that peripheral's task register

group.

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

peripheral toggles the corresponding task signal. See Tasks, events, shortcuts, and interrupts on page

94.

6.1.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 with each event having a separate

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

interrupts on page 94. An event register is only cleared when firmware writes a '0' to it.

4430_161 v1.0

NRF52810-QFAA-R Datasheet(PDF) 95 Page - Nordic Semiconductor