AUTOSAR Integration Guide for AutoChips MCUs
AUTOSAR (AUTomotive Open System ARchitecture) is the standardized software architecture widely adopted in the automotive industry. This guide covers the integration of AutoChips MCUs into AUTOSAR-based systems, providing practical guidance for software developers and system architects.
AUTOSAR Architecture Overview
AUTOSAR defines a layered software architecture consisting of the Application Layer (ASW), Runtime Environment (RTE), and Basic Software (BSW). The BSW is further divided into ECU Abstraction Layer, Service Layer, and Microcontroller Driver Layer (MCAL). AutoChips provides MCAL drivers that interface between the microcontroller hardware and the upper AUTOSAR layers.
MCAL Configuration
The Microcontroller Driver Layer (MCAL) provides low-level drivers for microcontroller peripherals including GPIO, ADC, PWM, CAN, LIN, and SPI. AutoChips MCAL drivers are compliant with AUTOSAR 4.x standards and support various compiler toolchains including Tasking, HighTec, and Green Hills.
MCAL configuration is performed using EB tresos Studio or similar configuration tools. The configuration process involves: selecting enabled peripherals, configuring clock settings and prescalers, setting up pin multiplexing and alternate functions, and configuring interrupt priorities and routing.
Integration Best Practices
Successful AUTOSAR integration requires attention to timing, memory, and communication aspects. Ensure MCAL initialization completes before BSW initialization. Configure memory sections according to linker scripts provided by AutoChips. Implement proper error handling and diagnostic event management.
As an authorized AutoChips distributor, LiTong provides AUTOSAR MCAL packages, configuration support, and integration consulting services.
💡 FAE Insights
📋 Customer Cases
Automotive Tier-1 Supplier
Automotive Electronics
Challenge
Team needed to migrate from proprietary software to AUTOSAR for OEM compliance. Limited experience with AUTOSAR configuration and integration.
Solution
Used AutoChips MCAL with EB tresos configuration tool. Started with reference configuration and adapted for specific requirements. Implemented incremental testing approach.
Customer Feedback
"Successfully achieved AUTOSAR compliance within project timeline. Reference configuration accelerated development significantly."
Frequently Asked Questions
1. What AUTOSAR version does AutoChips MCAL support?
AutoChips MCAL drivers support AUTOSAR Classic Platform version 4.2.2 and 4.4.0. The drivers are tested and validated against these AUTOSAR specifications. For Adaptive AUTOSAR applications, standard POSIX drivers can be used with AutoChips MCUs. Contact LiTong for specific AUTOSAR version requirements and compatibility information.
2. What configuration tools are supported?
AutoChips MCAL supports industry-standard configuration tools including EB tresos Studio, Vector DaVinci Configurator, and ETAS ISOLAR. The MCAL delivery includes configuration files (ARXML) that can be imported into these tools. EB tresos is the most commonly used tool and has the most mature support for AutoChips MCAL.
3. How do I debug AUTOSAR integration issues?
AUTOSAR debugging requires understanding the layered architecture. Use DET (Default Error Tracer) to catch BSW and MCAL errors. Enable development error detection in MCAL configuration. Use RTE trace to monitor inter-SWC communication. For timing issues, use OS timing protection and analyze task scheduling. LiTong FAEs can provide debugging support for complex integration issues.
4. What is the RTE and how does it work?
RTE (Runtime Environment) is the middleware layer in AUTOSAR that enables communication between software components (SWCs). RTE provides standardized interfaces for inter-component communication. It handles data consistency and timing. RTE is generated based on component configuration.
5. How do I configure MCAL for my application?
MCAL configuration is done using EB tresos Studio or similar tools. Import the MCAL package, create a new project, and configure each peripheral using the graphical interface. Generate the configuration code and integrate it with your application. Validate the configuration using DET.