Mass production ready AUTOSAR standard software

Our EB tresos AutoCore is an industry-leading implementation of AUTOSAR-compliant basic software for automotive ECUs (electronic control units). Our implementation of an AUTOSAR basic software core can be used to develop automotive ECUs for mass production projects. Our EB tresos AutoCore is available for the AUTOSAR release 3.1 and AUTOSAR release 4.0 with variants for CAN, LIN, FlexRay and Ethernet communication. Furthermore, EB tresos AutoCore includes a selection of the HIS-recommendations for a scalable AUTOSAR stack. What is more, we have also developed mass production ready variants of our AUTOSAR basic software core for BMW and the Volkswagen Group.

It is available for many popular automotive microcontrollers. We develop modules in cooperation with semiconductor vendors and test them extensively on target systems to ensure production level software quality. With the solid foundation of our EB tresos AutoCore, you are ready to start your innovative application software development projects.

 

Areas of application

The AUTOSAR standard’s broad scope and the involvement of next to every automotive OEM and Tier 1 supplier opens up a wide area of applications. Our EB tresos AutoCore is used in the following scenarios:

• Body, chassis and powertrain domain


• ECUs requiring FlexRay, CAN, LIN and gateway functionality


• Projects requiring software in accordance with the AUTOSAR standard, typically multiple supplier projects or projects with a focus on software reuse

EB tresos AutoCore is supplied with complete technical documentation in English and is fully supported through our help desk.

Our engineering services team ports EB tresos AutoCore to specific target platforms (ECUs), if they are not already supported, and integrates company specific standard modules into EB tresos AutoCore.

Runtime environment (RTE)

Our runtime environment is completely generated based upon AUTOSAR software component descriptions.

This guarantees:

• Perfect integration of application software layer and RTE


• Very low amount of overhead

Our RTE is stand-alone capable in conjunction with our operating system, EB tresos AutoCore OS. This allows you to use it as first step towards migrating an existing ECU software project to AUTOSAR. In addition, our RTE has been successful applied in the AUTOSAR Validator 2 Project (reference implementation of an AUTOSAR RTE).

Operating system

AUTOSAR single core OS

Our embedded real-time operating system (OS) implements the AUTOSAR standard. It complies with the OSEK/VDX standard and supports all OSEK conformance classes. Our AUTOSAR OS also supports all AUTOSAR scalability classes. This includes schedule tables, global time synchronization, OS-applications, timing protection and, where hardware support is available, memory protection. If you wish to reduce the memory footprint and CPU runtime, EB tresos AutoCore Os can be optimized at source level to remove all components that are not used in the given configuration.

• scalability classes 1 to 4


• features beyond an OSEK OS standard are memory protection, execution protection and schedule tables


• Improved robustness as compared to an OSEK OS


• Functions for stack usage measurement


• Functions for net task duration measurement


• Pre- and post ISR hook functions


• Generated configuration report


• ORTI (OSEK RunTime Interface) support


• Successful application in the AUTOSAR Validator 2 Project (reference implementation of an AUTOSAR OS)

AUTOSAR multicore OS

The use of multiple processor cores in one ECU enables you to scale architectures more easily and to achieve better performance per watt, as well as better data throughput. Multicore architectures do not only permit a more efficient distribution of control functions, they also offer new possibilities in the area of functional safety. Multicore processor support different safety architectures because they can operate redundantly as well as in a purely parallel mode with independent operation of the processor cores. In addition to the AUTOSAR standard, our implementation of a multicore operating system offers the following features:

Multicore extensions according to AUTOSAR release 4.0:

• AUTOSAR multicore startup and shutdown


• inter-OS-Application Communicator (IOC)


• multicore locking mechanism (AUTOSAR spinlock API)


• backward-compatibility with single-core applications

Code size and execution time optimizations via:

• configuration-dependent source-level optimization


• customizable AUTOSAR support


• use of a single hardware timer for all timing protection and timebase counters


• optional small auto-incrementing software counter

API functions for:

• runtime measurement of tasks and ISRs


• API functions for CPU-load measurement


• ORTI support for debugging

AUTOSAR OS for safety relevant projects

Our EB tresos AutoCore OS for safety relevant projects contains our micro-kernel OS and our QM OS together they form a fully featured AUTOSAR OS. Both are free from interference from each other. The micro-kernel OS entails all functions related to memory protection, interrupt handling and context switching between tasks. It is also completely verified according to ASIL D. The QM OS entails the remaining OS API functions that make up a complete AUTOSAR stack.

Communication stack

• Optimized for performance


• Optimal use of existing communication controller hardware


• Support for the bus systems FlexRay, CAN and LIN


• Includes transport protocol layer and network management


• Fit to serve as a stand-alone gateway controller


• Easily extensible with modules supporting non-AUTOSAR protocols and busses like XCP or TCP/IP


• Memory-, error- and mode management modules


• Implementation of nearly the full range of AUTOSAR services for ECU mode management, diagnostic error handling and memory management (for instance, the diagnostic protocol UDS (ISO 14229) is supported)


• OEM-specific diagnostic routines for DEM and DCM are available upon request

Firmware

We work in close cooperation with major semiconductor vendors to develop the MCAL modules (microcontroller abstraction layer modules) for the most frequently used automotive microcontrollers. We test these MCAL modules for compatibility with the standard software modules and integrate them with our EB tresos AutoCore.

This guarantees:

• Early availability of drivers for new controllers


• Optimal utilization of on-chip features


• Seamless integration of the hardware-dependent firmware with other EB tresos AutoCore modules

Ports are available for current microcontrollers from Freescale, Fujitsu, Infineon, NEC, Renesas, STMicroelectronics and Texas Instruments  .

Comprehensive tooling support

Modules of EB tresos AutoCore are configured, validated and generated with EB tresos Studio:

• Each module has its own editor


• Common graphical user interface


• Configuration validity checks ensure the consistency of configurations


• Importers for module configuration data support DBC, LDF, OIL and AUTOSAR file formats

Further tools from the EB tresos product line allow you to configure the FlexRay and CAN communication protocols, debug and trace the software and to carry out FlexRay and CAN cluster emulation in real-time.

Comprehensive project support

EB tresos AutoCore’s scope of functionality is AUTOSAR. However, it is not limited to that but complemented by competent engineering services and project support:

• Specification, implementation and integration of company-specific basic software modules


• Porting to specific microcontrollers