Search Results

In-vehicle communication faces increasing bandwidth demands, which can no longer be met by today's MOST150, FlexRay or CAN networks. In recent years, Fast Ethernet has gained a lot of momentum in the automotive world, because it promises to bridge the bandwidth gap. A first step in this direction is the introduction of Ethernet as an On Board Diagnostic (OBD) interface for production vehicles. The next potential use cases include the use of Ethernet in Driver Assistance Systems and in the infotainment domain. However, for many of these use cases, the Fast Ethernet solution is too slow to move the huge amount of data between the Domain Controllers, ADAS Systems, Safety Computer and Chassis Controller in an adequate way. The result is the urgent need for a network technology beyond the Fast Ethernet solution. The question is: which innovation will provide enough bandwidth for domain controllers, fast flashing routines, video data, MOST-replacement and internal ECU buses?

A main challenge when developing next generation architectures for automated driving ECUs is to guarantee reliable functionality. Today’s fail safe systems will not be able to handle electronic failures due to the missing “mechanical” fallback or the intervening driver. This means, fail operational based on redundancy is an essential part for improving the functional safety, especially in safety-related braking and steering systems. The 2-out-of-2 Diagnostic Fail Safe (2oo2DFS) system is a promising approach to realize redundancy with manageable costs. In this contribution, we evaluate the reliability of this concept for a symmetric and an asymmetric Electronic Power Steering (EPS) ECU. For this, we use a Markov chain model as a typical method for analyzing the reliability and Mean Time To Failure (MTTF) in majority redundancy approaches. As a basis, the failure rates of the used components and the microcontroller are considered.

In addition to basic switching functionality, smart power switches mainly provide diagnostic and protection functions, e.g. for short circuits to the load, which makes it all the more surprising that short circuit protected smart switches have been used for years in automotive applications without there being a precise definition of a short circuit. This article describes what Infineon has done to fill this gap. It was first necessary to define the kind of short circuits likely to occur in automotive applications and to specify the use and operating points of the smart switches. The next logical step was the standardization of the test circuit and application conditions in the AEC (Automotive Electronics Council) to allow an industry-wide comparison of the test results.

More than ever, microcontroller performance in cars has a direct impact on the driving experience, on compliance with improved safety, ever-stricter emissions regulations, and on fuel economy. The simple microcontrollers formerly used in automobiles are now being replaced by powerful number-crunchers with incredible levels of peripheral integration. As a result, performance can no longer be measured in MIPS (Millions of Instructions Per Second). A microcontroller's effectiveness is based on coherent partitioning between analog and digital, hardware and software, tools and methodology. To make an informed choice among the available devices, the designer needs benchmarks that are specific to automotive applications, and which provide a realistic representation of how the device will perform in the automotive environment.

The increasingly stringent requirements in relation to emission reduction and onboard diagnostics are pushing the Chinese automotive industry toward more innovative solutions and a rapid increase in electronic control performance. To manage the system complexity the architecture will require being well structure on hardware and software level. The paper introduces GEMS-K1 (Gasoline Engine Management System - Kit 1). GEMS-K1 is a platform being compliant with Euro IV emission regulation for gasoline engines. The application software is developed using modeling language, the code is automatically generated from the model. The driver software has a well defined structure including microcontroller abstraction layer and ECU abstraction layer. The hardware is following design rules to be robust, 100% testable and easy to manufacture. The electronic components use the latest innovation in terms of architecture and technologies.

The increasing legal requirements for safety, emission reduction, fuel economy and onboard diagnosis systems push the market for more innovative solutions with rapidly increasing complexity. Hence, the embedded systems that will have to control the automobiles have been developed at such an extent that they are now equivalent in scale and complexity to the most sophisticated avionics systems. This paper will demonstrate the key elements to provide a powerful, scalable and configurable solution that offers a migration pass to evolution and even revolution of automotive Sensors and Sensor interfaces. The document will explore different architectures and partitioning. Sensor technologies such as magnetic field sensors based on the hall effect as well as bulk and surface silicon micro machined sensors will be mapped to automotive applications by examples. Functions such as self-test, self-calibration and self-repair will be developed.

