The automotive industry has undergone significant transformations in recent years, with a growing focus on software-driven innovations. However, this shift has also introduced new challenges, particularly in terms of software fragmentation.

Historically, automakers have relied on different computer hardware running different operating systems and software platforms for each model year, resulting in a fragmented landscape. This approach has led to increased costs, complexity, and difficulties in managing software updates.

Hardware and Software Challenges

• Fragmentation: Automakers were tied to proprietary hardware and software systems, which limited their flexibility and freedom to choose the best components for their vehicles. Each model year, automakers would receive a new operating system and software platform from their hardware suppliers, resulting in a fragmented landscape. This made it difficult to manage software updates, ensure consistency across different models, and maintain a unified user experience. Wonder why Teslas can get OTA software updates but you have to take your Ford to a dealer for similar updates?
• Scalability and customization: The hardware and software platforms used in in-vehicle infotainment (IVI) systems were often designed for specific models or trim levels, making it difficult to scale up or down to meet changing market demands. Automakers had to customize the software for each model, which was a time-consuming and costly process. This led to increased development costs, longer production cycles, and a higher likelihood of errors and bugs.
• Integration: Integrating various software components, such as navigation, speech recognition, and multimedia players, was a complex task. This complexity made it challenging to ensure seamless interactions between different systems and components.
• Security: The fragmented software landscape made it difficult to ensure the security and integrity of the IVI system. This exposed automakers to potential security risks, such as hacking and data breaches.
• High Development Costs: The cost of developing and testing new hardware and software components was high, which made it challenging for automakers to innovate and stay competitive. The complexity of IVI systems, with multiple components and interfaces, made it difficult to diagnose and repair issues, leading to increased maintenance and support costs.

Shifting gears from proprietary software to AGL

The introduction of Automotive Grade Linux (AGL) has helped to address these challenges by providing a unified software platform, enabling automakers to develop and deploy IVI systems more efficiently, securely, and cost-effectively.

As Dan Cauchy, Executive Director of AGL at the Linux Foundation, explains, “AGL was created to alleviate that problem by creating a single platform that everybody builds on top of.” By providing a standardized software base, AGL enables automakers to focus on developing their unique features and services, rather than rebuilding the underlying software for each model year.

Initially focused on infotainment, AGL now includes instrument clusters, heads-up displays, and telematics. Since then, AGL has expanded to cover additional automotive software areas, including telematics for fleet management, which can enable companies like UPS and FedEx to access vehicle data more effectively.

Cauchy highlights that AGL’s first major release, the Unified Code Base (UCB), was designed to reduce fragmentation. “We intended to eliminate the fragmentation I described earlier and have a single platform where all the automotive components and open source packages are integrated,” Cauchy explains.

By maintaining a standardized software base, AGL allows automakers to integrate their preferred navigation, speech recognition, and branding without having to rebuild software for each model year, creating a more sustainable and efficient development process.

Automakers have increasingly adopted AGL, with Toyota leading the way—the 2018 Camry was the first to feature it, followed by most Toyota and Lexus models. Subaru has also integrated AGL into models like the Legacy, Forester, and Outback. While some European manufacturers have adopted AGL, official confirmation remains limited. Semiconductor companies such as Renesas, Qualcomm, and Xilinx are key contributors to the ecosystem.

Since its inception, AGL has gained traction across the automotive industry, with members including Toyota, Honda, Mazda, Nissan, Suzuki, Hyundai, Mercedes, Volkswagen, and SAIC. The project also collaborates with leading semiconductor companies and cloud providers like AWS, fostering a comprehensive platform for various stakeholders.

Now integrated into over 100 million vehicles, AGL is driving the adoption of Software Defined Vehicles (SDVs) to streamline software management. It is also working with LF Energy on an EV charging initiative. The Open Source Program Office (OSPO), led by Toyota and Honda, helps automakers navigate legal and compliance challenges in contributing to open source projects by providing best practices and a structured playbook.

AGL’s focus on SDVs enables hardware abstraction, allowing a single software image to function across different vehicles, similar to Apple’s iOS updates. Additionally, its collaboration with LF Energy on EVerest, an open source EV charging stack, supports Europe’s push for standardized infrastructure.

Guest: Dan Cauchy
Organization: Linux Foundation