Tried and tested OSEK/VDX compliant basic software

We have been developing communication stacks since 1999. Since then several implementations of our EB tresos OsekCore have been employed in mass production projects. Our OsekCore communication stacks are proven in many mass production applications such as body control systems, climate control systems or radio navigation systems. Our OsekCore OS (operating system) is a central part of the BMW standard software platform.

EB tresos OsekCore is a state-of-the-art implementation for OS (operating system), CAN, LIN, and flash bootloader. Our mass-production-ready software delivers a complete, flexible and scalable solution for running complex control strategies in a multibus network environment. It includes diagnostic services and ECU mode management and is delivered as a fully integrated and configured basic software package. Strategic partnerships with semiconductor manufacturers guarantee that our EB tresos OsekCore is available for the most popular automotive microcontrollers.

In addition, we offer a variety of services to support your ECU software development project, ranging from consulting and development services to seminars and trainings on site.

CAN communication stack

• Optimized for performance and small footprint


• Optimal use of existing communication controller hardware

Our CAN communication stack includes all necessary software components:

• Interaction layer (signal abstraction)


• Network management (operating modes)


• Transport protocol layer (segmentation support)


• Diagnostics (KWP2000 and UDS)

LIN communication stack

• LIN master and slave solutions are available for LIN version 1.3, 2.0, 2.1


• Optimal use of available hardware (standard or LIN UART, LIN controller)

Our LIN communication stack includes all necessary software components:

• Interaction layer (signal abstraction)


• Transport protocol layer (segmentation support)


• Diagnostics (KWP2000 and UDS)

Gateway

Our CAN-to-CAN gateways are available with the following options:

• Signal routing only support


• Signal and diagnostic routing support

Our CAN-to-LIN gateways are available with similar options, as well.

CAN flash bootloader

• Flash driver add-on for CAN communication stack


• Optimized configuration of communication stack to reduce footprint


• PC-based download tool available upon request

OSEK OS (operating system)

Our OSEK/VDX compliant operating system, EB tresos OsekCore OS, integrates easily with the communication stack, EB tresos OsekCore, forming a complete basic software architecture. Our solution is standard compliant since 1997:

• OSEK/VDX 2.2.2


• ORTI 2.0 and 2.1


• OSEK time

Hardware availability

We work in close cooperation with major semiconductor vendors  to develop the CAN and LIN drivers for the most frequently used  automotive microcontrollers.
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 OsekCore modules

Ports are available for common microcontrollers used in embedded automotive ECUs

OEM specific implementations

• Chery


• PSA


• Renault/Nissan


• Further OEM-specific solutions are available on request

Communication safeguard

EB tresos OsekCore modules implement features for reliable communication including (but not limited to):

• CAN controller (bit timing, acceptance masks supervision)


• Data buffer (encryption, mirroring)


• State machines (encryption, mirroring, consistency checks)

Comprehensive tooling support

Modules of EB tresos OsekCore 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 file formats

Competent project support

We provide competent engineering services for the whole embedded software lifecycle:

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


• Porting to specific microcontrollers


• Local support – global representation