ARTS: a distributed real-time kernel
ACM SIGOPS Operating Systems Review
The Spring kernel: a new paradigm for real-time operating systems
ACM SIGOPS Operating Systems Review
The MARUTI hard real-time operating system
ACM SIGOPS Operating Systems Review
The real-time operating system of MARS
ACM SIGOPS Operating Systems Review
Object oriented design with applications
Object oriented design with applications
Workshop on integrated approach for fault tolerance-current state and future requirements
ACM SIGOPS Operating Systems Review
Fault Tolerance: Principles and Practice
Fault Tolerance: Principles and Practice
| Hi-index | 0.00 |
Increases in hardware availability and capability have caused microprocessor based real-time embedded systems to become increasingly pervasive [8,9]. With this popularity, however, has come an increase in the size and complexity of embedded applications. Dealing with this complexity typically involves runtime support for interprocess communication and synchronization, memory sharing, device management [9], and, less typically, for error recovery and debugging [4,8]. Most real-time embedded operating systems provide this support through an interface consisting of a complex collection of subroutine calls. Basing this interface on an object-oriented model provides encapsulation and extensibility features to the application programmer. Although some work has been done using this approach, those systems generally use proprietary languages (e.g. ARTS) and are too large to be used in embedded systems [9].This paper describes a high level object-oriented design for a real-time embedded operating system, called EOS, and for the EOS application program interface. EOS is intended to be compact enough to be used in embedded systems, yet provide standard capabilities such as message handling, memory sharing, device management, and direct support for error tracking and recovery.