1.WHAT IS AN RTOS?

->A real-time operating system (RTOS) is an operating system (OS) intended for real-time applications. Such

operating systems serve application requests nearly real-time. A real-time operating system offers programmers

more control over process priorities. An application's process priority level may exceed that of a system process.

Real-time operating systems minimize critical sections of system code, so that the application's interruption is nearly

critical.
A key characteristic of a real-time OS is the level of its consistency concerning the amount of time it takes to accept
and complete an application's task; the variability is jitter. A hard real-time operating system has less jitter than
a soft real-time operating system. The chief design goal is not high throughput, but rather a guarantee of a soft or
hard performance category. A real-time OS has an advanced algorithm for scheduling.

real-time OS is more frequently dedicated to a narrow set of applications. Key factors in a real-time OS are

minimal interrupt latency and minimal thread switching latency, but a real-time OS is valued more for how quickly or

how predictably it can respond than for the amount of work it can perform in a given period of time.

Memory allocation is more critical in an RTOS than in other operating systems.

First, speed of allocation is important. A standard memory allocation scheme scans a linked list of indeterminate

length to find a suitable free memory block. This is unacceptable in an RTOS since memory allocation has to occur

within a certain amount of time.

The simple fixed-size-blocks algorithm works quite well for simple embedded systems because of its low overhead.

2.)SYMBIAN:
Symbian OS is one of Nokia's mobile operating systems for mobile devices and low-endsmartphones,
with associated libraries, user interface, frameworks and reference implementations of common tools,
originally developed by Symbian Ltd.

In 2008, the former Symbian Software Limited was acquired by Nokia and a new independent non-profit
organisation called the Symbian Foundation was established. Symbian OS and its associated user
interfaces S60, UIQ and MOAP(S) were contributed by their owners to the foundation with the objective of
creating the Symbian platform as a royalty-free, open source software. The platform has been designated
as the successor to Symbian OS, following the official launch of the Symbian Foundation in April 2009.
The platform was officially made available as open source code in February 2010.

Devices based on Symbian OS account for 46.9% of Smartphone sales.

Design
Symbian features pre-emptive multitasking and memory protection, like other operating systems
(especially those created for use on desktop computers). EPOC's approach to multitasking was inspired
by VMS and is based on asynchronous server-based events.

Symbian OS was created with three systems design principles in mind:

 the integrity and security of user data is paramount,

 user time must not be wasted, and
 all resources are scarce.

To best follow these principles, Symbian uses a microkernel, has a request-and-callback approach to
services, and maintains separation between user interface and engine. The OS is optimized for low-
power battery-based devices and for ROM-based systems (e.g. features like XIP and re-entrancy in
shared libraries). Applications, and the OS itself, follow an object-oriented design: 

Disks on Symbian devices are usually flash memory).

). Furthermore, all Symbian programming is event-based, and the CPU is switched into a low power mode
when applications are not directly dealing with an event. This is achieved through a programming idiom
called active objects. Similarly the Symbian approach to threads and processes is driven by reducing
overheads.

The Symbian kernel (EKA2) supports sufficiently-fast real-time response to build a single-core phone

around it — that is, a phone in which a single processor core executes both the user applications and
the signaling stack.[6] This has allowed Symbian EKA2 phones to become smaller, cheaper and more
power efficient than their predecessors [citation needed].

Features Of Symbian Operating System

1) Generally, the language C++ is used in most of the symbian operating systems. But in many Symbian
Operating System the operating system can also use languages like Python, Visual Basic, OPL and Perl

2) Symbian Operating System was built in such a way that it follows the three basic design rules.

 The integrity and security of user data is of paramount importance.

 Response time must not be as small as possible.

 All resources are scarce.

3) Symbian OS programming is said to be event-based, and the Central Processing Unit is switched off when the
running applications and programs are not linked to the event. This is achieved through a programming logic called
active objects.

5) The Symbian Operating system is compatible with all kinds of devices, mostly removable media file systems.

6) Symbian Operating system 9.x which is one of the latest models has adopted a better model.

7) The Symbian system is not Open Source software. Cell phone manufacturers, though have some parts of its
source code.

8) The Symbian applications like the Themes, games, wall papers and software’s are all SIS files which can also be
easily transferred by using Bluetooth, or through the internet or through transfer using cables.

Symbian Applications
Symbian phones have numerous applications like business tools, educational tools and different tools
which help in making our mobile phones more user friendly. Dictionaries, Alarm Clocks, Mp3 players,
photograph editors and call related tools are some of these Applications. Here are a few of the widely
used applications.

 1) Spy Call: This soft ware helps you to be able to record the conversations that you make with other
people on your cell phone. This software helps you to record calls very conveniently with just a single
touch.

