Component set

Channel Controller (cc)

Creates and manages processing channels for signals received from the RF front end. Acquires and tracks signals, decodes telemetry, and writes channel measurements to the Channel Measurement Table. Controls the correlators implemented in programmable logic and distributes tasks across CPU cores and FPGA fabric to exploit the MPSoC's heterogeneous architecture.

Environment Manager (em)

Controls the RF front-end chain: gain controllers, direct-conversion tuners, LPF/BPF/HPF filters, and variable-rate decimators. Runs anti-jamming algorithms to protect the receiver from intentional interference. Maintains the RFChain abstraction — the set of controllable components in a single chain — and exposes an API for the Channel Controller and other components to configure gain, filter, and decimation state per RF stream.

Satellite Manager (sm)

Owns all satellite-state information used by the PVT Provider to compute position and time. Stores orbital parameters for each satellite and provides the context needed to apply corrections to raw measurements — ephemeris, almanac, and ionospheric/tropospheric correction context.

PVT Provider (pp)

Computes the position, velocity, and time (PVT) solution from Satellite Manager measurements. Estimates satellite locations from ephemeris or almanac data, runs integrity algorithms (RAIM) to detect and mitigate faulty measurements, and can compute the solution using Ordinary Least Squares or a Kalman Filter depending on application configuration.

Assurance Manager (am)

Ensures the reliability and accuracy of the PVT solution. Aggregates assurance metrics from assurance functions distributed across the Channel Controller, Satellite Manager, PVT Provider, and Environment Manager to compute an overall assurance level. Owns integrity algorithms — including Receiver Autonomous Integrity Monitoring (RAIM) — that detect and mitigate errors from faulty sensor data or interference.

System Controller (sc)

Central hub for system control. Manages component lifecycle, system state, and CRUD on shared data. Allocates system resources (CPU time, memory, I/O) across components and enforces real-time constraints so that time-critical tasks meet their deadlines.

Security Kernel (sk)

Implements and manages secure boot, software authentication, secure reprogramming, data-at-rest encryption, and access control. Designed to meet Information Assurance and Anti-Tamper requirements in contested PNT threat environments while protecting sensitive data and controlled signal access.

Mission IO (mio)

Bridges the SERGEANT component set to the host mission computer. Adapts internal component state and commands to the mission-computer interface — receiving commands and surfacing receiver state and measurements back out.

Operating System (os)

Provides the runtime the rest of SERGEANT builds on: task scheduling, resource management, and hardware abstraction between the application software and the Zynq UltraScale+ MPSoC. Enforces real-time scheduling for time-critical tasks.

Fault Manager (FDIR) (fm)

Fault Detection, Isolation, and Recovery. Continuously monitors the system for hardware and software faults, diagnoses them, isolates the faulty component or subsystem, and recovers the system to a functional state. Critical for mission reliability in safety-critical applications.

Test Harness (th)

Test and validation harness for the overall system and individual components. Provides test cases and procedures for evaluating performance, reliability, and functionality across development, integration, and deployment phases.

Software Development Kit (sdk)

Tools and libraries for third-party application development against the SERGEANT framework — access to FPGA fabric, CPU cores, memory, and component APIs, plus the development toolchain (compilers, debuggers, simulators) for building and validating custom applications.