Academic literature on the topic 'AUTOSAR'

The goal with the master thesis was to find a modular diagnostic platform to reuse in future Stoneridge Electronics projects. The master thesis started with Autosar as a consideration and the more we investigated about Autosar, the more drawn we were to it. This has led to the master thesis being devoted to Autosar. Autosar (AUTomotive Open System ARchitecture) is a standardized automotive software architecture, developed by vehicle manufacturers, third-party suppliers and tool developers. Autosar seems to be a very strong approach for many vehicle manufacturers. All major vehicle manufacturers are today members of Autosar. This thesis presents several ideas on how to migrate an existing architecture to Autosar. It is important to migrate to Autosar in a step by step matter because of numerous reasons. Two reasons are cost to migrate to Autosar and reliability issues. One of the goals of this master thesis was to develop one of many Autosar software components also called basic software modules in C. The basic software module written is the Can Transport Protocol, which is a part of the diagnostic platform. Programming the whole Can Transport Protocol is a large assignment and beyond the scope of a master thesis for one person. The programming part was split into two parts. According to Autosar, the Can TP used in the Autosar architecture is ISO 15765-2 USDT. This standard is used in many projects at Stoneridge Electronics. This master thesis also presents advantages and disadvantages of Autosar for Stoneridge Electronics. The conclusion is to be prepared for Autosar for numerous reasons. The major reason is the car manufacturer’s strong Autosar approach. Autosar is today well accepted by the major car manufacturers. There are however a few disadvantages with Autosar for Stoneridge Electronics and they are: • Cost to migrate to Autosar • Autosar requires more resources • Autosar has not yet considered the truck and bus industry.<br>Målet med detta examensarbete var att finna en modulär diagnostikplattform för smidig återanvändning i framtida Stoneridge Electronics projekt. Examensarbetet startade med Autosar som en alternativ lösning men blev snabbt lösningen på examensarbetet. Ju mer vi undersökte Autosar desto mer dragna till det blev vi. Detta har lett till att examensarbetet har blivit helt tillägnat åt Autosar. Autosar (AUTomotive Open System ARchitecture) är en standardiserad automobil mjukvaruarkitektur, utvecklad av biltillverkare, underleverantörer och verktygsutvecklare. Autosar verkar ha en väldigt stark frammarsch bland biltillverkare samt underleverantörer. Alla större biltillverkare är idag, i någon form, medlemmar i Autosar. Flera idéer presenteras hur man bör, på ett smidigt sätt, övergå till Autosar. Det är viktigt att man övergår till Autosar i en steg för steg process. Två anledningar är kostnaden att övergå till Autosar samt säkerhets frågor. Ett av många mål med examensarbetet var dessutom att utveckla en av många Autosar mjukvarukomponenter, så kallade ”basic software modules” i programmeringsspråk C. Mjukvarukomponenten som utvecklades var ”Can Transport Protocol” som är en del av diagnostikplattformen. Att programmera hela komponenten krävde att examensarbetet delades upp i två delar. Enligt Autosar är Autosars ”Can TP” baserad på ISO 15765-2 (USDT). Denna standard (USDT) är idag mycket väl accepterad hos Stoneridge Electronics och återanvänds flitigt i många Stoneridge Electronics projekt. Detta examensarbete presenterar fördelar och nackdelar med Autosar för Stoneridge Electronics. Slutsatsen är att vara förberedd med Autosar p.g.a. ett flertal anledningar. Den största anledningen är Autosars starka frammarsch bland biltillverkare och leverantörer. Autosar är idag väldigt accepterad bland de större biltillverkarna. Det finns dessvärre ett flertal negativa aspekter med Autosar för Stoneridge Electronics och dessa är: • Kostnaden att övergå till Autosar. • Autosar kräver mer resurser. • Autosar har ännu inte funderat på buss- och lastbilsindustrin.

Kurz nach der Jahrtausendwende führte die steigende Innovation und Komplexität von entwickelten Automotive-Systemen zum Anstieg der Anzahl von installierten elektronischen Systemen in Fahrzeugen. Dies wurde und wird noch immer durch die stetig wachsende Anzahl von rechtlichen und sicherheitstechnischen Vorgaben verstärkt. Da ein signifikanter Teil der Entwicklungskosten neuer Systeme in der Softwareentwicklung auf den im Automotive-Bereich verwendeten Steuergeräten (Electronic Control Unit, oder ECU) entsteht, wurde 2003 der AUTOSAR Developement Partnership ins Leben gerufen. Das Ziel dieser Arbeit ist, ein einheitliches System zu realisieren, in welchem eine vom Anbieter unabhängige Testbasis für AUTOSAR-konforme Tests ermöglicht werden soll, so dass ein Begleiten des Entwicklungsprozesses möglich ist. Es sollen sich Testmodule verschiedener Art am System anmelden und schließlich einem Arbeitsfluss zur Absicherung von AUTOSAR-Steuergeräten zur Entwicklungszeit hinzugefügt werden.

