Stand-Alone RTLinux
  OCERA Home  /  Download  /  Components  /  Scheduling  /  Stand-Alone RTLinux (2.0)
  Training and support
    POSIX Streams

  Resource management
    Generic Scheduler patch
    Preemption+RTLinux patch
    RTLinux API on Linux
    QoS Manager
    Linux/CBS Scheduler

  Scheduling
    Application Scheduler
    TLSF Memory Allocator
    POSIX CPU Clocks
    POSIX Barriers
    POSIX Message Queues
    POSIX Signals
    POSIX Timers
    POSIX Trace
    RTLinux/CBS Scheduler
    RTLinux CC
    GNAT for RTLinux
    RTLinux ide/fs
    RTLinux Java
    RTLinux Terminal
    RTLinux UDP/IP
    Stand-Alone RTLinux
    XtratuM

  Fault-tolerance
    FT Application Monitor
    FT Controller

  Communication
    CANopen device
    CAN/CANopen monitor
    Virtual CAN API
    RT Ethernet Analyzer
    Linux CAN Driver
    ORTE
    CAN model
    Verification of RTOS

Stand-Alone RTLinux

   Description
Keywords: RTLinux Porting
Description: Stand-Alone RTLinux will be a Linux independent implementation of RTLinux. Stand-Alone RTLinux will be a bootable executive with the following main features: a) Low memory overhead. The core systems contains only following modules: the code of RTLinux, the minimum code needed to boot the system and basic virtual memory management. b) Scalability. Users will be able to customize RTLinux funcionalities to reduce kernel memory usage. c) Porting will be possible to systems without hardware for virtual memory support. Therefore, Stand-Alone RTLinux could be ported to a wider range of architectures. d) Less TLB and memory cache misses (or none at all, if paging is not activated) since only real-time applications are being executed. e) We are not longer limited by the Linux memory manager. Standard RTLinux memory management relays completely on the Linux so it is not possible to implement custom virtual memory management algorithms. Stand-Alone RTLinux has full control of the MMU. Current implementation provides three different memory schemes: 1.- Non protected memory. RTLinux executive and application can read and write at any memory location. 2.- Simple memory protection. The application can not write into the RTLinux executive memory space, and null pointers are catched. 3.- Context memory protection: Several applications (each application can run one or more threads) are executed in a protected memory space. Each aplication can read and write its own data but only read system and other applications code and data.
   General information
Author(s): Vicente Esteve (UPVLC)
Participants: Universidad Politecnica de Valencia
Workpackage: Development of real-time scheduling components (WP5)
Deliverable: Component documentation can be found in deliverable D5.4
Component homepage: http://www.ocera.org
Licenses: MPL, GPL, LGPL and CeCILL (Multiple license issues)
Current version: 2.0
Status: Stable
Hardware:
Processor: i386
Platform:
RTLinux: 3.1
   Download
Current version: 2.0 [sa-rtl-2.0.tgz] [src] [CVS at SourceForge]
Note: This component can be used outside of the OCERA framework.

 Status codes: Analysis >> Design >> Alpha >> Beta >> Testing >> Stable

© OCERA Project. webmaster@ocera.org
Maintained by: Sergio Sáez   Last update: Wed Jan 10 16:56:57 2007