Version 4 (modified by Saeed Ehteshamifar, on Jun 15, 2016 at 2:17:19 PM) (diff)


Fault injection

Mentors: Joel Sherrill

Students: Past, Present, and Potential Students

Status: Initialized. More at SOCIS' wiki page

Introduction: Introduce the main concepts around the project: Theoretical preliminaries, preexisting RTEMS capabilities used or augmented (if any), important concepts, problems/needs the project will try to solve/satisfy.

Goal: Help users get RTEMS certified to meet their needs:

  1. project deliverables (code, docs, testing),

Code: python script to run fault-injection tool to acheive same testing goals as:

Docs: Wiki page and README for how to run the tool

Testing: the student's work will be evaluated on whether following the directions on the README and wiki produces the desired test results.

  1. required/suggested methodology

Use an existing free and open software

Use python to invoke it correctly.

  1. standards of quality,

Runs an Linux and Windows...

Produces a report like

  1. possible goal extensions beyond the main objective.

Have the out-put go into a web-page format

  • Relevant failures: NOT Most of the report is junk failures. They configure their test

case with more objects than fit into memory and the BSP locked up about 3 lines into the C code. They wrote this failure up more than 1000 times.

  • By directory or by capability reporting... smaller pieces that are easier to analayze

Requirements: List the requirements and level of expertise you estimate are required by the developer tackling this project will have to have: Required level of programming language(s), specific areas of RTEMS or tools, level of familiarity with RTEMS, cross-development, GNU/Linux, etx., development/documentation/testing tools, mathematical/algorithmic background, other desirable skills.

Resources: Current RTEMS developers, papers, etc that may help you in this project.


  • who helped and did work

Miscellaneous Sections

As the project progresses, you will need to add build instructions, etc and this page will evolve from a project description into a HOWTO.


Other sections: If you have more to say about the project that doesn't fit in the proposed sections of this template, feel free to add other sections at will.