EB tresos

Interview with Florian Wandling on AUTOSAR 4.0

Marlene Gössinger — Fri, 06 Apr 2012 09:08:42 +0000

Florian Wandling, product line manager, is interviewed by ICC Media during the Embedded World 2012 in Nuremburg about AUTOSAR 4.0. Hear about the main advantages of AUTOSAR 4.0 and how it contributes also to your success.

Watch the interview

Meet us at the Mathworks Automotive Conference 2012

Florian Reindl — Fri, 23 Mar 2012 10:36:42 +0000

Mathworks is inviting engineers and project leaders across the automotive industry for an automotive conference in Stuttgart, Germany. Among the highlights are a keynote speech from Dr. Andreas Titze, Head of E/E Architecture and Networks at Volkswagen, presentations and case studies of international OEMs and Tier1 suppliers.

Meet our experts on AUTOSAR 4.0 basic software tooling in the exhibition forum.

For registration visit the Mathworks event page.

EB AUTOSAR 4.0 Days – Road ready with AUTOSAR 4.0

Florian Reindl — Wed, 11 Jan 2012 12:21:46 +0000

>>Road ready with AUTOSAR 4.0<<

True to this motto we are pleased to invite you to one of our EB AUTOSAR 4.0 Days.

This year sees the premier of our EB AUTOSAR Days. We created them to actively cultivate the communication with you.

AUTOSAR 4.0 ready for mass production soon. Some car makers such as BMW and Volvo have already made the strategic decision to use fully AUTOSAR 4.0 compliant software in future production projects.

Against this background our experts on AUTOSAR and Functional Safety will encourage you with their lectures to an exchange of experiences. During the breaks you will have time to deepen your conversations with various interesting guests from your profession.

Please save the date:

Munich – 31.01.2012 in the Kempinski Airport Hotel

Stuttgart – 01.02.2012 in the Golden Leaf Airport Hotel

Frankfurt – 07.02.2012 in the Steigenberger Airport Hotel

Paris – 14.02.2012 in the BEST WESTERN CDG Airport

Start: 9:30 a.m. – End: 2:00 p.m.

The following agenda topics are covered:

What’s new in AUTOSAR 4.0

AUTOSAR 4.0 software and tooling support

AUTOSAR ready for OEM

Joining AUTOSAR and Functional Safety

Please register by contacting us using the keyword AUTOSAR 4.0 Days.

If you have any questions about this event please do not hesitate to contact Mr. Christian Dürr on extension 09131-7701 6179.

Please feel free to forward this invitation to interested colleagues.

We are looking forward to your registration.

Meet our AUTOSAR 4 and Functional Safety experts at the embedded world 2012

Florian Reindl — Fri, 16 Dec 2011 14:38:06 +0000

The embedded world exhibition and conference is the world´s biggest exhibition of its kind and the meeting-place of the international embedded community. Come and visit us at our booth 4-206 in hall 4 to learn more about EB’s automotive software.

Nuremberg, Germany
February 28th – March 1st, 2012

Our main topics at ew 2012 are:

• How to get AUTOSAR 4.0 and functional safety road ready

• How EB GUIDE 5 accelerates your HMI development

• How easily you can develop Driver Assistance algorithms with EB Assist ADTF

• How versatile our navigation solution EB street director is

To book a meeting with us, please contact us.

We look forward to meeting you there.

Comparing and merging two arbitrary XDM files using EB tresos Studio

Florian Reindl — Mon, 12 Dec 2011 16:30:22 +0000

In our latest edition of our tips and tricks for EB tresos Studio, we would like to show you how you can facilitate the collaboration within your development team.

In the latest version, our basic software configuration tooling EB tresos Studio 12 enables you to compare and merge two arbitrary XDM files.

Celebrating more than 100 EB Flashbuilder licences

Florian Reindl — Mon, 12 Dec 2011 16:09:15 +0000

Our business department “ECU Off-Board Solutions” just shipped the 100th license of the EB Flashbuilder. Congratulations!

The reason for this success can be seen in the tool’s usability which precisely meets the customers’ needs updating embedded software in R&D departments, production and after sales.

Our EB Flashbuilder allows OEMs, Tier1s and other suppliers to create flash containers according to the ASAM Open Diagnostic Data Exchange (ODX) standard easily.

It comes with a graphical wizard that automates all the necessary creation steps from object code to the finished ODX container. Users need no special know-how on Extensible Markup Language (XML) or ASAM ODX.

