Home Learning Paths ECU Lab Assessments Interview Preparation Arena Pricing Log In Sign Up

MISRA-C:2012 Overview

CategoryCountCan be deviated?Typical Coverage
Mandatory rules10No — violations must be fixedMemory safety, undefined behaviour
Required rules~130Yes — with documented deviationLanguage subset, type safety, control flow
Advisory rules~16Yes — with documented deviationStyle, maintainability
Directives~17Yes — with justificationProcess requirements (documentation, testing)

💡 MISRA Compliance Model

MISRA compliance is not binary pass/fail. A project is compliant if: all Mandatory rules are satisfied (no deviations); all Required and Advisory violations have formal documented deviations with justification and risk assessment; static analysis tools verify compliance; and a qualified reviewer signs off. A common misconception is that a Polyspace or PC-lint warning = MISRA violation — static analysis can produce false positives and cannot check all rules; code review is also required.

Selected Mandatory Rules

RuleCategoryRequirementExample Violation
Rule 6.2MandatoryA signed integer type used in a bit-field shall be declared as signed and not plain intstruct { int x:3; } — type of x is implementation-defined
Rule 9.1MandatoryThe value of an object shall not be read before it has been setuint8_t x; if(x > 0) — unintialised read
Rule 13.2MandatoryThe value of an expression and its persistent side effects shall be the same under all permitted evaluation ordersf(i++, i) — order of evaluation undefined
Rule 17.3MandatoryA function shall not be declared implicitlyCalling undeclared function — implicit int return
Rule 18.2MandatorySubtraction shall not be applied to pointers unless they point into the same arrayp1 - p2 where pointers are to different objects

MISRA Directives: Process and Documentation

Cmisra_directives.c
/* MISRA-C:2012 Directive 4.1: Run-time failures shall be minimised
   Requires: pre/post-condition checks, input validation */

Std_ReturnType Adc_Read(uint8_t channel, uint16_t *result)
{
    /* Pre-condition: valid channel index */
    if (channel >= ADC_MAX_CHANNELS) {
        return E_NOT_OK;                /* guard against invalid input */
    }
    /* Pre-condition: result pointer not NULL */
    if (result == NULL_PTR) {
        return E_NOT_OK;
    }

    *result = ADC_REGS->DR[channel] & 0x0FFFu;
    return E_OK;
}

/* MISRA-C:2012 Directive 4.7: If a function returns error information,
   that error information shall be tested
   Wrong: ignoring return value */
/* Adc_Read(0u, &val);           -- VIOLATION: return value ignored */

/* Correct: always check return value */
Std_ReturnType ret = Adc_Read(0u, &val);
if (ret != E_OK) {
    /* handle error */
    Dem_ReportErrorStatus(DEM_ADC_ERROR, DEM_EVENT_STATUS_FAILED);
}

Summary

MISRA-C:2012 is the primary code quality standard for automotive software; it is referenced by ISO 26262 (ASIL A–D) and mandated by most OEM software requirements. The mandatory rules (10 rules) cover undefined and implementation-defined behaviours that cause real bugs: uninitialised reads, evaluation order violations, and implicit function declarations. Directives (especially Dir 4.1, 4.7, 4.9) define process requirements: input validation, return value checking, and macro discipline. A static analysis tool (Polyspace, PC-lint, Cppcheck) configured for MISRA-C:2012 is the practical implementation — manual review alone cannot verify rule compliance across a large codebase.

🔬 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

  1. 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'.
  2. 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.
  3. 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.
  4. 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.

← PreviousHands-On: GPIO & Timer Driver in CNext →Common MISRA Violations & Fixes