Here is a list of all related documentation pages:

Multi Value Registers (1D Register Accessors)	Registers can have more than one value, so they are a one-dimensional "array" of data
2D Register Accessors	A TwoDRegisterAccessor behaves like a two-dimensional array, consisting of several sequences (or channels) which each have a number of samples
Using and creating custom backends
Data Consistency Group	This is a group of register accesses similar to the ReadAnyGroup that ensures that the data consistency of multiple variables matches
Design: AsyncNDRegisterAccessor
Device Mapping	A device map file (dmap file) allows to give alias names for ChimeraTK device descriptors
Exceptions and recovery	This description is explicitly for DeviceAccess
Logical Name Mapping Backend	Backend to map logical register names onto real hardware registers
Basic Example	To use the ChimeraTK::Device class you need a so called "device map" file (dmap file)
Accessing numeric-addressed registers without a map file	During firmware development one might need to access registers without having a map file
Questions and Answers	This page is answering questions which users have asked when working with the DeviceAccess Library
Technical specification DeviceBackend	‍This is a stub to collect snipptes which are not to be forgotten when writing the spec
Technical specification: TransferElement V1.1	‍NOTICE FOR FUTURE RELEASES: AVOID CHANGING THE NUMBERING! The tests refer to the sections, incl
Testing applications using the DummyBackends	This page introduces the DummyBackends provided with ChimeraTK-DeviceAccess
Using push-type inputs with AccessMode::wait_for_new_data	Usually the content of device registers are read out synchronously: Whe read() is called in an accessor the hardware is accessed
XDMA backend
Todo List