Simply put, a software-defined vehicle is a vehicle with features and functions that are enabled through software. This is different from today’s vehicles, which are primarily hardware-based platforms. A software-defined vehicle needs to simultaneously run multiple applications that are built on a standard operating system, similar to today’s computers and mobile phones. In automotive, this standard operating system is called middleware. As the operating system, middleware provides a foundation for basic functionality, including communication, memory management, scheduling, input/output/access to vehicle data, and Internet connectivity.
Standard safety and control electronic control units (ECUs) – braking systems, power windows – have been standardized in AUTOSAR for almost 20 years. The software in these ECUs is comparatively simple; the largest have a few megabytes of code. On…
Picture this: you and your team of software engineers need to create an ECU using AUTOSAR (AUTomotive Open System ARchitecture). But no one has used AUTOSAR before. Within the team, individuals have varying levels of overall experience, but to be…
The automotive industry is facing a dramatic transformation that brings fundamental changes to vehicle E/E architectures in the connected and automated driving environment. Designs are shifting from many application-specific ECUs to a few high-performance domain controllers with bundled functionalities. This technical engineering trend imposes a consolidation of automotive cybersecurity and a change of the AUTOSAR architecture.
As applications advance for infotainment and ADAS systems, a new standardized middleware is being built – it will operate in conjunction with the classic and adaptive systems to provide robust and safe solutions while building on the complexity required for these advanced vehicle functions.
Adaptive AUTOSAR is a catalyst for change within automotive enabling the introduction of new application domains and new E/E architectures. However, the Adaptive Platform does not (yet) address all the issues that are relevant for cross-domain integration and vehicle computation E/E architectures. Hence, ETAS, together with Bosch, is building RTA-VRTE to address the challenges.
The CASE (Connectivity, Autonomy, Shared Ownership, Electrification) requirements driving development of next-generation automotive E/E architectures are promoting change in automotive ECUs at an ever increasing pace. Thus the need for a new high performance, highly flexible platform supporting HPC, dynamic communication and incremental change — a new platform and not Classic.