Operating System Independent Print E-mail

Overview

Since hardware obsolescence must be managed with a strict control strategy, CES has applied a similar risk control strategy to our software products, which are delivered bundled with the boards.

Target specifications require an identical set of functionalities, independent of the underlying operating system. Only performance and size differentiation is allowed for each operating system. Software changes can also lead to major unexpected program failures, costing either time, money or even requiring complete redesign.

No-Risk Approach

CES took the hard way (ie. multiple software designers for each hardware designer) by designing the BSPs in-house for each of the supported operating systems (ie. VxWorks®, Integrity®, LynxOS® and Linux®). The risk incurred by the software choice is totally removed for the customer and assumed by CES. This unique approach has immediate advantages, such as selecting one platform for multiple programs requiring different operating systems or allowing to mix operating systems on the same platform.

  • Example: Both VxWorks® and Integrity® are available for the RIOC-4070, each sharing the same calls.

RIOC-4070


  • Example: The RIO4-8070 can run VxWorks® on the front-end CPU and Linux® on the back-end CPU.

RIO4-8070