Project Managers told us that the EB Flashbuilder is a tool combining a user friendly configuration with a fully automated build process. By encapsulating all complexity it enables the users to concentrate on their core business and, thus, creates additional freedom.

EB working with IBM on software development solution for AUTOSAR

Florian Reindl — Tue, 06 Dec 2011 16:19:34 +0000

EB and IBM Software Will Help TRW, Carmakers and Suppliers Get to Market Faster with New Automotive Test System

Erlangen, Germany, November 30, 2011 – EB (Elektrobit), a leading developer of cutting edge embedded technology solutions for the automotive and wireless industries, announced today a software development initiative with IBM to deliver an integrated development platform that allows carmakers and suppliers to manage the growing complexity of Electronic Control Units (ECUs) software in automotive development, speed-up development cycles and standardize software to increase re-usability across car platforms.

“A month ago, EB has delivered the first compliant software development toolset for AUTOSAR 4.0 to carmakers and suppliers”, said Dr. Jochen Schoof, Vice President ECU Software and Tools at EB. “The project with IBM to integrate its application development tools on top of EB tresos basic software framework is another proof for the strong momentum on the way to industry-wide AUTOSAR 4.0 adoption.”

AUTOSAR is a leading automotive standard that is endorsed by carmakers, suppliers, embedded device manufacturers and software providers. It is rapidly gaining adoption in the automotive industry as it allows re-using software across all car platforms worldwide. The standard reduces the complexity of design and simplifies the collaboration between engineering teams of all parts of the ecosystem, from hardware to software.

EB and IBM will deliver an integrated development platform based on AUTOSAR 4.0. TRW, a leading supplier of automotive solutions supports this joint project and anticipates significant tangible benefits from the interoperability between IBM Rational Rhapsody and EB tresos. “In many cases the complexity and overhead required for AUTOSAR compliance has been significantly underestimated,” said Mark Haller, Director global software engineering. “This partnership between IBM and EB will provide us with a unified solution to bridge the gap between E/E and ECU electronic and software development, test and traceability.”

EB is integrating IBM Rational Rhapsody, a graphical modeling tool for complex software systems, with EB tresos, a tool that provides a framework for basic software configuration and deployment down to basic hardware control components within a car. This integrated platform benefits the automotive industry by providing access to a tested, end-to-end ECU software development tool-chain. IBM’s engineering tools allow systems modeling and design applications within the AUTOSAR 4.0 software architecture. Combined with EB tresos, engineers have the ability to test their design and software even before the future hardware is available. The layered approach and defined interfaces reduces the risk associated with the complexity of automotive software projects.

“As automotive systems design and development becomes increasingly complex, our customers are demanding interface standardization and extensive tool interoperability,” said Meg Selfe, vice president, Complex and Embedded Systems, IBM. “Developers working within the AUTOSAR standard for automotive development projects can now benefit from the high degree of software interchangeability and reusability through the combined offerings of IBM and EB.”

AUTOSAR solutions from EB are available immediately.

New AUTOSAR training dates

Florian Reindl — Wed, 30 Nov 2011 13:12:21 +0000

This seminar provides an insight into the function and interaction of AUTOSAR software modules. In addition to the new possibilities offered by AUTOSAR applications, we will also introduce migration scenarios for existing applications.

More details

The dates for 2012 are as follows:

14th – 16th February

24th – 26th April

26th – 28th June 2012

18th - 20th September 2012

20th – 22nd November 2012

The training location is EB Germany Erlangen (Germany), Am Wolfsmantel 46.

Größere Kartenansicht

Microkernel OS – smart meets ISO 26262 requirements

Florian Reindl — Mon, 14 Nov 2011 16:02:42 +0000

Our experts on AUTOSAR operating systems (OS) presented the article “An AUTOSAR-compatible microkernel for systems with safety-relevant components” at the annual Gesellschaft für Informatik e.V. real-time conference (”Echtzeit 2011″) in Boppard.

The article describes in detail the approach we took to develop an AUTOSAR-compatible OS sofware module that uses a Microkernel developed to meet the steep requirements of the ISO26262 standard.

Learn more and read the full article in the conference proceedings availiable from “Springer” publications or learn more about our functional safety portfolio.

Meeting the requirements of the ISO 26262

