April 16, 2009 Center for Hybrid and Embedded Software Systems PtidyOS: An Operating System based on the PTIDES Programming Model sdfdsfsdfdsfdsfds Methodology Preliminary Results Discussion and Future Work References Shanna-Shaye Forbes Jia Zou Slobodan Matic Edward A. Lee / PTIDES - Programming Temporally Integrated Distributed Embedded Systems is based on Discrete-Event model of computation. PTIDES relates model time to physical time at specific points in the system and leverages time synchronization across distributed platforms. PtidyOS -a lightweight operating system aimed at distributed real- time embedded systems. Our approach combines PTIDES semantics with traditional scheduling methods. The first implementation leverages EDF scheduling scheme and guarantees correct event order defined by PTIDES. This is achieved without requiring totally ordered event processing. We describe a preliminary implementation on an ARM based microcontroller. PtidyOS is still under development. Preliminary results indicate that out-of- order execution can satisfy timing requirements at the millisecond level, however there are still some unanswered questions. 1.Does the ability to process events out-of-order save you any time, or does the overhead associated with it equal to or greater than a standard RTOS? Future Work: Extending causality analysis to more complex models and using a code generation framework to generate code for PtidyOS automatically. Driver support for PtidyOS, including support for protocol stacks to enable IEEE 1588 to use in a distributed real-time system. Enabling hibernation for power saving model. [1] J. Zou, S. Matic, E. A. Lee, T. H. Feng, and P. Derler. “Execution strategies for PTIDES, a programming model for distributed embedded systems”. 15th IEEE Real-Time and Embedded Technology and Applications Symposium, April, [2] [3] J. C. Eidson. Recent Advances in IEEE 1588., July Is a library linked against application C code. Steps away from threading model Current implementation uses a Single Stack* Introduction PTIDES defines a “safe to process” analysis for events within the system. By relating timestamps of events to physical time of the system, and by leveraging time synchronization across multiple platforms, an event can be determined to be “safe to process” by comparing the timestamp of the event to current physical time. Which platform is PtidyOS running on? Figure 3: High level block diagram of Cortex-M3 Luminary board Figure 2: A simple PTIDES model[1] Cortex-M3 ARM 7 32-bit processor Hardware assistance for IEEE 1588 [3] PTP. Ethernet, CAN, PWM support Reentrant Interrupts with stack manipulation Microkernel Scheduling Combines PTIDES semantics with traditional scheduling algorithms (for example Earliest-Deadline-First(EDF)). -- goal is to enable the user to specify which scheduling algorithm they wish to use. EDF is currently implemented. Memory Management -- No dynamic memory allocation. For events, seek time O(n), n is the number of events in the queue Multitasking -- All event processing is implemented within interrupt service routines. -- All interrupts are reentrant, interrupts do not have priority only events do. Event Processing Algorithm Sequence Diagram PtidyOS’s PTIDES implementation Implements the single event queue per platform version of PTIDES. Divides the local execution strategy into a safe to process analysis and local resource scheduling layer. PtidyOS at a glance *The use of a single stack and interrupts for mutual exclusion was done in TinyOS. PtidyOS uses these concepts and introduces time semantics. 100 Hz Blue, Model Delay1: 5ms WCET1: 1ms 10Hz red, Model Delay2: 50ms, WCET 2: 2ms Periods of both input signals: 5ms modelDelay1 = WCET: 0.5ms modelDelay2 = WCET: 1ms Merge WCET: 1ms Figure 5:Simple PTIDES Preemption Model Sensor-actuator edge-to-edge delays are exactly 5ms and 50ms. We saw a maximum jitter of 60usecs. Purple: Actuator invocations (output signals, given high priority) Red: Invocations of model delay and merge actors. In the diagram one actuation preempted the processing of a merge actor (purple pulse inside the red pulse). When given the same path delays there is no preemption because the absolute deadlines are different when the inputs occur after one another Work In Progress Sensor 1 Model Delay 1 Actuator 1 Sensor 2 Model Delay 2 Actuator 2 Sensor 1 Model Delay 1 Sensor 2 Model Delay 2 Merge Actuator Figure 1: A multi-platform PTIDES model Background Figure 4: Simple PTIDES Model To ensure event of highest priority is always processed first, interrupts play an important role: Event processing is done within Interrupt service routines Reentrant interrupts A PTIDES model is specified in C and causality analysis of the model is performed during system initialization.