RTEMSSummerOfCode

From RTEMSWiki

Jump to: navigation, search

Contents

http://code.google.com/soc

GSoC 2010 Top Page http://socghop.appspot.com/

RTEMS is happy that the Google will once again sponsor the Summer of Code in 2009. We plan to apply as an organization and hope we will be fortunate enough to be included again. Please use this page as a jumping off point and ask questions. The most important thing is becoming a part of the community and participating.

Potential Mentors: Share your knowledge and pledge to help a student. Go here to register as a mentor and then return here and add your name to our list.

Information for prior years:

General Information

General Program Information and Guidance

RTEMS Specific Information

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

Please visit Open Projects to see if you can find a project that interests you. If you have any questions about the projects, feel free to ask on the email list or use the Wiki Talk page feature. The project descriptions were usually written by someone with a high level of insight into the problem and will be happy to explain things in more detail to you.

This year we want you to be able to hit the ground running and are asking you to show that you can actually build RTEMS, modify it a little, and run samples. Please visit the GSoC Getting Started page for details.
  • Students working on code should require no special hardware. The development can all be done and tested using a GNU/Linux host (preferably RPM based). Between the simulators in gdb, skyeye, and qemu, there is plenty of simulated target hardware.
  • RTEMS is an operating system targeting embedded systems. All development is cross. Some of the projects are focused on improving the user development experience. Eclipse has proven popular for cross embedded development and one of the suggested projects is to bring those capabilities to RTEMS.
  • 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. Another area of effort is helping 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 in addition to an ITRON API 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.

References

  • Drupal has some information on the writing applications that looks promising

Students Proposals

The final version of your proposal must be submitted via Melange at Google. But 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. :)

Student Completed Hello IRC Handle Proposal Title Google Docs URL
NAME Yes or No on #rtems Title +

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 freenode.net.

The Proposal Title should be self-explanatory. If approved, we will ask you to create a code.google.com 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

This is probably not an all inclusive list of who has offered to be an RTEMS mentor.

  • Joel Sherrill - I am one of the original RTEMS developers and have been the project maintainer for over 10 years.
  • W. Eric Norum - I have been applying RTEMS to large experimental control system applications for over 8 years.
  • Chris Johns - I have been a user and developer of RTEMS for over 10 years.
  • Ralf Corsépius - I have been a user and developer of RTEMS for over 10 years and am the person providing the RTEMS toolchain rpms.
  • Alain Schaefer - I am a user of RTEMS for 1 year and have ported RTEMS to the bfin architecture. I volunteer to mentor for the Eclipse and the Configuration GUI
  • Thomas Doerfler - I have been a user and developer of RTEMS for about 8 years, mainly for industrial control units.
  • Ray Xu - I have been a user and developer of RTEMS for about 3 years in my spare time for fun. I volunteer to mentor project related to tinyRTEMS, skyeye, USB etc.
  • Alan Cudmore - I have been using RTEMS for satellite flight software applications for over 5 years. I volunteer to mentor for the Dynamic Loader project: I have experience with the vxWorks Dynamic Loader, the CEXP loader, and the posix dlopen() APIs.
  • Daron Chabot - I've been using RTEMS in data acquisition systems for about 5 years and I've also been an Eclipse user for about 1.5 years.
  • Aaron J. Grier - I have been using RTEMS for ~8 years to control audiological test equipment.
  • Peter Dufault - I've been doing real time work for many years, and with RTEMS for about 5 years in electric motor control systems. I'm particularly interested in control systems.

References

Retrieved from "http://rtems.org/wiki/index.php/RTEMSSummerOfCode"
Personal tools