Developing software to the rigorous standards required for safety-relevant systems is costly and time-consuming. Standards such as ISO26262, as used in the automotive domain, demand that rigorous procedures be applied to the development of all software that could interfere with the safety-relevant functions of an electronic control unit (ECU).

These procedures apply to all phases of development, from the definition of requirements through design, implementation, test,verifcation and final assessment. These rigorous procedures are very time-consuming and costly. In practice, it may not be possible to develop a system to these standards within reasonable timescales.

An approach that is commonly used in many fields is to isolate software components from each other. By this means a failure in one component cannot interfere with the behaviour of another. Alternatively, interference can be detected and appropriate action can be taken. This approach is known as providing “freedom from interference” for the safety-relevant components.

The road to freedom from interference

Providing freedom from interference for the safety-relevant AUTOSAR Software Components needs some kind of protection mechanism. AUTOSAR would appear to be the logical place to provide this protection, but in the AUTOSAR model the operating system (OS), the basic software stack and the Run-Time Environement (RTE) run with the same privileges. This would mean that the whole of AUTOSAR would need to be developed to the very rigorous standards of ISO26262. However, a full AUTOSAR implementation is a large body of software, much of it generated to enable a high level of configurability. Developing this amount of software to the uncompromising procedures required for safety-relevant systems would be a herculean task, especially since the code generators would also need to be verified. An alternative solution must therefore be found.

Microkernel OS - smart meets ISO 26262 requirements

A full implementation of an AUTOSAR OS has the memory protection features common in other operating systems that are often used as means to prevent interference between software components. The memory protection mechanism isolates the components of a system to prevent unintended interactions between them, thus removing the necessity to develop all the components of the system to the high standards required for the safety components.

An AUTOSAR OS implementation would certainly provide the necessary protection, but the development of this amount of software to rigorous safety standards would be very costly, as mentioned before.
A minimal operating system kernel, a “Microkernel”, can be used to isolate not only the basic software and Run-Time Environment (RTE) but also much of the functionality of the OS module.

Using the approach outlined therein it we have created an operating system that is functionally compatible with the AUTOSAR standard. This OS can be used in safety-relevant systems without compromising safety but also without incurring the high costs of developing the whole OS to the elevated requirements of the ISO26262 standard.

EB is ready for ISO 26262 Functional Safety

Florian Reindl — Mon, 07 Nov 2011 13:16:08 +0000

We provide concepts and mechanisms for safety-related ECU software. Our EB tresos AutoCore OS provides a solution to the challenges of ISO 26262.

We support companies in the development and integration of applications and functions in safety-related systems. For this purpose, we have already put concrete strategies and mechanisms into place.

To enable the efficient integration of ECU software despite additional efforts to meet safety requirements, we have created our own concepts and mechanisms that take the required safety criteria into account. These safety mechanisms are realized in the following products:

EB tresos Safety OS - Protects safety-related data from violations according to the sandbox principle (data protection).

EB tresos Safety E2E Protection - Monitors internal ECU data exchange and helps to achieve reliable data communication beyond the ECU (Communication Protection).

EB tresos Safety Time Protection – Detects when safety related functions are executed at the wrong time or in wrong sequence (Control Flow Monitoring). If this happens, the ECU goes into secure mode.

AUTOSAR 4.0 also supports multicore microcontrollers. On the one hand, multicore processors have lower power consumption compared to the same number of single core processors; on the other hand multicore solutions are used in safety-related applications to increase safety through redundancy.

EB tresos AutoCore OS (multicore) is designed to solve such challenges. For example, to secure safety-critical applications, the second core of a multicore processor monitors the results of the first core. Another possibility is that control variables are calculated in parallel within the multicore using a second, independent software. In addition, modern security processors with active hardware monitoring of redundant, coupled cores are supported (lockstep).

Often third-party IP, which was not designed according to the required ASIL (Automotive Safety Integrity Level), has to be integrated into a controller executing safety-related functions. Because the source code is not accessible and the behavior therefore cannot be verified at the code level, freedom of interference with regard to the data is established by encapsulating the function – the Data Protection. In such an encapsulated function, access to data is restricted to a very limited area and permanently monitored.

Our Data Protection concept provides memory protection in the operating system and RTE so that memory areas which contain safety-related data cannot be inadvertently changed by other software parts. This monitoring can prevent code that is not known in detail – black box software – from affecting the data of other functions of the same ECU or other con-trol devices in case of a fault.