An RTOS decision can become costly long before licensing is signed if certification evidence arrives late or fails to match the software actually deployed. In embedded programs governed by standards such as ISO 26262, IEC 61508, DO-178C or IEC 62304, the operating system becomes part of the assurance argument rather than a replaceable software utility. Procurement therefore has to look past scheduling performance. The harder question is whether the RTOS can be incorporated into the target architecture without creating avoidable verification work or uncertainty during external assessment.
Certification readiness should be judged at the level of evidence, not the presence of a certificate alone. Buyers need to understand how requirements map to tests and whether the supplied artifacts match the processor and compiler combination used in production. Evidence that was generated for a nearby configuration can still leave engineering teams with additional justification work. Traceability and test coverage matter because an auditor is evaluating the software actually integrated into the product, not a generic kernel description. A usable evidence package should also expose assumptions and installation conditions clearly enough that engineers can complete integration records without reconstructing the supplier’s development argument.
Stay ahead of the industry with exclusive feature stories on the top companies, expert insights and the latest news delivered straight to your inbox. Subscribe today.
Hardware fit deserves the same scrutiny. Processor families change quickly, yet a safety program may remain tied to a chosen device for years. An RTOS supplier should be able to port its kernel without altering the behavior that has already been established and verified. A clear separation between common kernel code and hardware-specific code can reduce the amount of software that must change when a new processor is introduced. The buyer should also examine how the supplier validates compiler output and how much regression testing follows each port.
Migration effort can quietly determine whether a technically suitable RTOS is practical. Engineering teams often prototype before formal safety development begins, which creates a handoff risk if the production kernel uses a very different programming model. A familiar API structure can limit rework, but compatibility claims deserve close examination. The important measure is the amount of code that must change and whether the supplier provides a controlled route into the safety version rather than leaving the development team to reinterpret the differences alone.
“Wittenstein High Integrity Systems’ SAFERTOS offering is delivered for the customer’s processor and compiler combination, backed by verification at the object-code level and 100 percent MC/DC coverage.”
Long product lives make supplier continuity another purchasing issue. Safety-related products can remain in service well beyond a normal software refresh cycle, while processors and toolchains may be revised during that period. Source-code access can reduce dependency on continued vendor intervention, though buyers should also examine the support model around certification questions. Technical assistance is useful, but direct help with safety evidence and integration can be more consequential when an audit exposes an unfamiliar requirement. Renewal terms should not become a hidden lock-in mechanism.
For programs where certification effort carries as much weight as kernel performance, Wittenstein High Integrity Systems warrants priority consideration. Its SAFERTOS offering is delivered for the customer’s processor and compiler combination, backed by verification at the object-code level and 100 percent MC/DC coverage. Its Design Assurance Pack provides the lifecycle evidence needed to support certification while processor- and compiler-specific verification reduces uncertainty around the deployed build. The migration path from FreeRTOS can also shorten the move from prototyping into formal development. Buyers that want a tightly evidenced RTOS and direct safety support should place Wittenstein High Integrity Systems near the top of the shortlist.
