12-04-2012, 11:04 AM
Real-Time Operating System and Embedded Development Environment
Real-Time Operating System and Embedded Development Environment.pdf (Size: 497.79 KB / Downloads: 65)
The OSE RTOS was designed from the
ground up to satisfy the requirement of
today’s complex and mission-critical
embedded systems. Originally developed
for the telecommunications industry
as a platform for delivering critical communications
services, it has been used in
millions of products worldwide for over
14 years. System designers focusing on
reliability, scalability, and simplicity are
increasingly making OSE their platform
of choice.
OSE is already a technical market leader.
The OSE RTOS was adopted by Ericsson
in 1988, by Nokia in 1990, and made
available throughout Europe in 1991.
OSE quickly became the preferred operating
system for high-availability applications
and distributed systems, especially
in telecommunications and wireless
systems. Today, OSE is at the core of
millions of cellular telephones, many
Internet infrastructure systems and other
devices.
Today’s real-time embedded systems are increasingly facing requirements considered cutting-edge only a few
years ago, such as supporting scalability across multiple CPUs, providing nonstop service under all conditions, and
running multiple communicating processes and applications.These complexities can increase costs, decrease reliability,
and extend time to market. A conventional Real-Time Operating System (RTOS) rapidly falls short when
asked to provide a foundation for the next generation of embedded applications. Designers of complex embedded
systems need a proven RTOS with the features to support the new generation of emerging systems.
THE OSE RTOS WAS DESIGNED FROM THE GROUND UP TO SATISFY
THE REQUIREMENT OF TODAY’S COMPLEX AND MISSION-CRITICAL
EMBEDDED SYSTEMS.
A conventional RTOS pushes much of the work to the application. The OSE RTOS has capabilities for
quickly and easily creating applications that operate at a higher level and execute reliably over their
lifetime. The OSE RTOS is a class above all others.
OSE
Real-Time Operating System and Embedded Development Environment
02
The OSE Architecture
OSE is a powerful platform for the
design of real-time embedded systems.
OSE’s message-based architecture instantly
and seamlessly achieves powerful
simplicity in complex, distributed
systems. OSE’s reliable process management
and dynamic runtime configuration
enable faster, more reliable system
deployment and maintenance. OSE’s
structured, multi-level facility for error
detection enables more efficient code
and more reliable and consistent exception
handling in the system. OSE also
includes built-in monitoring of critical
processes, alerting you before a software
failure brings down your entire system.
OSE makes it possible to develop highly
reliable applications in far less time. The
architecture is designed specifically to
meet the challenges of distributed and
fault-tolerant system designs.
At the heart of the OSE architecture is a
direct message-passing model that provides
fast, asynchronous interprocess
communication. Messages are allocated
from the OSE memory pool. Memory is
conserved and fragmentation is avoided.
OSE manages all of the details of buffer
ownership as messages are passed from
process to process, relieving the application
of this responsibility. As a result,
applications interoperate much more intuitively
and avoid many of the program
errors that result with other interprocess
communication models. This is the OSE
direct message-passing advantage.
OSE is the Leading RTOS for Use in High-Availability Designs
OSE was designed with a built-in capability
for creating service-critical, mission-
critical, and safety-critical systems.
This remains a central design feature in
OSE - not an afterthought. For example,
OSE has always supported essential concepts
such as user-supervisor and hardware-
enabled memory protection.
Rather than executing as a single process,
or multiple processes with no inherent
memory protection, OSE enables an
application to consist of a number of
distributed components. Each process
can be a separate object with its own
protected resources controlled entirely
by the kernel. An application written for
OSE can easily be divided into logical
parts, each independently designed and
coded, with communications between
them transparently managed by messages
passed across protection domain
boundaries. The result is high application
performance, while maintaining stability
and reliability across the entire
system. And OSE goes beyond supporting
these essential concepts with architecture
and specific mechanisms that
greatly enhance the system availability.
The deeper you look into OSE and compare
it to other offerings on the market,
the more you understand why developers
choose OSE when time to market
and high availability are critical.
OSE HAS BUILT-IN SUPERVISION MECHANISMS FOR MONITORING
CRITICAL PROCESSES…
OSE can put critical processes on a
watch list and automatically notify the
application, should a process be created
or killed. Applications can take action
before a fault becomes a fatal error.
OSE TRANSPARENTLY EXTENDS ITS MESSAGE-PASSING CONCEPT
ACROSS CPUs…
OSE’s unique Link Handler and Name
Server technology manages the transparent
connection of processes to services
regardless of their location. If one process
or an entire board fails, the software
can automatically reconnect clients and
their services without interruption to the
application.
“WE WANTED AN OPERATING SYSTEM THAT WAS FAST, ROBUST AND HAD STRONG MEMORY MANAGEMENT CAPABILITIES.
WE ALREADY KNEW THAT OSE FULFILLED ALL OF THESE CRITERIA MAKING THE RTOS A NATURAL FIRST CHOICE FOR US.”
Ericsson Licensing Technology
Messages are allocated from the OSE memory pool. Memory is conserved and fragmentation is
avoided. OSE manages all of the details of buffer ownership as messages are passed from process
to process, relieving the application of this responsibility.
03
OSE IS UNMATCHED IN ITS ABILITY TO SUPPORT DYNAMIC
SOFTWARE RECONFIGURATION…
Live software replacement is a reality
with OSE. New versions of programs can
be loaded onto the system and clients
can be redirected to the new instance at
any time. Recompiling, reloading, and
rebooting the system are no longer
necessary.
DESIGN ON A HIGHER LEVEL WITH OSE AND PROJECTS ARE
COMPLETED FASTER AND WITH FEWER ERRORS…
Developers who have not used OSE
have grown accustomed to referencing
through piles of manuals to learn the
low-level primitives found in most any
RTOS. OSE provides a rich set of services
and all of the standard APIs for those
services. OSE developers find that most
applications can be managed with just
eight powerful kernel APIs.
With OSE you design at a higher level,
creating applications that are easier to
write, understand, and maintain. This
has far-reaching benefits. Programmers
learn and master OSE faster than other
operating systems, make fewer mistakes,
and find errors more quickly. This
decreases development time and produces
code that is more readily reused.
Together with OSE’s automatic error
detection and built-in application-level
debugging, these features greatly enhance
productivity and quality.
OSE BUILDS IN AUTOMATIC ERROR DETECTION…
OSE has an advanced, built-in error
detection system. Should an error be
detected, OSE automatically invokes a
user-defined error handler specific to the
process, block, or system scope. This
simple-to-use, but powerful feature
replaces the complex code and inconsistencies
that often result when programmers
handle errors differently
throughout the application.
WITH OSE YOU CAN DEBUG AT THE APPLICATION LEVEL,
AN EASIER PLACE TO WORK…
OSE’s modern message-based concept
provides the basis for powerful application-
level debugging that is superior to
conventional operating systems.
Events, such as direct passing of specific
message types or context switching, can
be followed step by step, or traced in
real-time. Breakpoints can be placed on
these events to stop or monitor execution.
During distribution and non-stop
system debugging, selected parts of the
system can be stopped without interrupting
the entire system. This type of
debugging can also be applied to simulated
targets entirely on the host through
use of the OSE Soft Kernel.
The OSE Platform
The leading OSE real-time kernel is complimented
by a rich set of operating
system accessories to form a complete
fault-tolerant platform for embedded
computing.
LINK HANDLER
The unique OSE Link Handler connects
all system nodes and enables transparent
communication and supervision between
the applications running on each
node. With built in support for redundant
communication paths across
heterogeneous transports, OSE Link
Handler provides the reliable means for
connecting programs with services
across any computing cluster.
NAME SERVER
The OSE Name Server makes it easier to
design distributed systems. Connected to
the Link Handler, it enables applications
to call any process in a distributed
system using a unique process name
without knowledge of where the target
or the process resides.