RFI on the implementation of F´ to ARINC653 #972
-
Hi there 👋, While reading the F Prime documentation, I saw that the F' has been ported to ARINC 653, see here in the Conclusion section. Could you tell me more about this? Do you have an example of an open source implementation? 👀 Our prime contractors, at least in Europe, are asking us more and more to adopt a TSP (Time & Space Partitioning) architecture on our products. Having never implemented them, I am not really familiar with TSP and this avionics standard. I hear some technical referents in my department talking quickly about the ARINC653 standard and from what I understand, it mainly defines standardized interfaces for partitions and how to schedule partitions. Having some information could help me a lot to defend the use of F' to my technical referents to instantiate it on future projects in my company. An example of F Prime implementation in a TSP architecture with ARINC653 standard would also be gold to convince them. 😃 |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
We had a research task early in F Prime development where we used an ARINC simulation to move components between partitions. The partitions communicated with each other via the hub pattern (see the architecture slides) using message channels. You simply connect components to either end of the hub to communicate with each other. They don't know they are on separate partitions. The porting process would essentially to build a deployment in F Prime for each partition, and then interconnect them using the hubs. The particulars of compilers, etc, is dependent on the ARINC platform, although my recollection is that they may have a common API. |
Beta Was this translation helpful? Give feedback.
@ThibFrgsGmz
We had a research task early in F Prime development where we used an ARINC simulation to move components between partitions. The partitions communicated with each other via the hub pattern (see the architecture slides) using message channels. You simply connect components to either end of the hub to communicate with each other. They don't know they are on separate partitions.
The porting process would essentially to build a deployment in F Prime for each partition, and then interconnect them using the hubs. The particulars of compilers, etc, is dependent on the ARINC platform, although my recollection is that they may have a common API.