/* FreeRTOS task creation — representative of most embedded RTOS APIs */
#include "FreeRTOS.h"
#include "task.h"
/* Task function signature: takes void* parameter, returns void, never returns */
void Task_CanReceive(void *pvParameters)
{
(void)pvParameters; /* suppress unused warning */
CanFrame_t frame;
for (;;) /* tasks must run forever — never return */
{
/* Block until CAN frame available (puts task in BLOCKED state) */
if (xQueueReceive(g_can_rx_queue, &frame, portMAX_DELAY) == pdTRUE) {
Process_CanFrame(&frame);
}
}
/* unreachable: vTaskDelete(NULL) here if task can legitimately end */
}
/* Task stack: statically allocated (required for ASIL — no heap) */
static StackType_t s_can_rx_stack[512]; /* 512 × 4 bytes = 2 kB */
static StaticTask_t s_can_rx_tcb;
void App_Init(void)
{
/* Create task with static allocation (deterministic; no malloc) */
xTaskCreateStatic(
Task_CanReceive, /* function */
"CanRx", /* name (debug) */
512u, /* stack depth (words) */
NULL, /* parameter */
3u, /* priority (higher = more urgent) */
s_can_rx_stack, /* pre-allocated stack */
&s_can_rx_tcb /* pre-allocated TCB */
);
}RTOS Tasks: The Fundamental Unit of Execution
Scheduling Algorithms
| Algorithm | Behaviour | Use Case |
|---|---|---|
| Round-Robin (time-sliced) | Equal-priority tasks share CPU in time slices (tick interval) | Non-critical background processing |
| Preemptive Priority | Highest-priority ready task always runs; lower-priority pre-empted immediately | Real-time control loops |
| Cooperative | Task voluntarily yields; no pre-emption | Simple single-task with yield points; legacy bare-metal style |
| Rate-Monotonic (RM) | Optimal static priority assignment: shorter period → higher priority | Provably schedulable if U ≤ 69% utilisation |
| Earliest Deadline First (EDF) | Dynamic: task closest to deadline runs first | Theoretically optimal but complex to implement |
Context Switch Mechanics (FreeRTOS/Cortex-M)
Task A running (uses R0-R15, PSP, xPSR) │ ├── SysTick interrupt fires (or higher-priority task unblocks) │ Hardware auto-saves: xPSR, PC, LR, R12, R3, R2, R1, R0 → Task A stack (PSP) │ ├── PendSV_Handler (lowest priority; deferred context switch) │ Software saves: R4-R11, PSP value → Task A TCB │ Call scheduler: select highest-priority READY task (Task B) │ Restore Task B: load PSP from Task B TCB; pop R4-R11 │ Return: hardware restores R0-R3, R12, LR, PC, xPSR from Task B stack │ └── Task B running Context switch time (Cortex-M4, FreeRTOS): ~12 µs at 168 MHz Stack overhead per task: 8 hw-saved + 8 sw-saved = 16 words = 64 bytes minimum
Task Priority Design Guidelines
| Priority | Task Type | Examples |
|---|---|---|
| Highest (7–10) | Hard real-time control | Brake actuator, EPS torque control, safety watchdog |
| High (5–6) | Communication drivers | CAN Tx, SPI data acquisition |
| Medium (3–4) | Application logic | Vehicle speed calculation, DTC management |
| Low (1–2) | Background / diagnostics | OBD logging, NvM flush, state estimation |
| Idle (0) | Idle hook | CPU utilisation measurement, sleep management |
Summary
RTOS task priority design follows rate-monotonic analysis: shorter period → higher priority. In automotive AUTOSAR, task periods are fixed at design time (1 ms, 5 ms, 10 ms, 100 ms, 1000 ms) and mapped to OS priorities accordingly. Static task allocation (pre-allocated stack + TCB) is mandatory for ASIL code — pvPortMalloc during task creation is non-deterministic and prohibited. The context switch cost (~12 µs on Cortex-M4) must be budgeted: at 1 kHz scheduling rate, context switches alone consume 1.2% of CPU time.
🔬 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.