SNIP_CLASSIC_COM_FIGURE_Figure_7_23_OS

Figure 7.23: IOC overall view There are use cases where 1 to N IOC code instances needs to be generated on top of the OS code which is used by multiple different Software Clusters. As those Software Clusters use different IOC configurations, as a consequence the OS code shall not include any code depending on a specific IOC configuration. T o ensure compatibility between IOC and OS code, there is still a dependency in that it is necessary to use the same OS configuration for the generation of the different IOC code Instances. Furthermore, the OS and IOC code should be generated from an OS Generator coming from the same vendor. [SWS_Os_00671] Upstream requirements: SRS_Os_80020 ⌈The IOC implementation shall be part of the Operating System The IOC is a third type of communication, in addition to • Intra OS-Application communication: Always handled within the RTE • Inter ECU communication: Already available via well-defined interfaces to the communication stack (COM) ⌋ IOC mode : This is the mode where the OS generator is invoked with a configuration parameter to generate the IOC code only . OS mode : This is the mode where the OS generator is invoked with a configuration parameter to generate the OS code only .