SDV SectorNews and signals from the software-defined vehicle sector. Global coverage, daily.

AUTOSAR released CAPI 1.0, a shared code implementation of its Adaptive Platform

The consortium published source code, code generators and a runnable demo of the Adaptive Platform, extending its work from written specifications to software that runs.

Close-up of indented lines of program source code on a dark computer screen.
Illustrative photo · Pixabay / Pexels · not the vehicle described

AUTOSAR announced on August 20 the release of CAPI 1.0, the Common Adaptive Platform Implementation, which it described as a move from a specification-driven standards organization to one that also delivers executable software.

The release gives the industry a common implementation of the AUTOSAR Adaptive Platform, including source code and code generators. According to the release page, CAPI 1.0 follows the Adaptive Platform release R20-11 and already carries forward-looking compatibility with some R23-11 interfaces. It implements all 15 core functional clusters, among them Communication, Execution Management, Logging and Diagnostics, and ships the code generators as source alongside a demo the consortium describes as easy to set up.

AUTOSAR said the project ran from kick-off to release within one year, and thanked the supplier iSOFT for delivering the first major implementation contribution. It said multiple manufacturers, suppliers and technology companies had requested access before the release, and listed Audi, BAIC, BMW, Changan, Dongfeng, Geely, Honda, Mercedes-Benz, Nissan, SAIC, Volkswagen, Volvo, XPENG and Xiaomi as running the Adaptive Platform in production vehicle programs.

The code is not open source. AUTOSAR’s release page states that the files are made available for information only, that commercial exploitation of the material requires a licence to the underlying intellectual property rights, and that contributing to CAPI requires Development, Premium, Premium Plus or Attendee partnership.

Thomas Rüping, chairperson of AUTOSAR, said the release marked a step “from defining standards to enabling executable software.”

Why it mattersFor twenty years AUTOSAR handed the industry a specification and left every integrator to build its own implementation, and a shared code baseline changes what the standard actually guarantees between two suppliers.

Source: AUTOSAR

The SDV Sector Brief

The month in vehicle software — top stories, what our readers read most, and an editor's take. First Tuesday of the month, 08:30 CET. Double opt-in, unsubscribe anytime.