Driven by factors like consumption, power output per liter, comfort and more stringent exhaust gas standards the powertain control area, has developed rapidly in the last decades. This trend has also brought with it many innovations in the ignition application. Today we can see a trend to Pencil-coil or Plug-top-coil ignition systems. The next step in system partitioning is to remove the power driver from the ECU and place it directly in/on the coil body. The advantages of the new partitioning - e.g. no high voltage wires, reduced power dissipation on the ECU - are paid with different, mainly tougher requirements for the electronic components. By using specialized technologies for the different functions - IGBT for switching the power, SPT for protection, supply and diagnostics - in chip-on-chip technology all required functions for a decentralized ignition system can be realized in a TO220/ TO263 package.

This paper outlines the results of a study performed to analyze the mission of TTCAN from applications to products for automotive systems. As commonly acknowledged communication is one of the key elements for future and even present systems such as an automobile. A dramatically increasing number of busses and gateways even in low- to midrange vehicles is putting significant burden upon the validation scenario as well as the cost. Accordingly, numerous new initiatives have been started worldwide in order to find solutions to this; some of them by the definition of enhanced or new protocols. This paper shall have a look particular on the new standard of TTCAN (time-triggered communication on CAN). This protocol is based on the CAN data link layer as specified in ISO 11898-1 and may use standardized CAN physical layers such as specified in ISO 11898-2 (high-speed transceiver) or in ISO 11898-3 (fault-tolerant low-speed transceiver).

Driven by the growing internet and remote connectivity of automobiles, combined with the emerging trend to automated driving, the importance of security for automotive systems is massively increasing. Although cyber security is a common part of daily routines in the traditional IT domain, necessary security mechanisms are not yet widely applied in the vehicles. At first glance, this may not appear to be a problem as there are lots of solutions from other domains, which potentially could be re-used. But substantial differences compared to an automotive environment have to be taken into account, drastically reducing the possibilities for simple reuse. Our contribution is to address automotive electronics engineers who are confronted with security requirements. Therefore, it will firstly provide some basic knowledge about IT security and subsequently present a selection of automotive specific security use cases.

Connecting mobile communication channels to vehicles’ networks is currently attracting engineers in a wide range. Herein the desire of vehicle manufacturers to remotely execute software updates over the air (SOTA) within electronic control units (ECU) is probably the field of highest attention at the moment. Today software updates are typically done at vehicle service stations and connection the vehicles electronic network via the onboard diagnosis (OBD) interface to a service computer. Herby the duration of the update is invisible to the user, as this happens during standard service appointments. With introduction of SOTA, these updates become very convenient to the customer and can lead to higher customer satisfaction levels. SOTA can be made transparent to the user however the method of implementation can affect the user experience.

Integration scenarios for ECU software become more complicated, as more constraints with regards to timing, safety and security need to be considered. Multi-core microcontrollers offer even more hardware potential for integration scenarios. To tackle the complexity, more and more model based approaches are used. Understanding the interaction between the different software components, not only from a functional but also from a timing view, is a key success factor for high integration scenarios. In particular for multi-core systems, an amazing amount of timing data can be generated. Usually a multi-core system handles more software functionality than a single-core system. Furthermore, there may be timing interference on the multicore systems, due to the shared usage of buses, memory banks or other hardware resources.

The infrastructure in modern cars is a heterogeneous and historically grown network of different field buses coupling different electronic control units (ECUs) from different sources. In the past years, the amount of ECUs in the network has rapidly grown due to the mushrooming of new functions which historically were mostly implemented on a one-ECU-per-function basis resulting in up to a hundred ECUs in fully equipped luxury cars. Additionally, new functions like parking assist systems or advanced chassis control functions are getting increasingly complex and require more computing power. These two facts add up to a complex challenge in development. The current trend to host several functions in single ECUs as integration platforms is one attempt to address this challenge. This trend is supported by the increased computing power of current and upcoming multi-core microcontrollers.

The number of safety critical automotive applications employing high current brushless motors continues to increase (Steering, Braking, and Transmission etc.). There are many benefits when moving from traditional solutions to electrically actuated solutions. Some of these benefits can include increased fuel economy, simplified vehicle installation and packaging, increased feature set, improved safety and/or convenience, simplified unit assembly and modular testability prior as well as during vehicle manufacturing. The trend to implement brushless motors in these applications (which require electronically controlled commutation) has also brought with it the need for powerful inverters, which primarily consist of Power MOSFETs and MOSFET Driver ICs. This paper reviews the challenges associated with the design of safety critical electronic systems which combine sensing, control and actuation.

