SNIP_CLASSIC_RTE_SECTION_4_1_4_4_Multiple_instantiation

4.1.4.4 Multiple instantiation [SWS_Rte_02002] Upstream requirements: SRS_Rte_00011 ⌈Multiple objects instantiated from a single AUTOSAR software component (type) shall be identifiable without ambiguity.⌋ There are two principle ways to achieve this goal – • by code duplication (of runnable entities) • by code sharing (of reentrant runnable entities) For now it was decided to solely concentrate on code sharing and not to support code duplication. [SWS_Rte_03015] Upstream requirements: SRS_Rte_00011, SRS_Rte_00012 ⌈The RTE only supports multiple objects instantiated from a single AUTOSAR software component by code sharing, the RTE doesn’t support code duplication.⌋ Multiple instances can share the same code, if the code is reentrant. For a multi core controller, the possibility to share code between the cores depends on the hardware. Example 4.2 is similar to the example 4.1, but for a software-component that support multiple instantiations, and where two instances have their R1 RunnableEntity mapped to the same task. Example 4.2 Runnable entity R1 called for two instances out of the same task context: