Spinlocks & Shared Resource Management - AUTOSAR Expert

OsSpinlock Configuration & Acquisition Order

Deadlock between cores is possible if two cores can acquire spinlocks in different orders. AUTOSAR OS solves this via OsSpinlockSuccessor: it defines a mandatory acquisition order that the OS verifies at runtime (in development builds with SpinlockOrderCheck enabled).

XMLOs_Spinlock.arxml



  SPINLOCK_NVM_REQUEST
  
  
    /Os/Spinlocks/SPINLOCK_DEM_STATUS
  



  SPINLOCK_DEM_STATUS

⚠️ Acquisition Order is a Global Invariant

Every code path on every core that acquires multiple spinlocks must acquire them in the order defined by OsSpinlockSuccessor. A single violation (a Core 1 task acquiring SPINLOCK_DEM before SPINLOCK_NVM while Core 0 does the opposite) causes a system deadlock that only manifests under race conditions — typically impossible to reproduce in testing. Use AUTOSAR OS SpinlockOrderCheck=TRUE in all development builds to catch violations at runtime before release.

Spinlock API: GetSpinlock vs TryToGetSpinlock

API	Behaviour	Use Case	Bounded Execution?
`GetSpinlock(SpinlockIdType)`	Busy-waits until acquired — other core must release	When data access is mandatory and caller can tolerate indeterminate wait	No — wait time unbounded if contention is high
`TryToGetSpinlock(SpinlockIdType, &TryToGetSpinlockType)`	Returns immediately with E_OK (acquired) or E_OS_INTERFERENCE (not acquired)	Safety tasks with strict WCET budgets; retry on next cycle if not acquired	Yes — always returns within a fixed time

CTrySpinlock_Pattern.c

/* Pattern: TryToGetSpinlock in a safety task with bounded WCET */
TryToGetSpinlockType spinResult;
(void)TryToGetSpinlock(SPINLOCK_SHARED_FLAG, &spinResult);

if (spinResult == TRYTOGETSPINLOCK_SUCCESS) {
    /* Got the lock — access shared data */
    sharedNvmWriteFlag = TRUE;
    ReleaseSpinlock(SPINLOCK_SHARED_FLAG);
} else {
    /* Spinlock held by other core — defer to next cycle */
    /* This is acceptable: NvM write will be triggered on next 10ms cycle */
    deferredNvmWrite = TRUE;
}

OS Restrictions on Spinlock Usage

AUTOSAR OS prohibits calling most OS services while a spinlock is held. Violations cause E_OS_SPINLOCK return codes or protection hooks in development builds.

Prohibited While Spinlock Held	Reason
`ActivateTask()`	May trigger scheduler on both cores — undefined interaction with held spinlock
`WaitEvent()`	Would block the core indefinitely while holding a spinlock, starving the other core
`ChainTask()`	Terminates current task — spinlock would never be released
`ShutdownOS()`	System shutdown with spinlock held — deadlock on next startup

CSpinlock_Correct_Usage.c

/* CORRECT: spinlock held only for shared memory access */
GetSpinlock(SPINLOCK_SHARED_FLAG);
    local_copy = sharedBuffer[index]; /* copy out */
ReleaseSpinlock(SPINLOCK_SHARED_FLAG);
/* Process local_copy OUTSIDE spinlock */
ProcessData(local_copy);

/* WRONG: calling ActivateTask while spinlock is held */
GetSpinlock(SPINLOCK_SHARED_FLAG);
    ActivateTask(Task_DataReady); /* AUTOSAR OS violation! */
ReleaseSpinlock(SPINLOCK_SHARED_FLAG);

Alternatives to Spinlocks

Mechanism	AUTOSAR API	When to Prefer Over Spinlock
IOC Channel	Ioc_Send / Ioc_Receive	Cross-core RTE data exchange — IOC spinlock is internal and OS-managed
SchM Exclusive Area	SchM_Enter_<Mod> / SchM_Exit_<Mod>	BSW-internal shared data within a module — SchM generates correct OS call
Event + IOC flag	SetEvent + IOC last-is-best	Asynchronous notification from one core to another without blocking
Core-local RAM buffers	No API — by design	Data produced and consumed on same core needs no cross-core protection

Summary

Spinlocks are the lowest-level cross-core synchronisation primitive in AUTOSAR OS. Use them sparingly and for the shortest possible critical sections. The OsSpinlockSuccessor ordering invariant must be respected globally across all code paths to prevent deadlock. For RTE-level data, always prefer IOC over raw spinlocks — IOC is portable, analysable, and integrates with the RTE generator.

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