Get a head start for your AUTOSAR development

We want you to be able to test your AUTOSAR software and its integration as early as possible and as quickly as possible. That is why we developed our virtual AUTOSAR basic software, EB tresos WinCore, which runs on a Win32 platform. That means that you can start even without ECU hardware.EB tresos WinCore contains all hardware independent basic software modules as used with your real ECU. This includes an AUTOSAR operating system that runs on a Windows PC. Even the Microcontroller Abstraction Layer (MCAL) is provided in the form of stub functions.

AUTOSAR startup projects

Our EB tresos WinCore allows you to learn and familiarize yourself with the AUTOSAR standard and our tool environment EB tresos Studio. You can start a mockup-project and begin configuring your basic software modules. Set yourself simple goals such as task scheduling, diagnosis-event handling. In preparation for future projects, you can also acquaint yourself with the workflows and configuration dependencies of the AUTOSAR standard.

Generation and build testing

Start your basic software development project and to carry out the complete software specification and build process including configuration, parameter validation, code generation, compilation and linking on your Win32 platform.

Functional testing without hardware

Even if the actual target hardware is not ready yet or if the necessary tools for testing (HIL-system, prototype vehicle, etc.) are not disposable, you can still continue developing with our EB tresos WinCore. Commission your ECU software and start testing the functional behavior of the hardware independent parts of you AUTOSAR software directly on your Win32 platform. That includes not only your application software (Software Components) but also your independent basic software modules and Complex Device Drivers.

EB tresos WinCore allows you to carry out unit tests and integration tests, focusing on the functional behavior exclusively. The virtual development saves you time and effort because you can test the functions step by step, change parameters and test again without having to reprogram (flash) your ECU every time you make changes.
When you continue with the next step of testing on the actual target hardware you can be sure that your basic software is functionally correct, since you can rule out faults emanating from the hardware.

Debugging without real-time effects

The first tests with basic software on a target hardware often disclose open issues, among them potential bugs. Our EB tresos WinCore lets you narrow down the possible sources by ruling out hardware problems.  You can simply replicate your basic software configuration and build a virtual standard core with EB tresos WinCore and try to reproduce the issue on a Win32 platform.

If you can reproduce the problem, this indicates a functional or configuration problem. If the problem does not reproduce on a Win23 platform, the reason is likely a real-time effect, resource-effect or a hardware related problem.

Extension with DBG-module (EB tresos Debug & Trace)

As an additional helper for debugging, we offer an optional DBG-module, EB tresos AutoCore Dbg within the AUTOSAR stack. The module reads out debug and trace data from the stack as specified and scheduled by you. The data can be buffered in the internal ECU memory or transmitted the data via standardized bus interfaces (CAN, FlexRay, Ethernet) and even via a Lauterbach debugger. Thanks to corresponding points of instrumentation, you can test what is transferred from one software layer to another, for example. This enables you to trace e.g. every path within your stack to monitor all ports and to make sure that the signal is transmitted in the intended manner. In short, our DBG-module provides you with a quick overview of the system status and allows you to identify problems at an early stage without requiring detailed knowhow on AUTOSAR basic software modules.

Extension with customer-specific test modules

For even more in-depth tests, particular basic software modules can be replaced with test modules as specified by you. Modules can be swapped at all ICC-3 levels, every layer of the AUTOSAR stack.
These test modules send and receive data from the software components (SW-Cs) via the RTE (RunTime Environment) and enable you to inject faults via data manipulation.