AGL Production Readiness Profile

### Overview This session, co-presented by Toyota and Denso, introduces the Automotive Grade Linux (AGL) Production Readiness Profile. While AGL membership has expanded to over 140 companies, actual commercial adoption in production vehicles by OEMs remains limited (with only three public OEM announcements noted, including Toyota in 2017). The gap exists because mainline AGL often lacks production-level automotive requirements, code quality, and architectural features needed for in-vehicle infotainment (IVI). To resolve this, Toyota and Denso are open-sourcing production source code, defining automotive requirements, and contributing a reference profile that upstream AGL can adopt.

### Key Topics - **Production Adoption Gap:** The contrast between high organizational membership in AGL and low production deployment by OEMs due to missing production-grade automotive requirements. - **Production Readiness Profile:** An activity under the AGL IVI project providing a platform for disclosing product-level requirements, specifications, and production-tested source code. - **Automotive Platform Modules:** Upstreamed modules designed for automotive use cases, specifically Health Monitoring, Lifecycle Management, and Power Management. - **Rule-Based Arbitrator (RBA):** A prioritization engine developed by Denso to manage conflicting visual notifications and audio/display content in integrated cockpits and HMI managers. - **Quality and Specification Standards:** Meeting high automotive verification standards (100% C0/C1 coverage, MISRA compliance, integration testing) and updating outdated AGL specifications.

### Technical Details - **Health Monitoring:** Designed to ensure driver experience continuity and safety. If an application (e.g., navigation) fails abnormally, the module detects the issue, restores it to a normal running state without requiring driver intervention, logs anomalies, and handles memory leaks. - **Lifecycle Management:** Controls startup and shutdown sequences of services and applications based on runtime-configurable rules. It enables quick recovery of previously active services (e.g., resuming radio playback upon vehicle start) and ensures proper system logging by guaranteeing the logger service is the last to terminate during shutdown. - **Power Management:** Supports rapid startup requirements (e.g., target boot under 10 seconds) by maintaining standby states and initiating boot processes upon receiving vehicle events, such as a door-open signal prior to the ACC-on state. It also maintains communication readiness for external events (e.g., alerting when sensors detect hazards, remote parking). - **Rule-Based Arbitrator (RBA):** Developed by Denso for consolidated cockpits where autonomous driving events, phone calls, warnings, and navigation alerts compete for display areas. RBA specifies basic rules (priorities, display areas) and exceptional rules (logical constraint formulas such as AND, OR, implication). It intercepts requests before the AGL compositor to arbitrate display presentation with minimal application impact. - **Quality and Verification:** Contributed code has undergone full production testing, attaining 100% C0 and C1 coverage, passing system and integration tests, and adhering to MISRA rules. Future plans include integration with AGL's Continuous Test framework and upstream code reviews.

### Takeaways The Production Readiness Profile represents a code-first approach supported by documentation to bridge the gap between open-source automotive software and production deployment. Toyota and Denso invite OEMs, Tier 1 suppliers, and community members to participate in the bi-weekly IVI meetings, review code, and contribute additional modules such as Window Managers and Application Managers.