An Open Ravenscar Real-Time Kernel for GNAT - DIT - Universidad ...

More documents

Recommendations

Info

objects. Interrupt handlers are executed in the context of the interrupt service tasks,which gives a clean execution model compared to other approaches in which the handleris executed in the context of the interrupted task.ORK follows a different approach. Under the Ravenscar profile restrictions onlyprotected procedure handlers can be defined. Moreover, the only possible locking policyis Ceiling Locking. This means that an interrupt handler can never be blocked waitingfor a protected object to become free. Since all interrupts are disabled while updatingthe kernel internal data (see 3.6 below), there is no need for complex mutual exclusionmechanisms. Actually, interrupt handlers are executed as if they were directly invokedby the interrupted task, with the difference that the interrupt stack is used instead of thetask stack.The Kernel.Interrupts package provides symbolic interrupt names and operationsfor attaching and detaching interrupt handlers. The handlers are directly attached to theinterrupts, without the burden of using POSIX signals as the current GNARL does.3.6 Other design issuesThe kernel interface is a purely procedural one, as there is no need for separate userand supervisor execution modes. All the program runs in supervisor mode, as it is commonin embedded systems. Mutual exclusion in the kernel is achieved by means of amonolithic monitor [15] protected by disabling interrupts, so that interrupt delivery ispostponed when a kernel function is executed [17, 16].Mutex lock operations are implemented by simply raising the locking thread activepriority to the ceiling priority of the mutex. This is consistent with the implementationproposed by the Ada Rationale [13] for protected objects.4 Related workThis project builds on some of the results of previous ESA projects which resulted inthe development of the current ERC32 GNU Cross Compilation system [10], whichincludes an Ada cross-compilation system for the ERC32 computer based on GNATand RTEMS, an open real-time operating system.The JTK kernel, which was developed at the Technical University of Madrid, [7,17], has provided some background for the development of ORK. We have also beeninspired by the Top Layer kernel [14].Other previous work of interest to the project includes Aonix’ Raven [8], and thekernels developed at the Florida State University [19, 18] and the University of York[20].5 Status and availabilityThe first version of the kernel has been fully implemented, and is available at the ORKproject server, www.openravenscar.org. The distribution package includes sourcepatches for the GNAT 3.13 runtime library, and GDB scripts, in addition to the kernelitself.
ORK is free software, and is distributed with the same license as GNAT (a slightlymodified GNU Public License). This means that everybody is free to read the ORKsource code, modify it, and redistribute it, provided they give others the same freedom.ORK is currently maintained on a voluntary basis for the general public.6 Conclusions and future workORK has been designed to provide an open source implementation of the Ravenscarprofile. Although the ORK project is primarily targeted to the on-board space softwaredomain, we expect that it will be useful to the hard real-time systems community atlarge.We plan to port ORK to other hardware platforms, starting with the ix86 PC compatiblearchitecture, in the near future. This will enable it to be used in other applicationdomains, and also in real-time systems education.AcknowledgmentsORK was developed by a team of the Department of Telematics Engineering TechnicalUniversity of Madrid (DIT/UPM), lead by Juan Antonio de la Puente. The other membersof the team were Juan Zamorano, José F. Ruiz, Ramón Fernández, and RodrigoGarcía. Alejandro Alonso and Ángel Álvarez acted as document and code reviewers,and contributed to the technical discussions with many fruitful comments and suggestions.The same team developed the adapted packages that enable GNAT to work withORK.GDB was adapted to ORK by a Jesús González-Barahona, Vicente Matellán, AndrésArias, and Juan Manuel Dodero. José Centeno and Pedro de las Heras acted asreviewers for this part of the work. All of them work at the King Juan Carlos Universityof Madrid.The ORK software was validated by Jesús Borruel and Juan Carlos Morcuende,from Construcciones Aeronáuticas (CASA), Space Division. We also relied very muchon Andy Wellings and Alan Burns, of York University, for reviewing and discussionsabout the Ravenscar profile and its implementation.ORK was developed under contract with ESA, the European Space Agency. JorgeAmador, Tullio Vardanega and Jean-Loup Terraillon provided many positive criticismand contributed the user’s view during the development. The project was carried outfrom September, 1999 to early June, 2000.References1. Ada Core Technologies. GNAT Reference Manual. Version 3.13a, March 2000.2. Ada 95 Reference Manual: Language and Standard Libraries. International StandardANSI/ISO/IEC-8652:1995, 1995. Available from Springer-Verlag, LNCS no. 1246.3. Lars Asplund, Bob Johnson, and Kristina Lundqvist. Session summary: The Ravenscarprofile and implementation issues. Ada Letters, XIX(25):12–14, 1999. Proceedings of the9th International Real-Time Ada Workshop.
Page 6 and 7: Only the first four of these packag
Page 10: 4. Ted Baker and Tullio Vardanega.

An Open Ravenscar Real-Time Kernel for GNAT - DIT - Universidad ...

Create successful ePaper yourself

Delete template?

Save as template?