2) BlackBaller: It is a filter that allows you to reject unwanted calls and messages that may disturb you
when you are busy. It gives you unique features like message filtering, and the latest friendly feature -
Smart Reject Sensor and thus will prevent you from getting disturbed.

3) SmartMovie: With this converter, you may view an avi or any other video clip on the screen of your
cell phone with ease.

4) Office Suite: This software enables you to to make text documents, calculate, compute, research and
analyze data right on your symbian cell phone.

5) Mobi Factor power MP3 player: This will allow you to listen to MP3, OGG, AAC and M4A on your cell
phone. It has a skin selector, equalizer, a custom playlist to arrange your melodies and various other
features to give you a blissful music experience.

6) Auto Key Lock: It is an application created especially for users that have a big problem forgetting to
lock the keypad of their phones. Since the Keypad locks automatically, It prevents self-dialing by
having the keys pressed accidentally by the user's hand or some object while it is in the pocket.

7) PhotoRite: It is a highly useful and improved image processing software to perform automatic
modifications on your photos and to edit your photos with ease. Photos processed by PhotoRite will
always have better quality then the ones clicked by the camera.
 SYMBIAN s/w h/w requirements:
System Requirements:
====================
Basic Requirements:
- Microsoft Windows XP SP2 or Microsoft Windows 2000 SP4. Tested with Windows XP SP2.
- IDE: CodeWarrior for Symbian OS v3.1
- ARM RVCT compiler 2.2 build 503 or newer is supported. (Version 3.0 is not supported by SDK toolchain)
- Minimum 1 GHz Pentium PC, 256 MB of memory
- Up to 1.5 GB free disk space, other requirements as required by the IDE used.

Additional Requirements:
- Installation/uninstallation and using of the SDK requires local admin rights.
- Active Perl 5.6.1 build 631 for SDK build tools. Newer or older versions of Perl may not be fully compatible with
Symbian toolchain. Perl must be installed before using the SDK to build applications.
- Java Runtime version 1.4.1_02 or later is required.
- Casira hardware is required for Bluetooth connectivity emulation.

INSTALLATION STEPS:
Symbian platform (Symbian Foundation)
Symbian^1 models 5230 · 5250 · 5530 XpressMusic · 5800 XpressMusic · C6-00 · N97 · N97 Mini · Omnia HD · Satio · Vivaz · Vivaz Pro · X6-00
Symbian^2 models (Fujitsu: docomo F-06B · docomo F-07B · docomo F-08B · F-10B · Raku-Raku PHONE 7 / Sharp: docomo SH-07B)
Symbian^3 models C6-01  · C7-00 · E7-00 · N8
Symbian^1-3 device
Fujitsu · Nokia · Samsung · Sharp · Sony Ericsson
manufacturers (current)

ARCHITECTURE
Structure: The Symbian System Model contains the following layers, from top to bottom:
 UI Framework Layer
 Application Services Layer
 Java ME
 OS Services Layer
 generic OS services
 communications services
 multimedia and graphics services
 connectivity services
 Base Services Layer
 Kernel Services & Hardware Interface Layer

The Base Services Layer is the lowest level reachable by user-side operations; it includes the File
Server and User Library, a Plug-In Framework which manages all plug-ins, Store, Central
Repository, DBMS and cryptographic services. It also includes the Text Window Server and the Text
Shell: the two basic services from which a completely functional port can be created without the need for
any higher layer services.

Symbian has a microkernel architecture, which means that the minimum necessary is within the kernel
to maximize robustness, availability and responsiveness. It contains a scheduler, memory
management and device drivers, but other services like networking, telephony and file system support are
placed in the OS Services Layer or the Base Services Layer. The inclusion of device drivers means the
kernel is not a true microkernel. The EKA2 real-time kernel, which has been termed a nanokernel,
contains only the most basic primitives and requires an extended kernel to implement any other
abstractions.

Symbian is designed to emphasize compatibility with other devices, especially removable media file
systems. The internal data formats rely on using the same APIs that create the data to run all file
manipulations. This has resulted in data-dependence and associated difficulties with changes and data
migration.

There is a large networking and communication subsystem, which has three main servers called:

ETEL (EPOC telephony),

ESOCK (EPOC sockets) and

C32 (responsible for serial communication).

Each of these has a plug-in scheme. For example ESOCK allows different ".PRT" protocol modules to
implement various networking protocol schemes. The subsystem also contains code that supports short-
range communication links, such as Bluetooth, IrDA and USB.

There is also a large volume of user interface (UI) Code. Only the base classes and substructure were
contained in Symbian OS, while most of the actual user interfaces were maintained by third parties. This
is no longer the case. The three major UIs - S60, UIQ and MOAP - were contributed to Symbian in 2009.
Symbian also contains graphics, text layout and font rendering libraries.

