Architecture
The SERGEANT framework
A modular software/firmware framework for parallel, DSP-intensive GNSS signal processing on a heterogeneous MPSoC.
SERGEANT is organized as a set of cooperating components. A small core set — Environment Manager, Channel Controller, Satellite Manager, and PVT Provider — carries the RF-to-PVT signal processing chain. An extended set handles assurance, security, system control, fault recovery, mission integration, and developer tooling around it.
System view
The full component set, grouped by tier. Every block links to its detail page.
Signal processing chain
A zoom-in on the base tier — how a GNSS signal moves from antenna to the host mission computer through the four signal-processing components.
Design traits
-
Concurrent module architecture
SERGEANT components are active entities with their own threads, communicating through OS-level mechanisms — message queues and shared memory. This exploits the MPSoC's multi-core application processor effectively and keeps inter-component coupling at the interface boundary.
-
Hardware-accelerated where it matters
The most demanding real-time signal processing — correlation, decimation, anti-jam filtering — runs in programmable logic. The application software orchestrates; the fabric computes.
-
Open-systems foundation
Documented module interfaces give integrators the ability to replace SERGEANT modules and plug in third-party applications. Vendor lock-in is an explicit non-goal.
-
Obsolescence-resistant by design
MAGNOM's modular card-stack lets processing, logic, and RF cores refresh independently. SERGEANT's abstraction layer keeps the application software stable across hardware generations.
Component detail
Each of the 12 components has its own page covering responsibilities, interfaces, and modules.