Virtual electronic control units in autosar

1. An electronic control unit comprising a plurality of cores, wherein:

the electronic control unit hosts a plurality of partitions including at least a first partition and a second partition;

the first partition is assigned to only one first core of said cores;

the second partition is assigned to only one second core of said cores;

the first partition is implemented to run an automotive open system architecture platform instance on the first core, the automotive open system architecture platform including an operating system configured for providing basic software services, wherein the first partition is the only one of the partitions implemented to run the automotive open system architecture platform instance providing the basic software services and wherein the first partition is the only one of the partitions which acts as a data interface for routing communications such that all data transfer between any of the plurality of partitions is routed through the first partition;

the second partition is implemented to run automotive open system architecture software components that need the basic software services provided by the first partition on the first core to fulfill respective functions of the software components; and

a partition interface couples the first and second partitions such that the software components are run as part of said automotive open system architecture platform instance implemented in the first partition.

2. The electronic control unit of claim 1 , wherein the partitions include a third partition that is assigned to only one third core of said cores, the third partition is implemented to run automotive open system architecture software components, and wherein a partition interface couples the first and third partitions such that the software components of the third partition are run as part of said automotive open system architecture platform instance implemented in the first partition.

3. The electronic control unit of claim 2 , wherein

the automotive open system software components of the second partition and the automotive open system software components of the third partition are implemented by separately memory flashing the respective partitions, and

flash memory addresses and address ranges of the first, second and third partitions are fixed and remain fixed between said flashing.

4. The electronic control unit according to claim 2 , wherein

said partition interface coupling the first and second partitions is implemented as a proxy software component of the automotive open system architecture platform instance,

and/or

said partition interface coupling the first and third partitions is implemented as a proxy software component of the automotive open system architecture platform instance.

5. The electronic control unit according to claim 2 , wherein one of the software components of the second partition communicates with one of the software components of the third partition through the first partition via said partition interfaces coupling the first and second partitions, and the first and third partitions.

6. The electronic control unit according to claim 1 , wherein

the operating system is configured for scheduling and/or time monitoring execution of the software components, and

said operating system is configured to schedule and/or time monitor a software component running on the second core and/or the third core.

7. The electronic control unit of claim 6 , wherein

said operating system is provided with fixed start addresses of software components running on the second core or the third core, such as to schedule execution of the respective software components.

8. The electronic control unit according to claim 1 , wherein every one of the plurality of partitions is assigned to only a respective one of said cores.

9. The electronic control unit of claim 1 , wherein the basic software services provided by the first partition and used by the software components of the second partition include services arranged in an automotive open system basic software: service layer, electronic control unit abstraction layer, microcontroller abstraction layer and/or complex drivers layer.

10. The electronic control unit according to claim 1 , wherein there are n second partitions and a total of n+1 partitions, wherein n is an integer greater than zero.

11. A method of executing automotive open system software components, the method comprising:

hosting a plurality of partitions including a first partition and a second partition; assigning the first partition to only one first core of an electronic control unit including a plurality of cores;

implementing the first partition to run, on the first core, an automotive open system architecture platform instance including an operating system configured for providing basic software services, wherein the first partition is the only one of the partitions implemented to run the automotive open system architecture platform instance providing the basic software services;

assigning the second partition to only one second core of the cores;

implementing the second partition to run, on the second core, automotive open system architecture software components that need the basic software services provided by the first partition on the first core to fulfill respective functions of the software components;

coupling the first and second partitions such that the software components are run as part of said automotive open system architecture platform instance implemented in the first partition; and

using only the first partition as a data interface for routing communications such that all data transfer between any of the plurality of partitions is routed through the first partition.

12. The method of claim 11 , further comprising:

assigning a third partition to at only one third core of the cores;

changing only one of the second partition or the third partition, wherein all partition interfaces remain unchanged; and

performing a binary comparison of software of the unchanged one of the second partition or the third partition to verify that the unchanged one of the second partition or the third partition has not been changed.

13. The method of claim 12 , further comprising:

changing the data interface and/or a partition interface;

changing only one of the second partition or the third partition; and

performing a binary comparison of the software of the unchanged one of the second partition or the third partition to verify that the unchanged one of the second partition or the third partition has not been changed.

14. The method of claim 12 , further comprising

performing the binary comparison and a test of the changed one of the second partition or the third partition.

15. The method of claim 11 , wherein there are n second partitions and a total of n+1 partitions, wherein n is an integer greater than zero.