Search Results

Recently, vehicle networks have increased complexity due to the demand for autonomous driving or connected devices. This increasing complexity requires high bandwidth. As a result, vehicle manufacturers have begun using Ethernet-based communication for high-speed links. In order to deal with the heterogeneity of such networks where legacy automotive buses have to coexist with high-speed Ethernet links vehicle manufacturers introduced a vehicle gateway system. The system uses Ethernet as a backbone between domain controllers and CAN buses for communication between internal controllers. As a central point in the vehicle, the gateway is constantly exchanging vehicle data in a heterogeneous communication environment between the existing CAN and Ethernet networks. In an in-vehicle network context where the communications are strictly time-constrained, it is necessary to measure the delay for such routing task.

Several external networks like telematics, and SOTA and many in-vehicle networks by gateways and domain controllers have been increasingly introduced. However, these trends may potentially make many critical data opened, attacked and modified by hackers. These days, vehicle security has been significantly required as these vehicle security threats are related to the human life like drivers and pedestrians. Threat modeling is process of secure software development lifecycle which is developed by Microsoft. It is a systematic approach for analyzing the potential threat in software and identifying the security risk associated with software. Through threat modeling, security risk is be mitigated and eliminated. In vehicle software System, one of vulnerability can affect critical problem about safety. An approach from experience and hacking cases is not enough for analyzing the potential threat and preparing new hacking attack.

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.

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 Engine Management System, more accurate control is required to improve engine performance. Especially generating the precise ignition signal has a direct effect on better engine performance. In the beginning of this paper, a basic software structure to synchronize the engine crank signal and generate ignition signals will be explained. Several cases which can generate dwell timing error will be introduced based on this software structure. In addition, each impact level for each error case will be described. For cases of major error, compensation ways will be proposed in order to obtain more accurate dwell timing. The compensation ways by both microcontroller hardware and user software will be explained in detail. In conclusion, this paper will show the accuracy of ignition signal which implements proposed compensation ways that can be improved as compared to conventional ignition signal.

Multi-core systems are adopted quickly in the automotive domain, Proof of concepts have been implemented for power train, body and chassis, involving hard real-time constraints. However, depending on the degree of integration, it can be costly, especially in those cases where existing single-core software has to be migrated over. Furthermore, there seems to be a high level of uncertainty, whether a found solution, with regards to partitioning, mapping and orchestration of software is close to an optimum solution. Some integrated solutions demonstrate considerably less performance, for instance due to communication overhead compared to execution on single-core systems. This paper discusses a methodology, as to how to effectively and efficiently investigate the software architecture design space for multi-core software development.