Search Results

Vehicle Security means protecting potential threats, unintended malfunction and illegal tuning. In addition, it has become a more important issue on an automotive system as it is directly connected to the driver and pedestrian's life. Automotive industry significantly needs to enhance security policies to prevent attacks from hackers. Nevertheless, in some systems, performance still has to be considered at first when security functions are implemented. Especially, in case of Engine Management System (EMS), fast engine synchronization for starting should be considered as the first priority. This paper is intended to show an approach to design efficient secure boot implementation for EMS. At the beginning of this paper, the concept of secure boot is explained and several use cases are introduced according to execution modes, such as the foreground and background secure boot modes. As a next step, engine starting process by EMS is explained.

In the early 1980s, an oxygen sensor was applied to improve the fuel efficiency of automotive embedded systems. Currently, the complexity of software development has being increased due to the emergence of various requirements and the electronic control devices to ensure the safety and convenience of the driver. The high-performance hardware embedded in the ECU is a big issue for the automobile industry. OEMs, TIERs, tool providers, and the others are aiming at a variety of unit reusability, including software and hardware, based on the plug-and-play architecture concept. It is enhancing the quality attributes (safety, performance, real-time) of various perspectives. Furthermore, international standard process (ISO 26262, A-SPICE) does not provide a direct methodology for dealing with requirements refinement procedures, standard specification methods, and traceability of extracts.

These days in automotive industry, AUTOSAR has been increasingly used as a standard and unified software platform as vehicle electronics have becoming more variety, more performance and more complicated. MCAL is a software driver which belongs to lowest level in AUTOSAR software structure. MCAL directly access the microcontroller hardware and is provided by microcontroller supplier like Infineon to handle microcontroller peripherals. And in cases for special dedicated functions of microcontroller or for special requirements, Complex Device Driver could be used as legacy software instead of MCAL. The paper is structured as follows: First, the SPI requirements for vehicle applications such as chassis will be shown. Then, the current AUTOSAR specification for SPI MCAL will be explained in detail. Next, the sequential SPI communication and the parallel SPI communication with multi-nodes will be discussed.

In automotive software developments, since the types of software functionalities are depending on automotive engineering domains such as powertrain, body, and chassis, software logic and data processing, code complexity, and its reliability are also depending on them. Therefore, it has some challenges that monolithic code quality measures are applied to software code for all domains. In addition, imprecise criteria for the measures also can make software developers and testers confused whether their code verifications are enough or not. This paper proposes domain-specific code quality measures and precise criteria by combining a new functionality model, named Abstract Function Model (AFM), and shows results of automotive software functionality analysis using the model. Using 8 real automotive software projects, we derived statistics of software code on specific automotive engineering domain and identified code quality measures from the statistics.