Version 2 (modified by JoelSherrill, on Mar 25, 2009 at 4:43:16 AM) (diff)

Small Projects

This page contains projects which can easily be tackled by someone new to RTEMS.

No Coding Required

The following requires no coding although it may help to be able to read C code:

  • Improve the Wiki pages for the various BSPs
    • There are approximately 100 boards supported by RTEMS. Each board has a page in the Wiki and there is an standard Wiki Infobox. Most BSPs still do not have any information here, links to vendor information, or even a good description of the board. This effort just requires a bit of web research and Wiki editing.
  • Flesh out our POSIX API User's Guide
    • RTEMS supports the POSIX 1003 standard following the "single process, multi-threaded" profile. We have permission from The Open Group and IEEE to excerpt text from their standards (available online) for use in this manual if cited. This manual is in the doc/posix_users directory in the source tree and by looking at it, I am sure you can find something that needs to be written. The corresponding code is in cpukit/posix or cpukit/libcsupport.

Modest Coding Required

The following require only modest coding experience. Remember you can test RTEMS on a simulator so no special hardware is required.

  • Doxygen markup
    • RTEMS predates Doxygen and thus our .h files were not created with Doxygen markup. We have added this to a lot of files but would eventually like to see it in the score, rtems, posix, libcsupport, and libfs subdirectories of cpukit. In much of the code, the information is there but not in Doxygen markup format.
  • Writing test code
    • There is a continual need for more test code. We would like a timing test suite for the POSIX thread support that is comparable to the current Classic API timing test suite. We expect this will eventually comprise about 50 different tests so could be tackled as a class project with the individual tests assigned to different people or groups.