 Okay, so welcome everyone So we have proved we are able to study presentation and not now Let's go to to the space because we are using another computer where this is not installed in for representation. I will Skip it Okay, so What's the line looks for space? we have started about a year and a half ago working together and from the early beginning we are Let's say community-based open source activity nobody pays us for our work. We are volunteers working there and We have started to work on it because several people met and we have been discussing the space applications Looking for any reference anything where we can start with and we have found out that there is nothing because everybody solves their problem for Based on the mission and we were starting starting to think that it would be pretty nice to have something in common Which the community can share together? so And so it was the first initiative hour that the last February we have started to organize some regular meeting to and our intention is to pick up all the stakeholders interested in space or in the London Linux in space applications and to let's say to gather the requirements and to define How shall the Linux which is ready for space look like and because we are mostly settled in Europe We also started to analyze the standards of European Space Agency because if you want to Have something in space in Europe that typically will have to deal with that And so we always declare that we our intention is to keep as close to the European Space Agency does as possible because they are so strict that Linux you cannot complain 100% So here are three organizations which have started to work together Last year we have been working with the research Institute of the Czech Technical University Then with the guys from the Czech Aerospace Research Center. They are here and they will after us They will show show you their satellite, which is based on Linux and currently working up there And we are from the technically University of Liberates I have picked the names of people who are working with us on our let's say regular meetings we have so on the first slide we are Two of us then there are the guys from the Czech Aerospace Research Center Javier from European Space Agency is responsible for software Let's say software on flights and he helps us a lot with the SS standards and our He he helps us on our way to try to be compliant as Or at least as as possible, let's say Eric Weiss does a lot of stuff in the Octo Timber that was so nice to join us and we are happy to have him on board and the same is for the last name Yeah, Kaivan sends a many greetings the greetings to the audience, but unfortunately he couldn't come because he didn't get visa so And Now shortly what we are doing now So you if you are interested you can scan the QR code Which will lead you to linux4space.org web page and we try to gather all the information there So we are organizing regular meetings which are going online every second week and on the meetings we have found out that Everybody now something about these space applications and the problems probably which we shall solve in space and discuss and Okay, we had a lot of notes and stuff like this So that's why we I think in March started the wiki page and discuss some general structure there then we have been working on your requirements and we are analyzing the standards and Let's say we are moving slowly to the implementation phase So we have started some GitHub of which is ready for for our layers and also What do we think it's important to keep people meeting together and discussing all the problems to mirror so I will skip this unfortunately and So the result of the let's say the first year is that we agreed on the some use case general use case Which is a typical for let's say the Linux for space distribution. So Definitely we Yet we are not reaching to have a mission critical system So we have some from because there are there is a so much types of use cases in space as you heard in the keynote this morning, so For the Linux for space, we would like to keep concentrated on the payload system Which typically is working with no graphical use interface because it's running on the CubeSat so CubeSat payload Which shall provide a real-time operation for let's say defined processes And we were concentrated when we were talking about requirements and trying to define them We were focusing on the space environment and space environments means that it's totally unfriendly to the hardware You have a lot of radiation there. So The LDR version you need to shut Shedown as fast as possible if you are reaching the radiation area and it's quite challenging in Linux sometimes and And You will need to have typically several real-time data and some backups there So the the other part of the use case is that we have decided what define as us that we are Designing the distribution with the standards in our in our heads thinking about the What's defined in these standards to be able to be compliant and we have decided to create some reference distribution consisting of several metalliers in the Octo and We are visiting the Eliza working Eliza project. There is a working group Focus to aerospace. So we keep the space because there is a lot of people a lot of people from the let's say avionics so we are keeping the space flag there discussing the stuff and the Last is that we would like to be community-based. I mean to open to everyone. So everyone who wants to do something or Even to comment something or provide us any feedback is really really welcome So yeah, this is for you Okay, thank you, Anka and I would like to talk about CubeSat or Linux in space especially CubeSat I take I took several It took me about two months to find out how many of your Linux is up there in year 2022 and This is a result. You can see on the Chart that almost 20% of CubeSat use Linux in space. There is about 30 30% of firmware custom firmware and About 8% of RTOS and there is a big undefined area It's It could be explained but by two options first options is that I'm very bad at googling and searching and Second option is that this is the place It's these CubeSats were built by private by companies, which you don't want to share their information Use if they're use any any Linux This statistics stats includes only unique CubeSat missions. That means if CubeSat for example, you're called lazy lazy was launched in January and then Was another one with same name Launched in December. We just counted also one record One important thing to To mention is that one CubeSat may have a multiple system That means that one CubeSat may have RTOS or TOS for on-board computer and line CubeSat may use Linux for the payloads Here's a short algorithm, which I use to find this information. I just pick one CubeSat and Put together with keywords. Nothing nothing hard and And if I haven't found anything, I just mark it as undefined one To find information about one CubeSat took about 15 and 30 minutes, it's quite a lot and I just repeat it until I got mad. That's all and In this table you can see that Number of CubeSat launch it from 2020 is Is slowly increasing the year 2020 is Covid year, so I think that it has an impact on space in the industry too Yeah, and we analyze also also year 2021 it's about 50% of Linux on the board and Next slide please Yeah Yeah, and because it's very hard to find something about about CubeSats and Related to Linux So we decided to create Linux for space okay, where every one of you can put any article if you know about about Linux in space or if you want to provide some information about protocols for example, for example CubeSats protocol, which I don't know why this one or if you want to describe Space missions constellations and so on you can you can use this space for it Or from my side, okay So to the requirements Why we started with the requirements and I think this is the first difference we have let's say in the project because In avionics or in the automotive you always start with the requirements to have traceable design Means you have to specify really precisely what you would like to get at the end so we started to on our in our group we started to Discuss the requirements we had the first set which we presented in Dublin and After Dublin a lot of people have joined several talks and discussions So we needed to redefine it or update it and everybody's reading and then giving comments So that's why we are too late in the implementation because we wanted to keep it and the requirements itself are available in public get up. The only problem is that To keep the requirement model we are using Mudlap simulink requirement it or so we are exporting it to several output formats, but it's downloadable from there With some as some PDF export If I will prove if I would be asked that what's the let's say the most important So I think the biggest portion of the requirements is related to the space environment itself Because the problem is that You have so many different missions So we spend a lot of time in discussions which type of requirements It's let's say mission specifically in which can be Understand as a general one. So definitely I Have selected as an example that the system show we have started with the requirement the system shall start immediately So then we analyzed what does it mean for the system and which parts of the system shall be somehow Analyzed and again, maybe updated modified configured to be able to at the end had this have this feature So there are several several nice interfaces and protocols which are typically in space They are mostly implemented in Linux. So we would like to have in our layer a Support for anybody who is interested to be able to let's say integrated easily into their own nexus And the other one is the are the power constraints because Yeah, if you are if you are running from this on all panel The power is always an issue and you need somehow to have a power some processes may have power budgets and you need to Let's say stop the process if there is a danger that will eat all the energy of the CubeSat Not to us the connection itself. I was Surprised that finally everybody asked. So how shall the kernel for space look like I'm so sure we don't know Yeah, because never nobody required anything yet or said, oh, this is the missing specifics stuff and so so mostly There are some feature. I think this is yeah, and there yeah in our set of requirements is related to reporting the information and Status of the CubeSat back to the earth So How we have decided to go from the requirements to the implementation that for each of the requirement, which is identified We added an actual joke though Because we need to keep the track later on working in recipes ago Who asked us to and who wanted it and why he wanted it to be able to communicate Let's say with the main stakeholder who define the requirement and to keep the track If I don't know later on you will find that you cannot fill the requirement or you need some update Okay, and now it's again for Lucas This is my part But to ECSS standardization Just a brief Information what is ECSS and how is it device divided? It's a divide into four Branches and in the root of these branches is General description with describes how this requirements and standards works and Yeah, yeah, how it works. Yeah, there are four branches. As I said first branch is space project management This aims to provide Information about project planning and implementation configuration as you can see there Second one is space assurance. This branch is one of the Important for us our project But not everything from this branch is is Let's say important for example materials and Linux, I don't know Another another one is space engineering another Another branch which is very important for this project and last branch is space to stability Which you describe for example of planetary protection space situation ever in this Total count over these Standards is for space management is six space assurance is 62 space engineering 65 and space insurance Sustainability sorry to the commands Yeah, and because there are a lot of these standards so we decided to Let's say select the one the ones which we need for our project we set up the rules the like we We need to use requirements definitely which focusing on Software engineering and IO communication. We can definitely exclude documents which are focusing on material mechanism and electrical and us Linker already said That's okay We are trying to be as close to ECSS as possible after selecting know after after applying these rules so we can see that space management is is Mark are removed There are ee components which are not necessary Materials as I said already and in the space branch we can We can Okay We can miss other groups other option and mechanical engineering and group system group ground system to and Space sustainability is another branch which is not important at this time too fast Oh Yeah, after applying this rule you can see that space assurance is about 9 documents now and space engineering. It's still big amount of documents. It's a 60 36 documents, sorry Yeah Yeah, and how how to how to How to describe our implementation strategy first step is done It's separate the comment impacts because every document has a different impacts for us the highest impact has Document with impacts on a whole project management methodology and so on The lowest impact has unrelated project For example the materials First fast is done. We set up an impact Now we want to start with the comments with with the highest impact Which we will try to implement into our project and then the third third phase is divide Logically into two different phases, but it's still certified We want to implements Requirements which impacts on your user user space software and the driver implementation Yeah And I tried to show How how many of the high documents will be in each phase in the first or second phase? It's about seven documents in space assurance in second phase of Space engineering is only about 10 documents and In the last phase It's in space issuance two documents as space engineering is big amount of documents 26 and I think that's all from my side And it links to the proposed yocto structure again when we are working discussing the implementation We wanted to keep the connection to requirements and also to the standards and We wanted to create set of layers which everybody can Integrate into their projects. So we wanted to keep us. Let's say quite hard Independent and we have selected few hardware references So first one is Raspberry Pi because everybody has it and works with that then the QML for somebody who doesn't work Doesn't want to borrow themself with the real hardware and that we said always the check Abbreviation for the aerospace is center because they have their own hardware and volunteered to implement it there as well and we have several layers because we have decided to create to Let's say you have two layers of which one is Let's say I called We call it metal in ox for space and it's for the system layer I mean everything which is related to the system itself like okay the bootloader the image definition or I don't know Whatever the system configuration and stuff like this shall be kept in this layer and Then there was the application layer. So if I would try to again Provide you till a near version how to orient it there So the first one is the kernel space and the second one is the user space and Later on we have decided to add So to do it like this So on this we have agreed. I think about three months ago So our intention was to have the system in the dark purple and to have the Linux for space up And then we found that there is a plenty of software which Maybe can be useful as well So then we have decided to create let's say a container for some we call it other useful space stuff for Linux But we would like to keep On the on the left part because again for each recipe for each piece of software Implemented there. We would like again to keep really close to the methodology and the software engineering Standards which are required by European space agency Sometimes it's not possible simply because the The workload of the open source is completely different than it's required by Esa And I think this is one of the issues which shall be discussed maybe for a future and Yeah, so as I told already in the requirements model, we have some The octo attribute where we fastly started to discuss for let's say feature by feature or requirement by requirement How shall it appear? In the octo and later on who will be responsible and who will want you to do it and stuff and stuff like this So definitely there is a recipe system later and it links to typically to To do a meta Linux for space or the meta Linux for space up. Sometimes there are features which are related generally to the system and We don't know how to do it in octo or there are just maybe a comments or Comments to the whole system and sometimes we are we have not decided yet so Again what you should shall expect in the system layer It shall be Let's say an example of the distribution show so we shall we hope to provide you Linux for space minimal image I mean the minimal working Linux bootable with all the features we need we want to have so again as an example What is related to space in the space? Typically you have some redundancy with the software because The radiation may destroy your flash memory So you will have several of the flash memories and you may keep more than just one file system because you need a copy of it for For the situation where you value when you lost the first one So during the boot this the device itself shall wake up and this say, okay, I see There were I was sleeping because there was a radiation and now I lost this memory So I shall start from this one. So that's exactly a stuff which belongs to the To to this this layer and again, you need to check the root file system that it was not corrupted after the last operation and Yeah, we would like to Have some kind of idle mode also for if you were just let's say if the coupon cubes that is new in nothing and waiting for To the payload is waiting to be working So what shall be in the recipe application layer? For me the best example here is this the diagnostic information because the satellite typically needs to communicate Down to the earth to the people who are operating it and it shall report number of restarts and I don't know how many times it how long it was in the idle and And and and a lot of stuff like this. So it's listed somehow in the requirement or again Service which is running in the user space Can be ready here print start and configure it for you to be able in for your real cubes Let's say to add your metal layer and to update it according to your needs So we have started a public good lab corridor Linux for space and You can see there that there are three subgroups first one is related to requirement So means we keep it just to have versions on the requirement and from that you can download as a good lab artifact The PDF created from the exports Then there is part which is called yokto and layer by layer there are good luck good luck projects for each of those layers and Then there is Linux for space for space yokto And we keep it there for you to have an example of the let's say the working directory for yokto So it's done. So if you would unload it and try to play with that You just need selected the type of hardware You would like to have NHL create for you properly working Directly for you to be able to compile it and I don't know play with it somehow So again back to the reference hardware So we have decided to use those popular emulators and then some let's say space really hardware so the first one is The type of hardware you will be You can stay here and listen about it in the next section and Yeah, and Javier from as I has proposed us to focus on the null 5 Which is opens of risk 5 processor, which is designed to be space ready. So it's exciting So, yeah, it's quite a challenge to be able to support it because It's not yet implemented in there is some Linux working on it, but yeah, so Unfortunately, this will not work. So I will just stop here. So if you're interested, you're welcome. Everyone is welcome And yes, we're already Hoping and now I think it's time for questions if you have any Yeah It's I'm sorry for that the check abbreviation for the check aerospace research and central and the guys are just in the next line at your back and They are talk they are talking in the next section. No, no, no, it's the name of the research Institute Yeah, they will be talking about it in the next section so I didn't want to You know, they want to talk about it Yeah, it's a surprise for next session Okay, sorry Actually, there is no requirement Yeah, okay, there was a questions about the real time behavior. Yeah, so when we were talking in general everybody says yes It would be nice to have it but when we Went to the negotiation about the requirements So when I was checking it last time before last week in the requirements, there is nothing about it yet Nobody required that to see I wanna yeah, I really wanna have it Done this way and I think I think it's mostly because we are talking about the payloads not to real mission-critical systems Yeah, exactly and Each of this discussion ended up. Okay. Maybe this is really mission-specific We hoped to have it Yeah, let's say definitely it shall be We are from the university and holidays are starting just now so we have two months I hope to have it. Yeah, so the first version. Let's say the first them Yeah, yeah, there was a just to repeat the question that There was a comment that I was not talking about any hypervisor Because again to reach the requirements from the standards. Maybe this is the only way. Yeah, but We are still working on the let's say standards analysis. So maybe it will come later. Yes You are totally right I know I know you have email So maybe we can cooperate so I think okay So in our Linux space is coming on Friday, and we will be there. Yeah, okay We can borrow you Okay, any There is a sign that we shall stop Yeah, okay, so then we have to stop. I'm very sorry that we lost some time at the beginning