#include
/* Rule 10.1: Operands shall not be of an inappropriate essential type
Violation: shifting a signed integer */
int16_t x = 10;
int16_t y = x << 3; /* VIOLATION: shift of signed type */
/* Fix: */
uint16_t xu = (uint16_t)x;
uint16_t y2 = (uint16_t)(xu << 3u); /* explicit cast + unsigned shift */
/* Rule 10.3: Value cannot be assigned to narrower essential type
Violation: assigning uint16 result to uint8 */
uint16_t adc = 1234u;
uint8_t trunc = adc; /* VIOLATION: implicit narrowing conversion */
/* Fix: explicit cast with range check */
uint8_t scaled = (uint8_t)(adc >> 4u); /* explicit: knows upper bits are 0 */
/* Rule 10.4: Both operands of operator in the same essential type category
Violation: mixing signed/unsigned */
uint32_t len = 100u;
int32_t diff = -5;
if (diff < len) { /* VIOLATION: signed/unsigned comparison */ }
/* Fix: */
if ((uint32_t)diff < len) { /* explicit cast; ensure diff >= 0 first */ }
/* Rule 10.8: Value of a composite expression shall not be cast to wider type
Violation: */
uint8_t a = 200u, b = 100u;
uint32_t bad = (uint32_t)(a + b); /* overflow in uint8 before cast! */
uint32_t good = (uint32_t)a + (uint32_t)b; /* cast before arithmetic */ Implicit Conversions: Rules 10.1–10.8
Control Flow Rules: 14.x and 15.x
| Rule | Requirement | Common Violation |
|---|---|---|
| Rule 14.4 | The controlling expression of an if/loop shall be essentially Boolean | if (status) instead of if (status != 0u) |
| Rule 15.2 | switch without a break shall have a comment | Fall-through case without /* FALL THROUGH */ |
| Rule 15.3 | A switch statement shall have a default case | Missing default: case in switch |
| Rule 15.4 | There shall be at most one break in a loop | Multiple break in a single for loop |
| Rule 15.5 | A function should have a single exit point | Multiple return statements (Advisory) |
| Rule 15.7 | Every if-else chain shall end with an else clause | Missing final else |
Writing a MISRA Deviation Record
/* MISRA-C:2012 Deviation Record Example */
/* Rule: MISRA-C:2012 Rule 11.5 (Advisory)
Message: A conversion should not be performed from pointer to void
into pointer to object
Code: void *raw = malloc_pool_alloc(64u);
uint8_t *buf = (uint8_t *)raw;
Reason: Memory pool returns void* by design; cast to uint8_t* is required.
The allocated memory is always correctly aligned for uint8_t.
This is a deliberate design choice, not an unsafe practice.
Risk: Low — alignment guaranteed by pool allocator; usage is bounded.
Approved: John Smith (SW Lead), 2024-03-15
Tools: PC-lint annotation: //lint -e9079 Deviation MISRA_11_5_001 */
/*lint -e9079 [Deviation MISRA_11_5_001: See deviation record DV-MISRA-001] */
void *raw = Pool_Alloc(sizeof(uint8_t) * 64u);
uint8_t *buf = (uint8_t *)raw;
/*lint +e9079 */Summary
The most frequently triggered MISRA rules in automotive C code are the implicit conversion rules (10.x): signed/unsigned mixing and narrowing assignments. These are not just style issues — MISRA 10.3 violations can cause silent data loss at runtime, and MISRA 10.4 violations cause wrong comparison results when signed values go negative. The deviation process is the release valve: Advisory rules that are impractical to follow universally can be deviated with documented justification. The deviation record is mandatory — a static analysis suppression annotation without a written justification is non-compliant.
🔬 Deep Dive — Core Concepts Expanded
This section builds on the foundational concepts covered above with additional technical depth, edge cases, and configuration nuances that separate competent engineers from experts. When working on production ECU projects, the details covered here are the ones most commonly responsible for integration delays and late-phase defects.
Key principles to reinforce:
- Configuration over coding: In AUTOSAR and automotive middleware environments, correctness is largely determined by ARXML configuration, not application code. A correctly implemented algorithm can produce wrong results due to a single misconfigured parameter.
- Traceability as a first-class concern: Every configuration decision should be traceable to a requirement, safety goal, or architecture decision. Undocumented configuration choices are a common source of regression defects when ECUs are updated.
- Cross-module dependencies: In tightly integrated automotive software stacks, changing one module's configuration often requires corresponding updates in dependent modules. Always perform a dependency impact analysis before submitting configuration changes.
🏭 How This Topic Appears in Production Projects
- Project integration phase: The concepts covered in this lesson are most commonly encountered during ECU integration testing — when multiple software components from different teams are combined for the first time. Issues that were invisible in unit tests frequently surface at this stage.
- Supplier/OEM interface: This is a topic that frequently appears in technical discussions between Tier-1 ECU suppliers and OEM system integrators. Engineers who can speak fluently about these details earn credibility and are often brought into critical design review meetings.
- Automotive tool ecosystem: Vector CANoe/CANalyzer, dSPACE tools, and ETAS INCA are the standard tools used to validate and measure the correct behaviour of the systems described in this lesson. Familiarity with these tools alongside the conceptual knowledge dramatically accelerates debugging in real projects.
⚠️ Common Mistakes and How to Avoid Them
- Assuming default configuration is correct: Automotive software tools ship with default configurations that are designed to compile and link, not to meet project-specific requirements. Every configuration parameter needs to be consciously set. 'It compiled' is not the same as 'it is correctly configured'.
- Skipping documentation of configuration rationale: In a 3-year ECU project with team turnover, undocumented configuration choices become tribal knowledge that disappears when engineers leave. Document why a parameter is set to a specific value, not just what it is set to.
- Testing only the happy path: Automotive ECUs must behave correctly under fault conditions, voltage variations, and communication errors. Always test the error handling paths as rigorously as the nominal operation. Many production escapes originate in untested error branches.
- Version mismatches between teams: In a multi-team project, the BSW team, SWC team, and system integration team may use different versions of the same ARXML file. Version management of all ARXML files in a shared repository is mandatory, not optional.
📊 Industry Note
Engineers who master both the theoretical concepts and the practical toolchain skills covered in this course are among the most sought-after professionals in the automotive software industry. The combination of AUTOSAR standards knowledge, safety engineering understanding, and hands-on configuration experience commands premium salaries at OEMs and Tier-1 suppliers globally.