= Open Projects = Welcome [wiki:GSoC Summer of Code (SOC)] Students and hackers. Peruse our projects, and if you have questions ask on the [wiki:TBR/Website/RTEMSMailingLists RTEMS mailing list] or [wiki:Developer/IRC IRC]. If you plan to submit a proposal to do something for the RTEMS Project as part of a SOC, see [wiki:GSoC/GettingStarted Getting Started for SoC Students] for our SOC getting started guide. RTEMS projects span kernel hacking, adding support for a new board (BSP), improving the development environment, developing tests, and more. If you are looking to get your feet wet with RTEMS then check out our [wiki:Small_Projects_ small projects page] where you can find projects that require little coding skill and are appropriate for those new to RTEMS or open source software projects. If you are interested in one of these projects but are not able to code and test it yourself, consider sponsoring one of the core RTEMS developers to do it for you. Volunteering or sponsoring is how things get done -- users keep RTEMS development alive! [[TOC(Developer/OpenProjects, depth=2)]] = Overview = Most of these projects will take between a few weeks and a few months of effort by a person who is familiar with the general use of GNU/Linux and GNU tools. Many RTEMS projects are done as student or volunteer efforts, so we try to define small projects or subtasks that can be completed and committed individually. Most of the projects are feasible as a [wiki:GSoC Summer of Code] project. Since some projects have multiple steps, students should work with prospective mentors to define the scope of work in their proposal. Similarly, some projects might be a starting point for a class project or graduate thesis. The order of projects in the list does not reflect their importance, difficulty, or feasibility. Our project list is not exclusive: if you have an idea, solicit feedback from the project's [wiki:TBR/Website/RTEMSMailingLists mailing list] or [wiki:Developer/IRC IRC channel]; many developers sit in IRC and check it (and their email) infrequently throughout the day, so be patient! '''If you have a new project add it to the appropriate list below, link to a wiki page that follows the recommended [wiki:TBR/Review/OpenProjectTemplate Open Project Template], and briefly (1-2 sentences) summarize the project and how it will improve RTEMS.''' = High Priority Projects = These projects have generated a lot of interest from users and are greatly desired. These are large or ongoing projects, so definitely ask for help defining the scope of work before proposing to do any of these projects. * [wiki:SMP_ Improvements to SMP support] - Multiprocessing is of increasing importance in modern systems and we want RTEMS to remain competitive and useful. This is a large project and subtasks should be identified before writing any proposal. * Implement or integrate [wiki:Projects/GSoC/Atomic_Operations Atomic Operations]. SMP code requires additional synchronization primitives that are not available currently in RTEMS. * [wiki:RTEMS_Test_Coverage Test Coverage Analysis] - Improve coverage by adding more test cases. Eliminating dead code and reaching 100% coverage helps reduce the likelihood of new and recurrent bugs. * [wiki:Projects/TCP/IP_update Update the RTEMS TCP/IP stack] - The networking stack is old and showing it. This project actively underway. At a high level, this effort requires porting the TCP/IP stack and providing support functional equivalents of multiple BSD kernel constructs. This project has many subprojects many of which are appropriate for SOC. It would be of great usefulness to the community to get as many of these does as an SOC project as possible. * RTEMS Toolkits - We are defining collections of libraries and support programs which make it easier to get started for certain types of applications. We haven't identified all potential toolkits or components. Each potential component must be evaluated for license and appropriateness for use in an embedded environment like RTEMS. We also should define some guidelines about creating and maintaining these kits. Here are the toolkits areas identified so far: * [wiki:Projects/BenchmarkKit RTEMS BenchKit] - benchmark programs for RTEMS * [wiki:Projects/ApplicationConfigurationKit RTEMS ConfigKit] - configuration file parsing libraries * [wiki:Projects/DatabaseKit RTEMS DBKit] - database packages * [wiki:Projects/GraphicsToolkit RTEMSGraphicsToolkit] - various graphics and video processing. This kit has had some work done on it. * [wiki:Projects/ScienceKit RTEMS SciKit] - libraries of general use to the scientific community RTEMS users * [wiki:Projects/ScriptKit RTEMS ScriptKit] - packages for scripting languages such as Python and Lua * [wiki:Projects/WebKit RTEMS WebKit] - packages for networked devices. = Testing = Testing a large body of software like RTEMS is in a continual state of improvement. There is always a need for more test cases and easier ways to run them all and decode the results. In addition, we want to be able to run all tests on as many hardware and simulator configurations as possible. Testing doesn't sound exciting to most people but when you combine the breadth of what we need to test with our desire for 100% instruction and branch path coverage, you get some very interesting and challenging work. Some of the identified activities which would augment our testing capabilities are listed here: * [wiki:Projects/TestingImprovements RTEMS Testing]. Testing for RTEMS, including Unit, Regression operational and building a custom test harness. No prior knowledge of software testing is required. * [wiki:RTEMS_Test_Coverage Test Coverage Analysis] - Improve coverage by adding more test cases. Eliminating dead code and reaching 100% coverage helps reduce the likelihood of new and recurrent bugs. * Test the [wiki:Projects/POSIXFIFOs POSIX FIFO Implementation]. * [wiki:RTEMSgprof_ Add support for gprof output to covoar] * Improve [wiki:Projects/GNUToolsTesting Testing of the GNU Tools] on RTEMS targets = Development Environment Oriented = RTEMS applications are cross-compiled on a development host to produce executables that are transferred to and executed on target systems. The projects in this section focus on the host side of that equation. This means they will run on a developer's computer and possibly communicate with embedded hardware. The following areas have been identified for projects related to improving RTEMS development: * Improvements in the [wiki:Developer/Eclipse/Information RTEMS Eclipse Integration] * Implement a cross-platform [wiki:Projects/GSoC/ApplicationConfigurationGUI Application Configuration GUI]. * Integration of RTEMS cross development environment into [wiki:Projects/EVisualStudio eVisual Studio] * [wiki:Projects/ArgoUML ArgoUML RTEMS Support] * [wiki:Projects/GDB_Python GDB Python] Script support for RTEMS * Scripts and documentation for creating and installing prebuilt tool packages: * [wiki:Building/RPM_Packages Building Tool RPM Packages] * [wiki:Building/DebianHostedTools Debian Packages] * [wiki:TBR/Delete/MacOSHostedTools MacOS tools] * [wiki:TBR/UserManual/MinGW_Tools_for_Windows MinGW Tools for Windows] * Two open areas are a 1. minGW build-script, and 2. updating the NSIS installer [http://wiki.rtems.org/wiki/index.php/BuildingMingwTools How to run NSIS on RTEMS scripts] and [http://wiki.rtems.org/wiki/index.php/Installing_MinGW_RTEMS_Tools running the NSIS installer] * Improvements to the [wiki:TBR/UserManual/RTEMS_Source_Builder RTEMS Source Builder] such as building host tools, building a GUI, and improving configuration management and creation. = RTEMS Run-Time Oriented = The projects in this category are more focused on the development of software that runs on RTEMS on target hardware. = Run-Time Projects Not Initiated = The following projects have no work on them. * Unified Interrupt and PCI APIs -- [wiki:UnifiedAPIs UnifiedAPIs] * RTEMS can always use [wiki:TBR/Delete/MoreBSPsForSimulators more BSPs for Simulators]. Being able to test, debug, and perform coverage analysis on simulators is critical to the ongoing success of the project. * Identify and implement the functionality currently missing in ''dup()'' * Implement a [wiki:Projects/Open/LineEditor Simple Line Editor]. Existing code can be refactored for starting point. * [wiki:Projects/SystemEvents RTEMS System Events] is a project to add a first class object for events. Currently all event sets are tied to a specific thread. * Implement OSEK Support [http://portal.osek-vdx.org/] * Port Transparent IPC (http://tipc.sourceforge.net/index.html) to RTEMS * Support for new Processor Families - Xtensa, Microblaze * Add cache manager support for architectures not having it. * Investigate the feasibility of implementing applicable sections of the [http://en.wikipedia.org/wiki/IEC_61131 IEC 61131] standard to enable RTEMS-enabled hardware to act as a [http://en.wikipedia.org/wiki/Programmable_logic_controller Programmable Logic Controller]. More information on the IEC 61131 standard can be found at http://www.plcopen.org/ . [http://www.beremiz.org/] is an open source framework for automation that may be a useful starting point. * [wiki:Projects/GSoC/Bdbuf_improvements Bdbuf improvements]. The current block device buffer implementation can benefit from a number of improvements. * ARINC653 API support within RTEMS [wiki:Projects/GSoC/ARINC653API ARINC653API] = Run-Time Projects With Some Work = The following projects have had some work on them but are not complete. Ask about the current progress on the mailing list. The remaining activities could be large or small: * [wiki:Projects/TinyRTEMS TinyRTEMS] is an umbrella term that corresponds to any activities or ideas that could shrink the code and data space requirements for RTEMS. The goal is to progressively lower the minimum CPU requirements. * Improve the RTEMS [wiki:SuperCore_Scheduler_ SuperCore Scheduler] - near complete * more [wiki:TBR/Delete/Libbsd-port NIC device drivers] = Third Party Packages = This is a list of projects related to third party free and open source software and its support for RTEMS. The following project areas have been identified: * Compiling RTEMS with [wiki:Projects/CLANG CLANG]. * Integrate [wiki:Projects/CEXP CEXP] into main RTEMS distribution. * [wiki:Projects/Mono Mono On RTEMS] * Turn the current port of [wiki:Packages/LWIP LWIP] into a first class citizen. Submit port, make target independent, etc. * [wiki:TBR/Delete/IDL_COM IDL/COM] Support for RTEMS. = Projects Whose Page Need Updating = The following projects have been worked on and the pages require updating. There may or may not be enough work remaining to constitute an SOC project; many of these are past SOC projects. If you are interested in one of these, please ask on the mailing list or IRC. * [wiki:RTEMS_Paravirtualization_ Paravirtualization] of RTEMS to make it suitable to be run as a guest OS in a hypervisor. * [wiki:MMU_Support_ MMU Support] for RTEMS. * Use [wiki:UseHashOrMapInNotepadsAndKeys_ Maps or Hashes] in the implementation of Classic API Notepads and POSIX API Keys. * Implement [wiki:POSIX_Asynchronous_IO_ POSIX Asynchronous and List IO] * [wiki:RTEMS_Trace_Tool_ Run-Time Tracing] - includes gathering, capturing, and displaying information to the user. * [wiki:Projects/SequencedInitialization RTEMS Sequenced Initialization] is a project to allow RTEMS initialization to be dynamically constructed based upon user requirements. It would be like C++ global constructors conceptually. * [wiki:Projects/libdl Dynamic Object File Loading] lets a base application with RTEMS dynamically load the rest of the application. The dynamic parts can be optional features and never loaded, or upgraded replacements for parts of the application. * [wiki:TBR/UserManual/USBStack port BSD USB stack] * [wiki:Projects/Parrot Parrot On RTEMS] * RTEMS port of [wiki:Projects/GCCGoRTEMS GNU GCC Go] * [wiki:Testing/Filesystem File System Test Suite] * [wiki:TBR/Delete/POSIXTimingTests POSIX Timing Tests] * [wiki:GSoC/2011/ISO9660_Filesystem ISO9660 file system] * RTEMS port of the [wiki:Projects/GNUJavaCompiler GNU Java Compiler (gjc)] * Add [wiki:RTEMSgcov_ support for gcov output] to covoar so tools like gcov and lcov can be used with RTEMS ([wiki:Projects/GCOVSupport another page here]) * [wiki:Projects/POSIXComplianceTestSuite POSIX Compliance Test Suite] * [wiki:Projects/SixtyFourBitTimestamps Sixty-Four Bit Timestamps] * [wiki:Projects/Refactor_the_filesystem_infrastructure Refactor the filesystem infrastructure] = Obsolete Projects = Some projects have been proposed that are viewed as being of minor use. This list is meant to provide a way to avoid wasted effort on projects that are not widely desired. However, projects on this list might still be useful to someone, given a motivated individual to work on them. * Various ideas have been proposed related to using RTEMS as a [[RTEMSHyperVisor | hypervisor]]. The lack of protected (kernel mode) execution precludes any feasible implementations. * Merge [[SimpleScalar | BSP for Simplescalar simulator]]. The BSP is heavily bit-rotted and the simulator is a dead project. * [http://code.google.com/p/rosetta-os Rosetta OS] [[RosettaOSDeviceDriverAPI| OS Independent Device Driver API]] * Implement current version of µITRON Interface [http://www.www.tron.org/index-e.html]. itron support was removed from RTEMS due to lack of interest.