All native Symbian C++ applications are built up from three framework classes defined by the application
architecture: an application class, a document class and an application user interface class. These
classes create the fundamental application behavior. The remaining required functions, the application
view, data model and data interface, are created independently and interact solely through their APIs with
the other classes.

This has the advantage that the APIs to such areas of functionality are the same on many phone models,
and that vendors get a lot of flexibility. But it means that phone vendors needed to do a great deal of
integration work to make a Symbian OS phone.

Symbian includes a reference user-interface called "TechView". It provides a basis for starting
customization and is the environment in which much Symbian test and example code runs.

INSTALLATION STEPS:
 SIS is an acronym that stands for Software Installation Script. It is an archive for Symbian OS, and not an

application file, as sometimes believed; the real Symbian application is the .APP or.EXE file within it. By

convention .sisx denotes a signed file.

There are different ways how a SIS file can be created. The basic approach is to create a package definition file
(.pkg) that contains information about the package like the vendor, package name and what files to include in the
package. Then use the make sis and sign sis utilities that process the .pkg file and create the actual SIS file.[1] Other
alternatives are to use the Carbide c++ IDE that automatically builds the SIS file as part of the build process or to
graphically define and create the installation package using Package Forge.[2]

The power is in your hands with Symbian

Symbian^3 is our most powerful platform release yet. It's also Symbian’s first fully open source, royalty-free platform,
available for anyone to create state of the art mobile devices such as the new Nokia N8.

The beauty of Symbian is the ability to take it and build something truly special and unique. No other platform is
structured in the same way. The Symbian platform is self-contained and fully accessible, allowing you to bring to life new
services and ideas in mobile product design.

 A complete and customizable platform

A fully adaptable platform designed specifically for modern mobile communication, to create everything from low-cost
feature-rich phones to high end smartphones.
 Total UI design flexibility
A complete touch screen solution with effortless multitasking, full platform theming and home screen customization, giving
real design flexibility and huge scope for differentiation.
 Better network management
Simple connection management providing easy and secure access to the Internet - just select the networks that work best
when you want to connect and the platform will help get you the most from whichever network is available to you.
 Real power to communicate
The core platform gives you unrivaled power efficiency to use the web and communicate using the super-fast browsing
experience, built-in video telephony and integrated social networking.
 Enhance your Symbian experience with applications
Browse the Symbian Horizon app directory and check out our partners' app stores where you'll find all the applications you
could ever need. We don't limit our developers, so you'll also find great content based on Adobe Flash, Microsoft
Silverlight, Qt, WRT and many other great technologies.

Inside a Symbian OS phone

Symbian OS phones are designed first and foremost to be good telephones, with quality voice calls and excellent

battery life. On top of that, Symbian OS phones are usually open platforms that provide opportunities for

interesting and novel software. Achieving these goals requires hardware designed specifically for the task, high

enough performance in the key use cases and an obsession for low power usage.

Looking into Symbian OS phone design, there are two complementary computing domains, the mobile radio

interface of the baseband processor (BP), also known as the modem, and the application processor (AP), which

runs the user interface and high-level code, under Symbian OS. Surrounding these domains is a collection of

peripherals that make up the product: battery, display, speakers, SIM card and more.

Figure 2.1 depicts a common two-chip solution, where the BP and the AP are self-contained systems, with a high

speed inter-processorcommunication (IPC) link between them. This is the preferred design for 3G phones, in which

each domain can re-use existing software and hardware sub-systems.

 Figure 2.1 A common two-chip solution

 1 Inside a Symbian OS phone

o 1.1 Baseband processor (BP)

o 1.2 Application processor (AP)

o 1.3 System-on-Chip (SoC)

o 1.4 Physical memory map

o 1.5 Central Processing Unit (CPU)

o 1.6 ARM

o 1.7 Memory Management Unit (MMU)

o 1.8 Caches

 1.8.1 Virtual and physical caches

 1.8.2 ARM v5 virtual cache

 1.8.3 ARM v6 physical cache

 1.8.4 Instruction cache (ICache)

 1.8.5 Data cache (DCache)

o 1.9 Random Access Memory (RAM)

 1.9.1 Mobile SDRAM
  1.9.2 Internal RAM (IRAM)

o 1.10 Flash memory

 1.10.1 NOR Flash

 1.10.2 NAND Flash

o 1.11 Interrupts

o 1.12 Timers

o 1.13 Direct Memory Access (DMA)

o 1.14 Liquid Crystal Display (LCD)

o 1.15 Audio

 1.15.1 Telephony audio

 1.15.2 Multimedia audio
1.16 Power management