<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:tax="http://schemas.microsoft.com/sharepoint/taxonomy/soap/" xmlns:tns="http://schemas.microsoft.com/sharepoint/soap/recordsrepository/" xmlns:spsup="http://microsoft.com/webservices/SharePointPortalServer/UserProfileService" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=PT link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Yes, ESA and we are going to get as much as possible feedback from the space community just to try to agree and define the RTEMS Space Profile. The RTEMS Space profile will be the subset of RTEMS that will be subject to Space Qualification. Any interested party that would like to participate in the pre-qualification, is invited.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>We understand. We also do not intend to “overflow” the community. We intend to have the major discussions in the qualification@ but everyone is invited to participate in the mailing list. With the execution of the project we could also change, if we need.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>We believe that we could need to ask some questions around in order to start to define the plans of the qualification.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thank you in advance for the support, kind regards,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Helder<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> users [mailto:users-bounces@rtems.org] <b>On Behalf Of </b>Joel Sherrill<br><b>Sent:</b> terça-feira, 4 de dezembro de 2018 16:59<br><b>To:</b> Amaan Cheval<br><b>Cc:</b> rtems-users@rtems.org<br><b>Subject:</b> Re: Qualification of RTEMS SMP (ECSS)<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><div><div><p class=MsoNormal>On Tue, Dec 4, 2018 at 10:53 AM Amaan Cheval <<a href="mailto:amaan.cheval@gmail.com">amaan.cheval@gmail.com</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><div><p class=MsoNormal>This is great news!<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>- Is there a way for other interested parties to join the effort (volunteers from the community)?<o:p></o:p></p></div></div></blockquote><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I am at hte Flight Software Workshop and the ESA person here says they will get input from the space community.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>From an RTEMS perspective, some will happen on devel@ but there is a qualification@ mailing list. As a community, we MUST figure out how to provide and maintain as much of the technical information as possible needed for qualification and certification efforts. But we must not crush an open source project with weight. Ensuring our processes are well-defined, tests are repeatable, continuous integration testing, etc are all important. Doing things better is one push.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>The other push may ended up with things only applicable to qualification efforts. Those must be maintained by those interested in qualification. The formal analysis may be in this bucket.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>This is an opportunity to do things better and do ground-breaking work for an open source project. We all just need to do our bit.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>FWIW I am presenting tomorrow at the FSW and have 3 slides on qualification efforts including this one. <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>--joel<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><div><div><p class=MsoNormal>- Will all the work also be planned on public channels (devel@, public WIP branches, etc.)?<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Tue, Dec 4, 2018 at 6:49 PM Sebastian Huber <<a href="mailto:sebastian.huber@embedded-brains.de" target="_blank">sebastian.huber@embedded-brains.de</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><p class=MsoNormal>Hello,<br><br>I would like to announce to the RTEMS community a 24 month project <br>sponsored by the European Space Agency (ESA).<br><br>The main goal of the project is to enable European space missions to use <br>RTEMS as a software product in criticality category C (this is basically <br>category B without independent software verification and validation, <br>ISVV). Criticality category C means:<br><br><a href="http://ecss.nl/standard/ecss-q-st-80c-rev-1-software-product-assurance-15-february-2017/" target="_blank">http://ecss.nl/standard/ecss-q-st-80c-rev-1-software-product-assurance-15-february-2017/</a><br><br>"Software that if not executed, or if not correctly executed, or whose <br>anomalous behaviour can cause or contribute to a system failure <br>resulting in: Major consequences"<br><br>In ECSS-Q-ST-40C major consequences are characterized in Table 6-1 as a <br>major mission degradation without effects to the outside world of the <br>system. A future activity may perform ISVV to enable a use in category B <br>settings.<br><br>The qualification will be done according to ECSS standards <br>(ECSS-E-ST-40C and ECSS-Q-ST-80C). The standards are available at<br><br><a href="http://ecss.nl/" target="_blank">http://ecss.nl/</a><br><br>free of charge after registration.<br><br>The project consists of four tasks.<br><br>1. Qualification toolchain<br><br>This task aims to produce a tool chain so that qualification related <br>work can be carried out efficiently. For example: document generation, <br>test suite runs (including code coverage), test reporting, test result <br>archiving, code metrics, static code analysis, traceability (e.g. <br>requirements to tests), etc.<br><br>2. RTEMS SMP qualification data package<br><br>This task covers the main RTEMS components (source code, tests, <br>documentation; new: requirements document, ECSS standard tailoring) so <br>that a data package for space mission consumers can be generated.<br><br>3. RTEMS SMP formal verification<br><br>This is a research project. The aim is to apply formal methods for the <br>verification of a subset of the RTEMS SMP algorithms.<br><br>4. RTEMS SMP application porting<br><br>The goal of this task is to port an existing uniprocessor space software <br>from RTEMS 4.8 (RTEMS Improvement by Edisoft) to RTEMS SMP. The <br>algorithms used by the software needs to be parallelized.<br><br>The project partners are:<br><br>* Edisoft (prime)<br><br>* Lero (<a href="https://www.lero.ie/" target="_blank">https://www.lero.ie/</a>) with Lero researchers from Trinity College <br>Dublin and University of Limerick<br><br>* Jena-Optronik GmbH and embedded brains GmbH<br><br>The results of this activity should be open source and available to the <br>RTEMS community. The actual planning needs to be discussed at <br><a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a> in the next couple of weeks. One of the first topics is <br>the definition of a space profile which defines the feature set subject <br>to this project.<br><br>-- <br>Sebastian Huber, embedded brains GmbH<br><br>Address : Dornierstr. 4, D-82178 Puchheim, Germany<br>Phone : +49 89 189 47 41-16<br>Fax : +49 89 189 47 41-09<br>E-Mail : <a href="mailto:sebastian.huber@embedded-brains.de" target="_blank">sebastian.huber@embedded-brains.de</a><br>PGP : Public key available on request.<br><br>Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.<br><br><br>_______________________________________________<br>users mailing list<br><a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a><br><a href="http://lists.rtems.org/mailman/listinfo/users" target="_blank">http://lists.rtems.org/mailman/listinfo/users</a><o:p></o:p></p></blockquote></div><p class=MsoNormal>_______________________________________________<br>users mailing list<br><a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a><br><a href="http://lists.rtems.org/mailman/listinfo/users" target="_blank">http://lists.rtems.org/mailman/listinfo/users</a><o:p></o:p></p></blockquote></div></div></div></body></html>