The SIL2LinuxMP project aims at the certification of the base components of an embedded GNU/Linux RTOS running on a single-core or multi-core industrial COTS computer board. Base components are boot loader, root filesystem, Linux kernel and C library bindings to access the Linux kernel. With the exception of a minimal set of utilities (to inspect the system, manage files and start test procedures), user space applications are not included.

In general, various rules can be used when a system has to undergo certification for use in a safety-critical environment.

"Compliant development"

The most obvious certification rule is "compliant development" which means that the entire development process from the design and the first line of source code up to the final step of system building must follow the rules of the selected safety standard. Open Source is not developed this way – therefore, "compliant development" cannot be used for the Linux kernel.

"Proven in use"

Another, quite popular, rule is "proven in use". Unfortunately, this rule is far more popular than feasible, since the term "proven" only refers to a particular hardware and software version of a given system that must be monitored during a considerable amount of time. If even a slight detail of the system's hardware or software needs to be changed, data collection must be restarted. Thus, the procedure for "proven in use" is similarly expensive and time-consuming for conventional and Open Source projects. By no means can the Linux kernel be regarded as safe, simply because it is so widely used.

"Compliant non-compliant development"

A final rule that is less often used and only available in particular standards is "compliant non-compliant development". It often consists of two consecutive project periods of time. In the first period, arguments for a certain equivalence between the employed and a compliant development will be collected, and methods to supplement these arguments will be developed where required. In a subsequent period, the developed material and methods will be applied to individually specified hardware and software components. In addition, the systems will undergo specific testing to supplement areas where sufficient evidence for standard compliance could not be achieved. The SIL2LinuxMP certification will be largely based on "compliant non-compliant development".

Workshops 2015

Workshops 2016

Workshops 2017

• Workshop #1 (January 24 to 26, 2017)
• Workshop #2 (April 4 to 6, 2017)
• Workshop #3 (June 6 to 9, 2017)
  
• Workshop #4 (September 26 to 28, 2017)
  
• Workshop #5 (December 5 to 7, 2017)
  

Workshops 2018

• Workshop #6 (February 13 to 15, 2018)
  
• Workshop #7 (April 17 to 19, 2018)
  
• Workshop #8 (July 17 to 19, 2018)
  
• Workshop #9 (September 4 to 6, 2018)