AUTOSAR software engineers and automotive ECU experts

AUTOSAR software engineers implement application components and configure platform software for new ECUs or existing architectures. Architecture reviews identify interface dependencies and timing constraints before implementation.

• AUTOSAR Classic: Configure basic software and RTE integration using tools such as Vector DaVinci or EB tresos. Develop software components against agreed ARXML interfaces.
• AUTOSAR Adaptive: Develop C++ applications on POSIX-based platforms, including service communication through ara::com and execution management integration.

The required specialization depends on the target platform and the boundary between application code and supplier-provided software.

Automotive embedded developers write C and C++ software where application behavior depends on the microcontroller and connected hardware. Bring in an ECU specialist for board bring-up or low-level faults that application-only debugging cannot isolate.

Work covers peripheral drivers and RTOS integration, with attention to interrupt handling and memory use. Engineers use JTAG debugging and trace analysis to investigate timing faults or unexpected resets. Bootloader development can include flash programming and recovery behavior, aligned with the ECU's update requirements and hardware constraints.

ECU integration specialists connect control software to vehicle networks and diagnostic tooling. They reconcile communication definitions with ECU configuration when components from different suppliers fail to exchange the expected data.

• Network integration: Configure CAN/CAN FD or automotive Ethernet communication. Use CANoe and CANalyzer to investigate signal mapping errors and network timing.
• ECU diagnostics: Implement UDS services and Diagnostic Event Manager configuration. Check diagnostic trouble code behavior against diagnostic specifications, including fault reporting and clearing conditions.

Automotive test engineers develop software-in-the-loop and hardware-in-the-loop tests for ECU behavior. They reproduce defects on the bench and connect failures to requirements, giving developers evidence for corrective changes.

Ongoing support covers regression automation and release fault investigation, including changes to existing AUTOSAR configurations. For safety-related software, specialists can contribute verification evidence and requirements traceability within an ISO 26262 process. Automotive SPICE support focuses on documented engineering activities and review evidence; compliance responsibilities remain defined by the project.