ESL OS RT / Real-Time Platform

Real-time systems engineered for safety-focused products.

ESL OS RT brings real-time operating-system integration, board support, timing analysis and security lifecycle planning together around your product requirements and target hardware.

Discuss an ESL OS RT project
ESL OS RT safety-critical real-time platform architecture illustration
Concept architecture for discussion. Kernel choice, safety mechanisms, hardware partitioning and assurance evidence must be defined and verified for each product; this diagram does not indicate certification.

Timing, boundaries and lifecycle

Build the platform around the system requirements.

Real-time behavior and safety assurance depend on the complete system, not the kernel alone. ESL works with product teams to connect application timing, hardware capabilities, failure handling, verification and maintenance into a scoped engineering plan.

01 / DETERMINISTIC EXECUTION

Measure the timing that matters

Define task priorities, deadlines, interrupt response and resource budgets, then measure behavior on the selected processor, board, drivers and representative workload.

02 / SAFETY BOUNDARIES

Design for faults and safe states

Assess watchdogs, interlocks, supervisory logic, recovery paths and hardware or software separation against the product hazard analysis and system safety concept.

03 / SECURITY LIFECYCLE

Maintain visibility after release

Plan component inventory, SBOM generation, vulnerability assessment, controlled update decisions and change-impact review as part of product maintenance.

01 / SCOPE

Translate product needs

Agree on timing targets, safety constraints, hardware, interfaces, applicable standards and evidence expectations.

02 / INTEGRATE

Assemble the platform

Integrate the selected RT kernel, board support, drivers, application interfaces and security controls for the target.

03 / VERIFY

Test and document

Validate timing, fault handling, updates and release artifacts on representative hardware, with results traceable to agreed requirements.

Planning a deterministic or safety-focused embedded system?

Talk with ESL

ESL OS RT / Assurance planning

Evidence and compliance are product-specific.

Start with the product’s intended use, hazards, threat model and market requirements. Map platform engineering, verification, change control and maintenance evidence to the manufacturer’s development and regulatory processes.

01 / REQUIREMENTS

Set the assurance scope

Identify product risks, safety boundaries, security goals, timing constraints and the responsibilities of the manufacturer and engineering partners.

02 / VERIFICATION

Trace tests to requirements

Plan target-level timing, interface, fault-response and regression tests. Record results and limitations against the agreed system requirements.

03 / MAINTENANCE

Control product changes

Track platform components, vulnerability dispositions, update decisions and change impact across maintenance releases and the product’s support plan.

Standards note

Depending on product, market and intended use, project inputs may include IEC 62304, IEC 60601-1-8, IEC 81001-5-1, ISO 14971, ISO 13485 or applicable regulatory guidance. These are considerations for project scoping, not a claim that ESL OS RT is certified, compliant, or approved. The manufacturer owns regulatory determinations and product conformity.