Version 44 (modified by Gedare, on Apr 18, 2013 at 1:20:20 AM) (diff)


RTEMS is a participating organization of the Google Summer of Code 2013! Please use this page as a jumping off point and ask questions. We want you to be a part of the RTEMS community!

Imported from old wiki.

Potential Students: Read through all the material on this page, and be sure to add yourself to the table in the Student Information section. Remember to fill out an official GSOC application in addition to the informal application we request. We also require you build RTEMS, create an application, run it and post the result to the RTEMS mailing list. The Configure and Build RTEMS page has the details on how you do this. Information on what to post are found on the Prove You Can Work On RTEMS page. For new comers to RTEMS we recommend you use a proven Virtual Machine image.

Potential Mentors: Share your knowledge and pledge to help a student. Visit the [1] URL for GSoC 2012 to register as a mentor and then add yourself to the list of RTEMS Mentors.


Information for prior years:

In 2012, we had ten students. In 2011 and **NAME** 2010?, we had eight students each year. In 2009 there were six students with a seventh sponsored by a combination the mentor donation and a donation from OAR Corporation,. In our first GSOC experience, 2008 we received four student slots with one failing. These students have contributed great code and some have continued to be a part of the community. We have been impressed with the quality of both high school and college students who have participated in the GSOC and GCI programs.


Google Code-In has been an incredibly challenging experience for the RTEMS Community. The tasks are much smaller that those in GSOC with a target of 2-4 hours for a skilled developer. Plus they should be achievable by a high school student and meaningful to the community. We gathered some statistics to give an idea of the magnitude of what they accomplished.

{| border="1" style="margin: 1em auto 1em auto;text-align: center;" |+

|Year | 2011 | 2012
Students Tasks Tasks By Top Student Students with Over Ten Tasks
22 65 12 1
31 245 61 4


The increase in tasks performed is likely due to just ten free software organizations participating in the 2012 edition (twenty in 2011) combined with our improved ability to define tasks which students could perform.


General Information

General Program Information and Guidance

RTEMS Specific Information

  • Fedora 14 RTEMS 4.10 and 4.11 Virtual Machines? are pre-configured RTEMS development environment on Fedora 14. They are virtual machines playable with VirtualBox. For students who do not have a dedicated Fedora 14 installation, this is a great way to work with RTEMS with a minimum of pain and setup.

Be sure to add yourself to the table below.

Project Ideas

Open Projects contains the open projects list for RTEMS. It is by no means an all inclusive list and we are open to suggestions. Submissions of ports to new architectures, new BSPs, new device drivers, and test improvements are always welcomed.

Student Information

SoC Project Management

Visit Open Projects to find an interesting project, or propose your own! Ask about your project idea on the email list or IRC. The project descriptions often require additional knowledge to flesh out a project proposal.

We want you to hit the ground running, so you need to build RTEMS, modify it a little, and run samples as a prerequisite. Please visit the RTEMS GSoC Getting Started page for details.

RTEMS is an operating system targeting embedded systems that are cross-compiled, meaning that you develop on a host system and run programs on a target system. In general, students working on code require no special hardware, because RTEMS runs on simulators like gdb, skyeye, and qemu. The development can all be done and tested using a GNU/Linux or other suitable host.

RTEMS is designed to operate under tight resource restrictions. Some of the projects focus on breaking existing linkages between subsystems so those limits can be lowered further, or to help RTEMS fit into smaller systems.

Even though it is targeted to embedded systems, developers still expect as many features as possible. RTEMS provides a robust set of POSIX primitives and what is now known as the Classic API which provides hard real-time functionality. Some of the projects are focused on implementing a few missing pieces of POSIX functionality.

Not all of the projects necessarily run RTEMS or target an embedded system. Some of the projects are focused on improving the development experience by improving developer tools and environments.


Students Proposals

The final version of your proposal must be submitted via Melange at Google. We have provided a Google Docs template for the Student Proposal. Feel free to copy it and invite potential mentors to review. Please be aware that this is NOT the official form to submit your proposal on. Your official application must be submitted through the GSOC Melange system. Periodically copy and paste your proposal into the student application form and save it in Melange to avoid any last minute problems. Until then, please use Google Docs and put the link in this table. That way any mentor or RTEMS community member can request access and comment on your proposal. Students.. please don't peek at each other. :)


{| border="1" style="margin: 1em auto 1em auto;text-align: center;" |+

|Student |NAME |Jin Yang |Prateek Tiwari |Hesham ALmatary |Deng Hengyi
Completed Hello IRC Handle Proposal Title Google Docs URL
Yes or No on #rtems Title Link to Google Docs for proposal |
Yes SYCrane CAN driver and API for CAN stack Proposal
Yes prateekt Supercore Scheduler Link to Google Docs for proposal |
Yes Hesham Enhance low-level API of libmm (Memory Protection & Caches) Link to Google Docs for proposal | Proposal
Yes weiY Atomic Operations and SMP lock debug tool for RTEMS Link to Google Docs for proposal |


|Dhananjay Balan |Peng Fan |Shubham Somani
Yes dhananjay Better RTEMS Support in GDB Link to Google Docs for proposal |
Yes freenix Link to Google Docs for proposal |
Yes S_Somani Application Configuration GUI for RTEMS. Link to Google Docs for proposal |


|Philipp Eppelt
Yes phipse Paravirtualization of RTEMS


|Vipul Nayyar |Jaskaran Singh |Vivek Krishnamurthy |Ye Xu
Yes vipulnayyar Unified API
Yes |
Yes Vivekkmurthy
Yes AresHsu? |


The Student column is for your name.

The Completed Hello column lets us all know whether or not you completed the require Hello World project. Based upon our experience, students who have successfully compiled and run an RTEMS application have a MUCH MUCH higher chance of success on the proposed project.

The IRC Handle column is your handle on IRC. RTEMS folks hang out in #rtems on

The Proposal Title should be self-explanatory. If approved, we will ask you to create a project to host your work and link to it here. You will need to give at least your mentor and Joel Sherrill? read/write access.

The Google Docs URL is your proposal in Google Docs that can be reviewed and commented on by mentors.

RTEMS Mentors

See our RTEMS Mentors page for a list of potential project mentors.

Attachments (1)

Download all attachments as: .zip