Overview
FrançaisABSTRACT
The fundamental purpose of the operating systems (OS) is to provide application services enabling the transparency of resource sharing and access to material. A large number of equipment buries circuits containing one or more processors and specialized coprocessors. These circuits are highly constrained in terms of surface and computing power, and for which the tasks to be performed being at least partially known in advance, require the use of an operating system, even minimalist. Thus, to treat a continuous stream of data or run programs, the OS can be specialized, simplifying the code and maximizing the performance.
Read this article from a comprehensive knowledge base, updated and supplemented with articles reviewed by scientific committees.
Read the articleAUTHOR
-
Frédéric Pétrot: Doctor of Science from Pierre et Marie Curie University (Paris VI) - Professor at Ensimag, Grenoble Polytechnic Institute
INTRODUCTION
Embedded and/or integrated systems are in some ways reminiscent of the computers of yesteryear, with their limited resources. This leads to a need for code compactness and optimized use of hardware, which is no longer the case in today's computer systems, where abundant computing and memory resources are the rule. However, let there be no mistake: comparison is not reason, and today's embedded computer systems are often far more powerful than their non-embedded predecessors, but they are also extremely constrained, and the few kilobytes, microseconds or milliwatts that are saved by an ad hoc operating system will always be useful to the application, enabling a device to operate better, safer and longer. Overall, the aim of an operating system is to abstract and share hardware resources to simplify application writing. Modern computer operating systems aim to optimize the user's average response time to a keyboard and mouse, even if this means requiring many resources at any given time to guarantee this objective. In the embedded world, such an objective often makes no sense, as there is no user to speak of, and the rather subjective and poorly formalized notion of acceptable response time is clearly inadequate. Operating systems for embedded systems generally need clearly specified constraints to realize the services they are supposed to provide. These criteria can be related to time performance, for example minimum and maximum interrupt processing latency, maximum memory space requirements, hardware control capacity with a view to low power consumption, and so on. Systems in which an action must be carried out within a predefined period of time, potentially repeatedly, are known as real-time systems. This is particularly important in the embedded world, where controlling the triggering of an air bag or the decoding of a video is only of interest if the action is carried out within the allotted time.
In addition, operating system construction methods have evolved over time, and today only include those parts that are useful both to the application - if this is known in advance, which is often the case - and to the hardware. This allows us to build a "tailor-made" system that maximizes the device's efficiency. As integration poses crucial questions of efficiency and flexibility, integrated systems currently being designed tend to include several (or even many) processors. The management of these many processors, which may be of the same or different types - for example, a general-purpose processor and a signal-processing processor - clearly has an impact on the operating systems intended for on-board use.
Most of today's embedded applications use algorithms that are very demanding in terms of memory resources and computing capacity. As a result, embedded electronic...
Exclusive to subscribers. 97% yet to be discovered!
You do not have access to this resource.
Click here to request your free trial access!
Already subscribed? Log in!
The Ultimate Scientific and Technical Reference
This article is included in
Traceability
This offer includes:
Knowledge Base
Updated and enriched with articles validated by our scientific committees
Services
A set of exclusive tools to complement the resources
Practical Path
Operational and didactic, to guarantee the acquisition of transversal skills
Doc & Quiz
Interactive articles with quizzes, for constructive reading
Embedded OS
Bibliography
Software tools
Google. Android http://developer.android.com/index.html
DSpace, Inc. dSpace. http://www.dspaceinc.com.
The Mathworks. Real-Time Workshop. http://www.mathworks.com/products/rtw/
...Websites
REEVES Glenn, "What really happened on Mars?", http://research.microsoft.com/en-us/um/people/mbj/Mars_Pathfinder/Authoritative_Account.html
...Events
Symposium on Operating Systems Design and Implementation, biannual (even-numbered years) leading symposium on operating systems, including OS for embedded systems, sponsored by USENIX and ACM.
International Conference on Architectural Support for Programming Languages and Operating Systems, a leading OS conference sponsored by the ACM.
Embedded Linux Conference, annual conference...
Standards and norms
- Standard Test Access Port and Boundary-Scan Architecture, IEEE Std. 1149.1-1990. - IEEE -
- Functional Safety of Electrical / Electronic / Programmable Electronic Safety-related Systems, IEC 61508-1998, International Electrotechnical Commission. - IEC -
Exclusive to subscribers. 97% yet to be discovered!
You do not have access to this resource.
Click here to request your free trial access!
Already subscribed? Log in!
The Ultimate Scientific and Technical Reference