Durch die Einführung der Systemarchitektur AUTOSAR im automobilen Umfeld, können Applikationen unabhängig von der verwendeten Hardware oder der genutzten Kommunikationssysteme entwickelt werden. Dadurch können Funktionen wieder verwendet werden, was Zeit und Ressourcen einsparen kann. So können Funktionen, die sich etabliert haben, in späteren Entwicklungen durch Anpassung in der Konfiguration genutzt werden ohne dabei den Quellcode zu ändern. Jedoch stellt die große Zahl an Parametern in der AUTOSAR Architektur große Herausforderungen an die Absicherung eines Steuergerätes. Dieser Aspekt wird durch eine meist heterogene Toollandschaft verstärkt. Umso wichtiger ist es, dass während der Entwicklung von AUTOSAR Steuergeräten statische Analysen die Software und die Konfiguration überprüfen, um so die Softwarequalität sicherstellen zu können. In der Masterarbeit werden eine Menge von AUTOSAR spezifischen statischen Analysen für die einzelnen Schichten eines AUTOSAR Steuergerätes entwickelt. Für die Analyse werden Einstellungsdateien (nach Standard und Firmenspezifische) und der Quellcode an sich genutzt. Die Analysen geben optional Korrekturvorschläge an den Entwickler. Die Umsetzung erfolgt in einem C# Prototyp und wird an der Lichtsteuerung des Automotive Demonstrator YellowCar angewendet werden.

AUTOSAR was created as a standard software infrastructure to be able to fulfill a very large amount of requirements. These days, more and more OEMs are trying to introduce AUTOSAR in their products. Since there are a large amount of diagnostic IDs needed in the Engine control unit and also a huge effort is necessary to configure the ECU, it is very much important to have a tool to generate some parts of the Engine Control Unit software, most importantly the diagnostics software. Diagnostic Communication manager is one such AUTOSAR module which deals with a huge amount of diagnostic data identifiers. Also at BEG, In the actual Non-AUTOSAR Bosch Automotive software, there are a number of different features that are needed and expected in the future AUTOSAR software. The aim of this thesis is to develop a tool that successfully introduces AUTOSAR in the BEG projects with all the necessary features and that is best in terms of Usability, Maintainability, and Improvability. This tool has to generate the complete AUTOSAR Diagnostic communication manager software with all the necessary features. The work can be divided into two parts. The first part includes a complete analysis of the existing tools that are used to generate configuration files and code. Then, List out all the possibilities of each tool, find their advantages and disadvantages and compare each of the tools, either individually or as a combination of tools. This is followed by documenting the choice of best way to generate AUTOSAR DCM with all the necessary features. In the second part, the implementation is carried out. After the best tool is chosen, the implementation of the features for that particular tool is planned accordingly so that it generates the DCM software. Implementation is made and then it is tested with the existing test bench.

Today there are more cars on the road than ever before, the automotive industry is continually expanding and adapting to meet the need of new technologies. To improve complexity management and reduce engineering time and cost ​Automotive Open System Architecture​, better known as AUTOSAR, has been introduced which aims to standardize Electronic Control Units (​ECUs)​ . Today the AUTOSAR standardization is used for the automotive industry, the purpose of the thesis is to investigate whether the standard can be used for something which has no direct connection to the automotive industry. The work done in the report is giving background information about AUTOSAR and the project is using AUTOSAR to visualize real-time data from the web on a LED-sheet. In this project a physical visualization board has been created and the code was written within the integrated software development environment Arctic Studio and its tools, the visualization board will be used at the ARCCORE office in Linköping.<br>Idag finns det fler bilar på vägarna än någonsin tidigare, fordonsindustrin expanderar ständigt och anpassar sig efter behovet av ny teknik. För att förbättra komplexitets hanteringen och minska tillverkningstider och kostnader så har Automotive Open System Architecture, närmare känt som AUTOSAR, införts som har målet att standardisera elektroniska styrenheter (ECUn). Idag används AUTOSAR-standardiseringen för fordonsindustrin, vad projektet kommer att utforska är att se om man kan använda standarden för något som inte har någon direkt koppling till fordonsindustrin. Rapporten ger en förklaring om AUTOSAR, i projektet så används AUTOSAR för att visualisera realtidsdata från webben på en LED-karta. I detta projekt har en fysisk visualiseringstavla skapats där kod skrevs inom den integrerade mjukvaruutvecklingsmiljön Arctic Studio, visualiseringstavlan kommer att användas på ARCCOREs egna kontor i Linköping.

