ARCHITECTURE OVERVIEW
Inside
QRT.
A real-time kernel for software that controls the physical world. See how application APIs, scheduling and optional memory protection fit together.
THE KERNEL
What QRT handles.
01 / SCHEDULING
The next event sets the timer.
QRT programs the hardware timer for the next scheduled event. Its preemptive scheduler manages runnable threads. Timer expiry, interrupt handling and thread execution are distinct parts of the response path.
02 / COORDINATION
Threads need more than CPU time.
Mutexes control access to shared resources. Semaphores
coordinate availability. Message queues pass data between threads. QRT provides these primitives at kernel level, giving application components defined ways to coordinate work.
03 / MEMORY PROTECTION
Access has boundaries.
On supported MPU-equipped targets, configured permissions govern which memory an application context can read, write or execute. A disallowed access raises a fault. The fault handler determines what happens next.
04 / APPLICATION INTERFACE
POSIX at the kernel interface.
QRT implements a documented subset of POSIX.1-2024 natively in the kernel. Threading, synchronisation, message queues and timers use that interface. Compatibility is defined by the implemented API subset.
Processor families
ARM Cortex-M
Target-specific configuration
The processor and port determine timer and interrupt support. Memory protection is optional and requires supported hardware.
SOURCE AND SUPPORT
The implementation
is yours to inspect.
Full kernel source code is included with the commercial licence. The scheduling logic, synchronisation primitives and protection configuration are available for review.
Technical support comes directly from the engineers building QRT.
Get Started
Talk to the team
Reach out to the team for licensing, technical questions, or evaluation.
contact@preemptsystems.com
Salhojankatu 25d
33500 Tampere
FINLAND