ARINC653 OpenSource suggestions

Thread Starter

JoseDAssisCordeiro

Joined Nov 13, 2016
2
Hi everyone,

Me and my group are developing the ARINC653 protocol this semester in OpenSource.
The idea is to have independent partitions than can run OS, applications or other things, in well defined and restricted amounts of memory, completely independent of each others in the same platform. If one crashes it won't affect the other partitions. This was first created 10 years ago for airplanes, we are trying to adapt this to other industries. We developed the OS and the memory and time partitions already, now we are looking for different points of view about the subject, what is worth it or not to explore about the different possibilities in the future using this.
 

Thread Starter

JoseDAssisCordeiro

Joined Nov 13, 2016
2
What are the advantages compared to running independent partitions on separate CPUs?
It saves a lot of hardware, if we can have small partitions all in the same chip, in order to optimize the use of the hardware.
Also to replace or update the software we only need to change one chip. For example airplanes live longer than the chips, so in that case we wouldn't need to replace all the small pieces of hardware and in that way saving costs.
The many possibilities for each partition, allowing the reuse of the same hardware and software for different uses.
 
Top