Die Möglichkeit, komplexe Applikationen für Steuergeräte zu entwerfen und zu implementieren wird durch die Systemarchitektur AUTOSAR stark vereinfacht. Ein Applikations-Entwickler implementiert nur noch die reine Funktionalität, während der Teil, der die Interaktion mit der Hardware ermöglicht, von entsprechenden Werkzeugen automatisch generiert wird. Viele Hersteller bieten hierfür Produkte, die vom grafischen Entwurf der Software bis zu finalen Tests des fertigen Steuergeräte-Codes alles abdecken. Zentrales Element ist hierbei immer die AUTOSAR-XML, welche alle Informationen zur Anwendung aufnimmt. Dadurch können verschiedene Zulieferer einzelne Module zu einer Anwendung beisteuern. Durch den technologischen Fortschritt und die Integrierbarkeit von verfügbaren Teilsystemen oder einzelnen Komponenten werden eingebettete Systeme immer komplexer ([Har02]). Daher müssen neue Spezifikationen erstellt und demzufolge neue AUTOSAR-Versionen publiziert werden. Die Hersteller müssen sich an diese neuen Vorgaben halten, um so konkurrenzfähig auf dem Markt zu bleiben ([ZS14]).

Automotive Ethernet is a newly introduced in-vehicle bus that allows unicast communication between ECUs. It is based on the OSI model of Ethernet, with a few modifications on the physical layer and newly introduced application protocols. AUTOSAR, a consortium of automotive OEMs, Tier-1 suppliers and tool vendors has defined a standard software architecture that simplifies the ECU software development with its well defined software specifications and APIs. The Automotive Ethernet stack is now an integral part of the latest AUTOSAR specification release 4.2. Infineon Aurix TriCore TC27x microcontroller is a popular board used in ADAS applications. The board has support for Fast Ethernet. This thesis investigates the setting up of an Ethernet communication on the TriCore board running under AUTOSAR software architecture. The various modules of the AUTOSAR Ethernet stack are familiarized and configured. This is followed up by validating the implementation on the Ethernet physical layer. The validation is based on a real Ethernet communication between the TriCore board and the Vector VN5610 network interface card. TCP and UDP based connections between the AUTOSAR compliant board and the VN5610 are tested and validated. A test suite for evaluating the protocol conformance of the AUTOSAR Ethernet stack exists at Bertrandt. The final step of this thesis involved the execution strategies for this test suite.

In the automotive industry today, embedded systems have reached a level of complexity which is not maintainable with the traditional approach of design- ing automotive embedded systems. For this purpose, many of the worlds leading automotive manufacturers have formed an alliance to apprehend this problem. This has resulted in AUTOSAR, an open standardized architecture for automotive embedded systems, which strives for increased flexibility and safety regulations. This thesis will explore the possibilities of implementing a CAN Communication stack using the AUTOSAR architecture and its corresponding methodology. As a result of this thesis, a complete AUTOSAR CAN communication stack has been implemented, as well has a simulator application with the purpose of testing its functionality.

Safety has been always been an important part, irrespective of the field of work that it accounts for. The functional safety standard that is currently being used in the automotive domain is the ISO 26262. This is an adaptation of the IEC 61508 safety standard. It is directed as a basic functional safety standard for a variety of industries. The version of ISO 26262 that is used in this thesis is the final draft released in January, 2011. In this thesis, various parts of the ISO 26262 functional safety standard are considered in order to understand the differences and interdependencies between them. The parts of ISO 26262 that are treated are as follows; Part 1: Vocabulary, Part 3: Concept phase, Part 4: Product development at the system level, Part 6: Product development at the software level and Part 9: Automotive Safety Integrity Level (ASIL)-oriented and safety-oriented analysis. During the entire course of this thesis the ISO 26262 standard is evaluated and the experience gained from it is jotted down. The understanding gained during this thesis about the ISO 26262 can be applied to ongoing or new development processes. As safety can never be overlooked, the wisdom that belongs to the ISO 26262 can be generously used into embedded systems that demand certain levels of safety.

Automotive embedded systems are going through a major change, both in terms of how they are used and in terms of software and hardware architecture. Much more powerful and rapidly evolvable hardware is expected, paralleled by an accelerating development rate of the control software. To meet these challenges, a software standard, AUTOSAR, is gaining ground in the automotive field. In this work, experiences from porting AUTOSAR to a high performance embedded system, Raspberry Pi, are collected. The goal is both to present experience on the process of AUTOSAR porting and to create an AUTOSAR implementation on a cheap and widely accessible hardware platform, making AUTOSAR available for researchers and students.