Scribd
Upload
4K views6 pages

How To Choose An RTOS

The document discusses factors to consider when choosing a real-time operating system (RTOS) for an embedded design. Key functional requirements include processor and memory support, real-time capabilities, interrupt latency, inter-process communication, and language support. Non-functional factors are whether it is custom-built or off-the-shelf, costs, availability of development tools, ease of use, and after-sales support. Careful analysis of both functional and non-functional requirements is needed to select the best-fit RTOS.

Uploaded by

syedashmad
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
4K views6 pages

How To Choose An RTOS

The document discusses factors to consider when choosing a real-time operating system (RTOS) for an embedded design. Key functional requirements include processor and memory support, real-time capabilities, interrupt latency, inter-process communication, and language support. Non-functional factors are whether it is custom-built or off-the-shelf, costs, availability of development tools, ease of use, and after-sales support. Careful analysis of both functional and non-functional requirements is needed to select the best-fit RTOS.

Uploaded by

syedashmad
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 6

How to Choose an RTOS

Introduction
• The decision of an RTOS for an embedded
design is very critical.
• A lot of factors need to be analyzed carefully
before making a decision on the selection of
an RTOS.
• These factors can be either
• 1. Functional
• 2. Non-functional requirements.
Functional Requirements
Processor support:
• It is not necessary that all RTOS’s support all kinds of processor
architectures.
• It is essential to ensure the processor support by the RTOS.
Memory Requirements:
• The RTOS requires ROM memory for holding the OS files and it is normally
stored in a non-volatile memory like FLASH.
• OS also requires working memory RAM for loading the OS service.
Real-Time Capabilities:
• It is not mandatory that the OS for all embedded systems need to be Real-
Time and all embedded OS’s are ‘Real-Time’ in behavior.
Kernel and Interrupt Latency:
• The kernel of the OS may disable interrupts while executing certain
services and it may lead to interrupt latency.
Functional Requirements Cont…
Inter process Communication (IPC) and Task Synchronization:
• The implementation of IPC and Synchronization is OS kernel
dependent.
Modularization Support:
• It is very useful if the OS supports modularization where in which
the developer can choose the essential modules and re-compile
the OS image for functioning.
Support for Networking and Communication:
• The OS kernel may provide stack implementation and driver
support for a bunch of communication interfaces and networking.
Development Language Support:
• Certain OS include the run time libraries required for running
applications written in languages like JAVA and C++.
Non-Functional Requirements
Custom Developed or Off the Shelf:
• It is possible to go for the complete development of an OS suiting
the embedded system needs or use an off the shelf, readily
available OS.
Cost:
• The total cost for developing or buying the OS and maintaining it in
terms of commercial product and custom build needs to be
evaluated before taking a decision on the selection of OS.
Development and Debugging tools Availability:
• The availability of development and debugging tools is a critical
decision making factor in the selection of an OS for embedded
design.
Non-Functional Requirements Cont..
Ease of Use:
• How easy it is to use a commercial RTOS is another
important feature that needs to be considered in the
RTOS selection.
After Sales:
• For a commercial embedded RTOS, after sales in the
form of e-mail, on-call services etc. for bug fixes,
critical patch updates and support for production
issues etc. should be analyzed thoroughly.

You might also like