Automotive Embedded C/C++/CAPL Best Practices

Comprehensive coding guidelines for automotive embedded software development in C, C++, and CAPL. Contains 180+ rules across 23 categories, prioritized by safety impact and industry compliance requirements (MISRA C:2012, MISRA C++:2023, AUTOSAR C++14 Classic & Adaptive, ISO 26262, ISO 21434). Covers full automotive communication stack (CAN/LIN/Ethernet/IP/TSN), cybersecurity, diagnostics, CAPL simulation/testing/fault injection, AUTOSAR BSW modules, boot/NVM/power management, compiler toolchains, static analysis tools, and CI/CD integration.

When to Apply

Reference these guidelines when:

• Writing new embedded C/C++ modules for automotive ECUs
• Implementing or reviewing CAN/LIN/Ethernet communication stacks
• Writing CAPL scripts for CANoe/CANalyzer simulation and testing
• Refactoring code for MISRA C/C++ or AUTOSAR C++14 compliance
• Designing safety-critical software (ASIL A-D per ISO 26262)
• Implementing RTOS task management and inter-task communication
• Reviewing code for memory safety, timing, and determinism
• Working with diagnostic protocols (UDS, OBD-II, DoIP)
• Implementing Automotive Ethernet (TCP, UDP, SOME/IP, DoIP, VLAN)
• Addressing cybersecurity requirements (ISO 21434, secure boot, TLS)
• Integrating with calibration/diagnostic tools (A2L, ODX, XCP)
• Optimizing for resource-constrained microcontrollers (RAM, Flash, CPU)