For the past approximately 20 years, the Serial Peripheral Interface (SPI) has been the established standard for serial communication between a host or central microprocessor and peripheral devices. This standard has been used extensively in control modules covering the entire spectrum of automotive applications, as well as non-automotive applications. As the complexity of engine control modules grows, with the number of vehicle actuators being controlled and monitored increasing, the number of loads the central microprocessor has to manage is growing accordingly. These loads are typically controlled using discrete and pulse-width modulated (PWM) outputs from the microcontroller when real-time operation is essential or via SPI when real-time response is not critical. The increase of already high pin-count on microcontrollers, the associated routing effort and demand for connected power stages is a concern of cost and reliability for future ECU designs.

This paper will give an overview of multicore in automotive applications, covering the trends, benefits, challenges, and implementation scenarios. The automotive silicon industry has been building multicore and multiprocessor systems for a long time. The reasons for this choice have been: increased performance, safety redundancy, increased I/O & peripheral, access to multiple architectures (performance type e.g. DSP) and technologies. In the past, multiprocessors have been mainly considered as multi-die, multi-package with simple interconnection such as serial or parallel busses with possible shared memories. The new challenge is to implement a multicore, micro-processor that combines two or more independent processors into a single package, often a single integrated circuit (IC). The multicores allow a computing device to exhibit some form of thread-level parallelism (TLP).

The C166 family, based on a 16-bit core; it is nowadays an enormous success in automotive, in particular in PowerTrain. This component is the right answer for the automotive real time applications of today. It is with both, automotive customer requirements and a long automotive experience in semi-conductors that this new generation 32-bit family is borne. The objective of this document is to provide and comment on automotive requirements in terms of the new micro-controller, to show the benefits for the applications and explain how the AUDO architecture fulfils these requirements.

Introduction The introduction of Ethernet and Gigabit Ethernet [2] as the main invehicle network infrastructure is the technical foundation for different new functionalities such as piloted driving, minimizing the CO2- footprint and others. The high data rate of such systems influences also the used microcontrollers due the fact that a big amount of data has to be transferred, encrypted, etc. Figure 1 Motivation - Vehicles will become connected to uncontrolled networks The usage of Ethernet as the in-vehicle-network enables the possibility that future road vehicles are going to be connected with other vehicles and information systems to improve system functionality. These previously closed automotive systems will be opened up for external access (see Figure 1). This can be Car2X connectivity or connection to personal devices. Allowing vehicle systems to communicate with other systems that are not within their physical boundaries impose a previously non-existing security problem.

In recent years, we see more and more ECUs integrating a huge number of application software components. This process mostly results from the increasing amount of so called in-house software in various fields like electric-drive, chassis and driver assistance systems. The software development for these systems is partially moved from the supplier to the car manufacturers. Another important trend is the introduction of new network architectures intending to meet the growing communication requirements. For such ECUs the software integration scenarios become more complicated, as more quality of service requirements with regards to timing, safety and security need to be considered [2]. Multi-core microcontrollers offer even more potential variants for integration scenarios. Understanding the interaction between the different software components, not only from a functional, but also from a timing view, is a key success factor for modern electronic systems [6,7,8,9].

End of Line tests are brief set of tests intended to evaluate ECU's in order to ensure correct functioning of its intended functionality. As these tests are executed on the production line, available time to perform these tests is limited. On one hand, faster production demands require these tests and its framework to be designed in a time optimized manner. On the other hand, increase in ECU functionality translates to an increase in test's functional coverage, requiring more time. Therefore the time taken to execute the tests reaches a critical point in overall ECU production. Availability of multicore microcontrollers with increase in clock speed can increase the performance of end of line tests, but design challenges e.g. synchronization do not guarantee a linear performance increase. Therefore, design of test execution framework is absolutely critical to increase performance of test execution.

The market potential for products such as scooters and small motorcycles is already self-sustaining. However, other applications for small engines can be more fragmented with a wide variety of requirements for the engine control unit. Consequently, the engine control unit can be designed to accommodate more features than are necessary for a given application to cover a broader market. The flip side of this approach is to design the engine control unit for a limited application reducing the market size. Neither approach creates a cost efficient product for the producer. It either supplies the market with an electronic control unit that has features not being utilized (wasted costs) or a unit that has limited capabilities reducing the economies of scale (higher costs). When these designs are developed using discrete components these inefficiencies are exacerbated.