Changes

Jump to: navigation, search
Limitations of traditional configurations
The following list recaps the typical requirements that such systems must meet. This list has been compiled on the base of real world use cases (specifically medical, transportation, automation and telecom applications):
* <div span id="REQ1">REQ1</divspan> ''Real-time and non real-time tasks integration'': On the same physical component it is required that non real-time and real-time worlds coexist; this allows overall design simplification, BOM reduction and tighter integration.* <div span id="REQ2">REQ2</divspan> The non real-time world - denoted as W2 in the rest of the document - is based on a well-known operating system such as linux; this operating system is also denote as GPOS (general purpose operating system).* <div span id="REQ3">REQ3</divspan> The real-time world - denoted as W1 in the rest of the document - is based on a RTOS or a bare metal executable.* <div span id="REQ4">REQ4</divspan> ''Inter-world communication and data sharing'': the two worlds must have the capability to:
*# communicate via asynchronous mechanisms
*# share data
* <div span id="REQ5">REQ5</divspan> ''Integrity'': W1 - also known as ''Secure world'' or ''Trust world'' - must guarantee a high reliability level, no matter how the other world behaves; in other words, W1 can not be altered by any kind of actions taken by the code executed in W2 (also called ''Non-secure world'' or ''Non-trust world'').* <div span id="REQ6">REQ6</divspan> ''Boot order'': W1 must be the first world to come up.* <div span id="REQ7">REQ7</divspan> ''Master-slave relationship'': once the system has completed boot process, a master-slave relationship must be established between W1 and W2, in the sense that W1 must have complete control of W2 world (for instance W1 must be able to force the complete reboot of the GPOS.* <div span id="REQ8">REQ8</divspan> ''L2 cache availability on W2 side'': Basic AMP configurations does not support L2 cache. Generally speaking, this is not an issue on W1 side because
** since typical code and data footprints are relatively limited, performances are generally not affected (this is not true for W2 world where, in case L2 is not available, overall Linux system performances may decrease noticeably)
** L2 may affect predictability of execution time significantly.
4,650
edits

Navigation menu