autosar adaptive in preevision - vector informatik
TRANSCRIPT
V0.2 | 2019-12-02
PREEvision 9.5
AUTOSAR Adaptive in PREEvision
u AUTOSAR Adaptive
AUTOSAR Methodology
AUTOSAR Adaptive in PREEvision
Combined Systems (Classic + Adaptive)
Vector AUTOSAR Adaptive Toolchain
Roadmap
Agenda
2
Motivation
AUTOSAR Adaptive
Automotive trends New requirements
u As a partner of the Automotive industry AUTOSAR saw the necessity to define a new platform
u It was clear that future cars will have heterogenous architectures
u The existing architectures had to be complemented by another one
Adaptive AUTOSAR
3
AUTOSAR Adaptive
u AUTOSAR Methodology
AUTOSAR Adaptive in PREEvision
Combined Systems (Classic + Adaptive)
Vector AUTOSAR Adaptive Toolchain
Roadmap
Agenda
4
AUTOSAR Adaptive Methodology
AUTOSAR Methodology
Application
Machine Service instance
Operating systemwith deployedapplication
5
AUTOSAR Adaptive workflow
AUTOSAR Methodology
Design / DevelopmentDeployment / Integration /
Verification
Generate
ara::com services
Redeploy for Target
compile, pack, sign
Config. ARA platform services
Policy: Rights access PHM (SWCL internal)
Create SWCL
Process Instances
Function Groups
Start-up config
Write Business Logic
Design Internals of SWCL
Executable / Process Design
Allocation of work Port to process assignment
Policy Grant Design
Safety concept
Define SWCL Design
Communication relations
Define global Services
Service Interfaces
Create System Design
Hardware topology
<<OEM Paketizer>>
Prepare for OEM backend
<<OEM Board>>
Install BSW (core)
Define SWCL internal services
Service Interfaces
1
2
3
4
5
6
7
Define Global DEXT Design
DTCs, Diagnostic Services
Machine Design Extract
<>
DEXT (SWCL Extract)
<>
SWCL Design
<>
Global Service Catalogue
<>
SWCL Service Catalogue
<>
Logic
C++
ara::*
C++
network binding
C++
JSON
{}App Binary
0101
Compile
Exec. Design
<>Process Design
<>
Integ-ration config.
<>
Tested SWCL
C++
Business Logic Package
0101
Redeploy for Test Target
compile
Test Deployment
<>Test Service Design
<>Define Test Machine
Deployment, services
SWCL Base Software
0101
Define Machine Deployment
Processor, function groups, services, file system, final DEXT
OS Selection
Adapt platform software to hardware
Vehicle “App Store”
Hardware selection
Application Developer4
E/E Architect1
Map platform SW into E/E architecture
Machine Platform Architect
2
Define high level UCM, watchdog, diagnostics
SWCL Architect3
Platform SW mapping to OEM needs
u Transformation of service interfaces
u New apps / functionalities
Create diagnostic mapping
SWCL Integrator5
Create a complete SWCL
Internal test that SWCL works correctly
ECU Integrator6
HW Setup
OS Installation / Startup / Configuration
SWCL bound to machine
Business logic tested in evaluation board
Vehicle Integrator7
Provide Vehicle Package
PREEvision
6
AUTOSAR Adaptive
AUTOSAR Methodology
u AUTOSAR Adaptive in PREEvision
Combined Systems (Classic + Adaptive)
Vector AUTOSAR Adaptive Toolchain
Roadmap
Agenda
7
AUTOSAR Adaptive support
AUTOSAR Adaptive in PREEvision
AUTOSAR Adaptive in PREEvision
Additional applicable layers
8
Design Workflow for AUTOSAR Adaptive
AUTOSAR Adaptive in PREEvision
Service Design
ServiceInterface
Design
ServiceInterfaceBinding
SoftwareDesign
Network Design
CommunicationDesign
HardwareDesign
HPC
Hypervisor Exec3
Exec1 Exec2
µPCore1 Core2
µC
Switch
ServiceInstantiation
SoftwareHardwareMapping
9
u The AUTOSAR Adaptive Explorer helps at all phases of the workflow with creating the Adaptive AUTOSAR System.
u Combined with diagrams, Signal Router and further data synthesis it’s possible to create an Adaptive System from scratch or edit an existing one.
AUTOSAR Adaptive Explorer
AUTOSAR Adaptive in PREEvision
10
Service
AUTOSAR Adaptive in PREEvision
u Service is an abstract description for a set of software functionality with the purpose to be available and be reused by several different clients.
u The Service Definition allows describing capabilities of the services as well as their dependencies.
u Additionally the Service ID and the preferred VLAN for a Service can be defined. These settings are considered by the following phases of the top-down design.
u The Service Definition can also be realized using the SOA Architecture Diagram.
11
u The Service Interface describes the capabilities of a Service.
u It allows the aggregation of Properties, Methods and Events.
u Service Interfaces can be created and modified using the Service Interface Editor.
u Additionally, Service Interfaces can be created and edited graphically on a Class Diagram.
Service Interface (1/5)
AUTOSAR Adaptive in PREEvision
12
u The sub-elements of a Service Interface are characterized by a data type.
u Data types can be assigned using the Service Interface Data Type Editor.
u Designing complex data types can also be realized graphically using the Class Diagram.
Service Interface (2/5)
AUTOSAR Adaptive in PREEvision
13
u PREEvision supports the SOME/IP protocol for the transport of service data over the network.
u SOME/IP identifiers shall be defined for every sub-element transmitting data into the bus.
u A synthesis for the SOME/IP interface deployment is available.
u The definition of the SOME/IP identifiers can be realized using the SOME/IP Interface Deployment Editor.
Service Interface (3/5)
AUTOSAR Adaptive in PREEvision
14
u The serialization of the Service Interfaces is defined by means of Transformers.
u Transformation rules can be defined for each sub-element of the Service Interface.
u This can be done within the Service Interface Transformation Properties Editor.
Service Interface (4/5)
AUTOSAR Adaptive in PREEvision
15
u E2EProfileConfiguration is defined by End To End Transformers, End2EndEventProtection-Props by End To End Transformation Properties using dedicated editors.
u End To End Protection can be assigned to every Event and Property Notifier of a Service Interface using the End To End Transformation Properties Assignment.
Service Interface (5/5)
AUTOSAR Adaptive in PREEvision
16
u The Software Architecture in AUTOSAR Adaptive is described by means of adaptive software components which can be grouped in compositions.
u Software Architectures can be created using the known software diagrams: SW Component Type or Instance Diagram and Interface Assignment Diagram.
u Alternatively, is also possible to work with the Provided Port Connection Editor and Required Port Connection Editor available in the AUTOSAR Adaptive Explorer.
Software Architecture
AUTOSAR Adaptive in PREEvision
17
u The AUTOSAR Adaptive Application describes a collection of executables that form an adaptive application. It realizes the transition for the support of Software Cluster.
u Adaptive applications can contain several executables.
u The creation and edition of AUTOSAR Adaptive Applications can be realized with the Adaptive Application Editor.
Adaptive Application
AUTOSAR Adaptive in PREEvision
18
u For deploying an Adaptive Application, startup dependencies to other applications or to states of the machine or function groups need to be defined.
u It is also necessary to configure the startup parameters of the process for the operating system.
u This activity is supported by the Process Startup Dependency Editor.
u For designing the state machine of an application, the State Chart can be used.
Application Deployment Configuration
AUTOSAR Adaptive in PREEvision
19
u The design of complex ECUs and high performance computers (HPCs) is supported in diagrams.
u Hypervisor, Microprocessor, Microcontroller, Core and Execution Context are available.
u The combination of different operating systems (Linux, MICROSAR, Android) and platforms (AR-Classic, AR-Adaptive) is possible.
Hardware Design
AUTOSAR Adaptive in PREEvision
20
u AUTOSAR Adaptive Platform supports Ethernet as communication bus technology.
u The design of the network topology can be realized using the Network Topology Diagram.
u The topology can be viewed and edited with the Network Topology Editor.
Network Design
AUTOSAR Adaptive in PREEvision
21
u As in the classic platform, the software components are distributed to the available machines.
u That can be realized graphically, working with diagrams and drag&drop, or using the Software To Machine Mapping Editor.
SW to HW mapping
AUTOSAR Adaptive in PREEvision
DnD
22
Service Instances (1/2)
AUTOSAR Adaptive in PREEvision
u A Service Instance makes the functionality of a Service Interface available on the AUTOSAR adaptive platform.
u Service Instances are automatically synthesized based on the information of the SW-HW mapping and the Service Interfaces assigned to the SW Ports.
u With the SOME/IP Service Instance Editor the service instances can be edited.
23
u Service Instances contain the information needed for the communication into the Ethernet bus.
u Tp/IP configuration as IP addresses and ports and the Service Discovery configuration can be realized using dedicated table editors.
Communication Design (Service Instances)
AUTOSAR Adaptive in PREEvision
24
u A further aspect to be configured for the machine deployment are the Service Discovery parameters.
u IP addresses as well as ports can be configured using the Service Discovery Configuration Editor.
Communication Design (Machines)
AUTOSAR Adaptive in PREEvision
25
Support of AUTOSAR Adaptive 19-03
AUTOSAR Adaptive in PREEvision
Import Export
Format Use CaseAUTOSAR version
Service Interface Description
Import/Export19-03
Execution Manifest*
Machine Manifest*
Service Instance Manifest*
Application Description
Custom Export
u Support of AUTOSAR 19-03 for import and export
u AUTOSAR 17-10 import and export is not longer supported!
* Preliminary manifests
26
Supported
Service Interface
C++ data types
SOME/IP deployment
SOME/IP serialization
End to End Protection
Adaptive Application SW Component Type
Adaptive Application*
Executable
Process
Startup configuration
Machine
Service Instance
Service discovery
System Design
Overview supported/not supported concepts
AUTOSAR Adaptive in PREEvision
Not supported**
Persistency Interface
Diagnostics
REST
Resources
Service Needs
Security
Crypto
Platform health
Software Cluster
Signal based communication
…
* Represents the transition to software cluster
New!
New!
Extended!
** This table is not complete
27
AUTOSAR Adaptive
AUTOSAR Methodology
AUTOSAR Adaptive in PREEvision
u Combined Systems (Classic + Adaptive)
Vector AUTOSAR Adaptive Toolchain
Roadmap
Agenda
28
Workflow for combined systems
Combined Systems (Classic + Adaptive)
Service Design
Network Design
ServiceInterface
Design
ServiceInterfaceBinding
AdaptiveSoftware
Design
HardwareDesign
SoftwareHardwareMapping
Classic Software
Design
SoftwareConnection
ServiceInstantiation
AdaptiveCommunication
Design
Signal Mapping and Serialization
ClassicCommunication
Design
ApplicationDescription
Manifest
ECU Extract
Common Task
AR Classic specific
AR Adaptive specific
Connection Task
29
u Service Interfaces of AUTOSAR Adaptive can be linked to AUTOSAR Classic Interfaces (Sender Receiver Interfaces, Client Server Interfaces and Trigger Interfaces)
Classic–Adaptive interface correspondence
Combined Systems (Classic + Adaptive)
Service Interface
Method
F&F Method
Property
Event
Classic SWC
Operation → Client Server Interface
DataElement → Sender Receiver Interface (F&F with arguments)
Trigger → Trigger Interface (F&F without arguments)
Operation → Client Server Interface (get and set operations)
DataElement → Sender Receiver Interface (notifier)
DataElement → Sender Receiver Interface
Adaptive SWC
30
Classic–Adaptive interface linking
Combined Systems (Classic + Adaptive)
Service Interface
Property
Event
Method
Sender Receiver Interface
getOperation
setOperation
Client Server Interface
Trigger InterfaceTrigger
Operation
F&FMethod
Data Elementnotifier
FF with params
FF without params
operation
event
31
Connecting Adaptive and Classic SWCs (1/2)
Combined Systems (Classic + Adaptive)
u The Port Adapter
u allows connecting Adaptive SW Components with Classic SW Components
u is the model representation of the links between the sub-elements of one Service Interface and several Classic Interfaces
DnD
32
Connecting Adaptive and Classic SWCs (2/2)
Combined Systems (Classic + Adaptive)
u Several clients and servers can be connected
33
Unified Communication Modeling
Combined Systems (Classic + Adaptive)
MM
PDU
Signal (serialized)SOME/IP header
Tx Rx
u On the Software Layer, Adaptive and Classic software components can be connected with Port Adapters
u The software components are mapped to machines and ECUs
u The Signal Router creates a SOME/IP representation of the Service Interface on the bus (Ethernet)
u The SOME/IP representation consists of PDUs with serialized Signals containing the data of methods or events
u For Classic ECUs, this information is taken into the ECU Extract
u For Adaptive Machines, this information is used to check the consistency of the model and will be ignored on export
Signal Router checks the system consistency and synthesizes the communication
Ethernet
34
AUTOSAR Adaptive
AUTOSAR Methodology
AUTOSAR Adaptive in PREEvision
Combined Systems (Classic + Adaptive)
u Vector AUTOSAR Adaptive Toolchain
Roadmap
Agenda
35
AUTOSAR Adaptive Toolchain
Vector AUTOSAR Adaptive Toolchain
Adaptive System Design
PREEvision
Diagnostics
Design
CANdela Studio
System Architecture
Sys DiagDesign
App Design
App DiagDesign
Service Instance
Machine Manifest
App Manifest
System Design
PlatformService
Deployment
Application Design
Deployment Configuration
Manifest*
Application Description
Simulation/Test
CANoe
Executable SW
Application Code
DaVinci AdaptiveTool Suite
SW Platform
AMSR Generators
Manifest
* Preliminary manifests36
AUTOSAR Adaptive
AUTOSAR Methodology
AUTOSAR Adaptive in PREEvision
Combined Systems (Classic + Adaptive)
Vector AUTOSAR Adaptive Toolchain
u Roadmap
Agenda
37
u PREEvision 9.5 → End of 2019
> AR Ad 19-03
> C++ data types
> End to End Protection
> Extensions of support for combined systems (Classic + Adaptive)
> …
u PREEvision 10.0 → 2020
u Candidate features> Software Cluster
> Time Sycronization
> Classic and Adaptive workflow unification
> Usability enhancements for combined system design
Roadmap
Roadmap
38
© 2016. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V0.2 | 2019-12-02
Author:Marcelino VarasVector Germany
For more information about Vectorand our products please visit
www.vector.com