Notice: We have migrated to GitLab launching 2024-05-01 see here:

Version 444 (modified by Chris Johns, on 02/06/17 at 04:26:39) (diff)

Use project as the ticket type.

Open Projects

Welcome! Whether you're here because of Summer of Code (SOC) or just want to scratch an itch to hack, we invite you to peruse our projects and ask about them on the RTEMS mailing list or IRC. If you plan to submit a proposal to do something for the RTEMS Project as part of a SOC, see Getting Started for SoC Students. RTEMS projects span kernel hacking, adding support for a new board (BSP), improving the development environment, developing tests, and more.

If you want to get your feet wet with RTEMS then check out our 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!

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 by student or volunteer coders, so we try to define small projects or subtasks that can be completed and committed individually. Most of the projects are feasible as a 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.

Projects in Bold text are higher priority simply meaning that users or developers have expressed a lot of interest in such projects. Projects in Italic text are space-oriented and therefore suitable for SOCIS.


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 mailing list or IRC channel; many developers sit in IRC and check it (and their email) infrequently throughout the day, so be patient! There may or may not be enough work on a project to constitute an SOC project, and some of these are past SOC projects. If you are interested in one of these, please ask on the mailing list or IRC.

If you have a new project add it to the appropriate list below, link to a wiki page below Projects/Open/ and use the Open Project Template. Briefly (1 sentence) summarize the project.

If one of the projects sounds interesting, but lacks detail, ask on an RTEMS mailing list for details and we can all help scope the project.

Help Convert to Tickets

We have started converting each of the projects listed here to tickets. Any help in the process is appreciated. A standard workflow for the same would be:

  • Create a new ticket (New Ticket(direct) in Trac).
  • The summary of the ticket should be the title of the open project.
  • The content of the project page should form the description of the ticket. May require WikiFormatting. (Perhaps it would be a good idea to just click on "Edit this page" down on the project's page and copy the already wikiformatted text.)
  • Put the "Type" of the ticket as "project"
  • Put the "milestone" to be "indefinite".
  • One of the mentors of the project should be mentioned in the "Owner" field and you should CC the rest of them. If no mentors are mentioned, keep the fields blank.
  • The "Keywords" field should be put to "SoC" denoting any Summer of Code RTEMS participates in.
  • We might want to use some other keywords e.g. to define the project type (e.g. one of: testing, ecosystem, kernel, statistics, BSP, API, libbsd, languages, libraries)
  • Add an appropriate "component"

If you are unsure about anything, ask on the mailing list.

The tickets are the newer and more relevant version of the content on the project's page. When in doubt, consider the description in the tickets as valid.


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:

Development Ecosystem

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:

RTEMS Run-Time Oriented

The projects in this category are more focused on the development of software that runs on RTEMS on target hardware.

Executive (SuperCore, SuperCoreCPU, libcpu): a.k.a. kernel

Runtime Statistics

Board Support Package (BSP)

Ticket Summary Owner
No tickets found

API Layers (POSIX, Classic, SAPI)



Libraries and Applications

Retired Projects

The following projects are complete or pending.

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.