Osy Micro Project Harsh
Osy Micro Project Harsh
Osy Micro Project Harsh
Micro project On
Submitted By
Guided By
Mrs. A.V.Kurkute
Sinhgad Institutes
PUNE – 411041
SR NO CONTENTS PAGE NO
2 Rationale 03
4 Literature Review 04
7 Skills Developed 07
Annexure – I
Micro-Project Proposal
a) The aim of to collect the information about real time operating system.
b) to understand how a desktop OS works
c) tutorial for beginner of operating.
i. Study the various functions of Operating System and learn about it.
ii. Study and learn to use software.
Name of
Sr. Planned Planned
Details of Activity responsible
No. Start Finish
Team
Date Date
members
1 33 Harsh Murkewar
Annexure - II
Micro-Project Report
1.0 Rationale:
A real-time operating system (RTOS) is an operating system capable of
guaranteeing timing requirements of the processes under its control. While a time-
sharing OS like UNIX strives to provide good average performance, for a RTOS,
correct timing is the key feature. Throughput is of secondary concern. In order to
deliver the tight worst-case timing performance needed by hard real-time, the RTOS
needs to be simple, small, predictable, and optimized to minimize the worst-case
performance. Linux operating system which started as a student project by Linus
Travaldo gained momentum.in in late 80s is now a complete operating system meeting
requirements of nearly all type of users. Further large group of developers are adding
features to the core kernel as well as KLM (kernel loadable modules).Several
techniques and patches are available to customize and modify bare Linux kernel to be
acceptable as a hard real time operating system. This article discusses these issues. This
paper attempts to throw some light on the technologies behind the embedded systems
design and concludes by the survey of some of the available real-time operating
systems.
a) The aim of to collect the information about real time operating system.
b) to understand how a desktop OS works
c) tutorial for beginner of operating.
• Firm: Firm real-time systems have hard deadlines, but where a certain low
probability of missing a deadline can be tolerated.
Most real-time systems interface with and control hardware directly. The
software for such systems is mostly custom-developed. Real-time Applications
can be either embedded applications or nonembedded (desktop) applications.
Real-time systems often do not have standard peripherals associated with a
desktop computer, namely the keyboard, mouse or conventional display monitors.
In most instances, real-time systems have a customized version of these devices.
Real-time computing is where system correctness not only depends on the correctness
of logical result but also on the result delivery time. So the operating system should
have features to support this critical requirement to render it to be termed a Real-time
operating System (RTOS). The RTOS should have predictable behavior to
unpredictable external events. A good RTOS is one that has a bounded (predictable)
behavior under all system load scenario i.e. even under simultaneous interrupts and
thread execution.
However, care must be taken to avoid starvation, which occurs when higher priority
tasks are always ready to run, resulting in insufficient processor time for lower priority
tasks. Non-prioritized interrupts should be avoided if there is a task that cannot be
preempted without causing system failure. Ideally, the interrupt handler should save
the context, create a task that will service the interrupt, and return control to the
operating system. Using a task to perform bulk of the interrupt service allows the
service to be performed based on a priority chosen by the designer and helps preserve
the priority system of the RTOS. Furthermore, good response times may require small
memory footprints in resource-impoverished systems. Clearly the choice of an RTOS
in the design process is important for support of priorities, interrupts, timers, inter-
task communication, synchronization, multiprocessing and memory management.
(i) Multi-tasking and preemptable: To support multiple tasks in real- time applications,
an RTOS must be multi-tasking and preemptable. The scheduler should be able to
preempt any task in the system and give the resource to the task that needs it most. An
RTOS should also handle multiple levels of interrupts to handle multiple priority
levels.
An RTOS uses small memory size by including only the necessary functionality for
an application while discarding the rest. Below we discuss static and dynamic memory
management in RTOSs. Static memory management provides tasks with temporary
data space. The systems free memory is divided into a pool of fixed sized memory
blocks, which can be requested by tasks. When a task finishes using a memory block
it must return it to the pool. Another way to provide temporary space for tasks is via
priorities. A pool of memory is dedicated to high priority tasks and another to low
priority tasks. The high-priority pool is sized to have the worst-case memory demand
of the system. The low priority pool is given the remaining free memory. If the low
priority tasks exhaust the low priority memory pool, they must wait for memory to be
returned to the pool before further execution.
.3 Task Scheduling
Etc.S
References
[1] Dedicated Systems Experts; What makes a good RTOS. Brussels, Belgium:
Dedicated Systems Experts,2020 .
Conclusion
Real time Operating systems play a major role in the field of embedded systems
especially for mission critical applications are involved. Selection of a particular
RTOS for an application can be made only after a thorough study of the features
provided by the RTOS. Since IC memories are getting denser scaled down
versions of general operating systems are able to compete with traditional Real
Time Operating Systems for the embedded product market. The choice of
Operating System generally comes after the selection of the processor and
development tools.