Timing Protection & Watchdogs - AUTOSAR Expert

OsTaskTimeFrame: Per-Task Execution Budget

XMLOs_TimingProtection.arxml

OsTimingProtection Parameter	Unit	Description
OsTaskTimeFrame	µs	Minimum time between task activations — alarm period must match this or protection trips
OsTaskExecutionBudget	µs	Maximum CPU time task may consume in one activation — exceeding calls OsProtectionHook(E_OS_PROTECTION_TIME)
OsInterruptTimeFrame	µs	Minimum time between ISR activations — protects against flood of CAN Rx interrupts
OsInterruptExecutionBudget	µs	Maximum ISR execution time — prevents ISR from monopolising CPU

OsInterruptTimeFrame: Protecting Against ISR Floods

Without OsInterruptTimeFrame, a CAN bus error storm can generate thousands of Rx interrupts per second, completely starving all tasks. The time frame imposes a minimum inter-arrival time enforced by the OS timer.

CISR_FloodProtection.c

/* OS enforces: CanIsr_Core0 may not fire more than once per 1000 us */
/* Configuration: OsInterruptTimeFrame = 1000 us */

/* If CAN error storm fires ISR at 50us intervals: */
/* After first ISR fires: OS arms 1000us timeframe timer */
/* Second ISR arrives at 50us: OS detects timeframe violation */
/* → OsProtectionHook(E_OS_PROTECTION_ARRIVAL) called */
/* → Return PRO_TERMINATETASKISR: ISR terminated, rest of system unaffected */

/* DEM event records the ISR flood: */
FUNC(ProtectionReturnType, OS_APPL_CODE) OsProtectionHook(StatusType err) {
    if (err == E_OS_PROTECTION_ARRIVAL) {
        Dem_ReportErrorStatus(DEM_EVENT_ISR_TIMEFRAME_VIOLATED,
                              DEM_EVENT_STATUS_FAILED);
        return PRO_TERMINATETASKISR;
    }
    return PRO_SHUTDOWN;
}

WdgM Supervision: Alive, Deadline, Logical

Supervision Type	WdgM API	Detects	Configuration Key
Alive	`WdgM_CheckpointReached(SE, CP)` every cycle	Task not executing (stuck or starved)	WdgMAliveCycleTime must equal task period ± tolerance
Deadline	`WdgM_CheckpointReached(SE, CP_START)` then `CP_END`	Execution takes too long or too short between two points	WdgMDeadlineMin / WdgMDeadlineMax in µs
Logical	`WdgM_CheckpointReached` along a defined graph	Incorrect code execution sequence (wrong branch taken)	WdgMCheckpointTransitionRef defines valid successor checkpoints

CWdgM_Integration.c

/* In safety runnable: alive supervision */
FUNC(void, EPS_CODE) EPS_Control_Runnable(void)
{
    /* Deadline start: timestamp before safety computation */
    WdgM_CheckpointReached(WDGM_SE_EPS, WDGM_CP_EPS_DEADLINE_START);

    /* Safety computation */
    EPS_ComputeTorqueOverlay();

    /* Deadline end: WdgM checks elapsed time is within [min, max] */
    WdgM_CheckpointReached(WDGM_SE_EPS, WDGM_CP_EPS_DEADLINE_END);

    /* Alive checkpoint: WdgM counts this each 10ms task cycle */
    WdgM_CheckpointReached(WDGM_SE_EPS, WDGM_CP_EPS_ALIVE);
}

Hardware Watchdog Trigger Chain

WdgM → WdgIf → WdgDrv Hardware Chain

  Task_WdgM_10ms
       │  WdgM_MainFunction()
       │  All SupervisedEntities healthy?
       ▼
  WdgIf_SetTriggerCondition(WDG_INSTANCE_0, WDGIF_ON_STATE)
       │  WdgIf routes to hardware watchdog driver
       ▼
  Wdg_SetTriggerCondition(timeout_ms)  ← resets hardware timer
       │  Writes to hardware WDG register
       ▼
  Hardware Watchdog Timer
       │  Reset if not triggered within window
       ▼
  If any SE fails: WdgIf_SetTriggerCondition(WDGIF_OFF_STATE)
       → hardware watchdog NOT triggered → system reset after timeout

XMLWdgM_Config.arxml


  SE_EPS_Control
  D
  
    10  
    1  
    1

Summary

Timing protection operates at three levels in AUTOSAR CP: OsTaskTimeFrame (OS-level per-task budget), WdgM alive/deadline/logical supervision (application-level liveness), and hardware watchdog (last-resort system reset). All three must be configured and tested together — disabling any one level leaves a gap in the temporal FFI argument required by ISO 26262.

🔬 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.