Module 5

RTOS
Module:5 Real Time Operating System
Classification of Real time system, Issues & challenges in RTS,
Real time scheduling schemes- EDF-RMS & Hybrid techniques,
eCOS, POSIX, Protothreads.
What are the example of hard real time system?
What are the example of soft real time system?
RTOS Architectures
two prevailing design philosophies affect RTOS design: monolithic
kernel versus microkernel. These systems are differentiated by their
structure; whereas monolithic kernel systems run in a single space,
microkernel systems compartmentalize different components of the
architecture.
Microkernel System Monolithic System
The kernel and operations are Kernel and operation processes
housed in separate spaces, with the share the same space. Operations
kernel itself being bare (hence move more quickly, and the
micro). Operation spaces are not systems boast higher performance.
given access to one another and However, updates may require an
must return to the kernel. extensive overhaul.
LAYMAN EXAMPLE OF MONOLITHIC(two
person sharing same house ) AND
MICROKERNAL(landlord and paying guest)
Real-Time System Examples

Transportatio Manufacturi
A&D Telecom Medical
n ng
•Flight •5G modem •Functional •Magnetic •Factory
display •Satellite safety resonance robotics
controller modem systems imaging systems
•Engine •Base station •Emergency •Surgery •Safety
turbine braking equipment systems
•Drones systems •Ventilators •Oil and gas
•Extraterrestr •Engine vibration
ial rovers warning monitors
systems
What Is an RTOS and How Does It Work?
A real-time operating system (RTOS) is an operating system with
two key features:
• predictability
• determinism.
In an RTOS, repeated tasks are performed within a tight time
boundary, while in a general-purpose operating system, this is
not necessarily so. Predictability and determinism, in this case, go
hand in hand: We know how long a task will take, and that it will
always produce the same result.
RTOS VS. OS?
An RTOS is a type of operating system, but it is vastly different
from the kind most consumers are familiar with.
Operating systems in phones or personal computers are,
comparatively, bloated with apps and features; they must be able to
support anything the user might want to do today.
An RTOS, on the other hand, is streamlined, meant to execute
its tasks quickly and effectively. It is a fraction of the size,
sometimes only a few megabytes (vs. more than 20 gigabytes), with
a simple graphical interface, and it lacks many familiar features,
such as a web browser.
CHARACTERISTICS OF AN RTOS
• Determinism: Repeating an input will result in the same output.ex.M
• High performance: RTOS systems are fast and responsive, often
executing actions within a small fraction of the time needed by a
general OS.
• Safety and security: RTOSes are frequently used in critical systems
when failures can have catastrophic consequences, such as robotics or
flight controllers. To protect those around them, they must have
higher security standards and more reliable safety features.
• Priority-based scheduling: Priority scheduling means that actions
assigned a high priority are executed first, and those with lower
priority come after. This means that an RTOS will always execute the
most important task.
CHARACTERISTICS OF AN RTOS
• Small footprint: Versus their hefty general OS counterparts, RTOSes
weigh in at just a fraction of the size. For example, Windows 10, with
post-install updates, takes up approximately 20 GB. VxWorks®, on
the other hand, is approximately 20,000 times smaller, measured in
the low single-digit megabytes.
 DIFFERENCES AND SIMILARITIES BETWEEN AN EMBEDDED
SYSTEM AND AN RTOS
An embedded system is a computer that is embedded into a larger
machine — for example, the microcontroller on a robotic arm. In
noncritical systems with some timeline flexibility, developers can use an
open source general-purpose OS (GPOS) such as Linux. Linux is full
featured, flexible, and well known.
In a critical system (whether that means safety critical or mission
critical), developers opt for real-time operating systems. The
characteristics that set an RTOS apart are often essential to success. For
instance, a robotic arm in a factory needs to be predictable and reliable,
and it must be able to stop immediately when employees enter its
area of operation. Variability can result in wasted resources, quality-
control issues, or injury.
A robotic arm must be able to stop immediately when employees enter its area of operation.
 RTOS Use in Embedded Systems
Due to its benefits, a real-time operating system is most often used in an
embedded system — that is, a system that operates behind the scenes of
a larger operation. The RTOS usually has no graphical interface.
Occasionally, multiple OSes are integrated simultaneously, to provide
operational capability coupled with the usability of a general-purpose
OS.

RTOSes are often in intelligent edge devices, also known as

electromechanical edge or cyber-physical systems. This means that
the device is both producing and operating upon data. So a car, for
example, would be able to monitor its surroundings and act upon
them instantaneously on its own. Such devices often couple artificial
intelligence or machine learning, or both, with real-time components
FEATURES AND ADVANTAGES OF AN RTOS

An RTOS is small, fast, responsive, and deterministic. This means

that it will execute tasks quickly and efficiently, responding as
expected every time.
Due to the significance of its host device, the RTOS infrastructure is
more secure and less likely to crash or fail.
Finally, an RTOS is developer oriented, meaning that it continues to
roll out updates that help users code more effectively.
Now a day OS is RTOS
BASED LIKE
UPDATION in OS
Benefits and Risks of a Commercial vs. In-House RTOS
Some companies try to produce their own RTOS in house, tailor-made
for their project, instead of buying a commercial off-the-shelf operating
system. This has some advantages: The operating system is designed
specifically for the use case, and the company understands its
mechanics and inner workings. However, this approach is often more
expensive and more time-consuming, and developers who are not
used to working on operating systems take a great deal of time to
produce one. Using a commercial system is faster, easier, and brings
the benefit of an experienced technical team that can answer questions
and provide support. An operating system is a tool, much like a
hammer or a drill. While you could make one — one that you would
thoroughly understand and that might fit your project better — it would
take a lot of time, without guarantees of performance or capability.
WHY USE AN RTOS?
In applications that require reliable and repeatable actions, the
RTOS is favored over its general OS counterpart. Especially in
embedded or critical systems, where reliability and speed are
essential, a real-time operating system is needed.
A hard real-time task must be performed at a specified time which
could otherwise lead to huge losses. In soft real-time tasks, a
specified deadline can be missed.
IF deadline missed
how to handle?
 the task can be rescheduled (or) can be
completed after the specified time,
Thank you
References
[1] https://www.windriver.com/solutions/learning/rtos
[2] https://www.embedded.com/rtos-trends-and-challenges/
[3]https://epgp.inflibnet.ac.in/epgpdata/uploads/epgp_content/
S000007CS/P001072/M023184/ET/1505901073mod26(1.pdf)
[4] https://www.linkedin.com/pulse/task-scheduling-rtos-madhavan-
vivekanandan/