Connect Android and AUTOSAR with Elektrobit’s EB corbos Link – technical insights

 

Connect Android and AUTOSAR with Elektrobit’s EB corbos Link – technical insights

Table of contents

  1. Introduction
  2. Background
    1. AUTOSAR
      1. ara::com
      2. AUTOSAR AP manifest and AUTOSAR XML
    2. Android Automotive OS
      1. Android partitions
      2. Constraints imposed by Android
      3. Android inter-process communication
  3. EB corbos Link top-level requirements
  4. EB corbos Link architecture and integration scenario
    1. ara::com events and fields as VHAL properties
  5. Summary & conclusion
  6. References

 

 

Introduction
EB corbos Link enables Android applications to communicate with Classic and Adaptive AUTOSAR ECUs using widespread middleware protocols such as SOME/IP. To achieve this, EB corbos Link seamlessly integrates a production quality AUTOSAR SOME/IP protocol stack into the Android framework and thus facilitates transparent access to the data pool provided by Classic and Adaptive AUTOSAR nodes for Android applications. This way, EB corbos Link combines the advantages of Android and the Android Automotive OS (AAOS) ecosystem with the benefits of an AUTOSAR in-vehicle network allowing the application developer to concentrate on application development within Android while being able to leverage AUTOSAR-enabled services, methods, and events throughout the vehicle.

 

Resource type
Tech paper

 

Related content

Reaching software-defined vehicle level 5 with EB corbos Link

Accelerating on the road to the smart truck cockpit

Elektrobit-Infosheet EB corbos Link

 

You are currently viewing a placeholder content from Pardot. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.

Unblock content

More Information ‘

‘