What runs here
The Microcontroller Abstraction Layer (MCAL) is the hardware-facing part of AUTOSAR Classic basic software. On an HPC safety island, it controls the peripherals assigned to the island’s MCU cores. Standard interfaces help upper software remain portable, but driver implementations and configurations depend on the particular silicon.
| Component | Role |
|---|---|
CAN Driver (Can) |
Controls an assigned CAN controller, including CAN FD where supported and configured. |
GPT Driver (Gpt) |
Provides general-purpose hardware timer channels. |
Watchdog Driver (Wdg) |
Configures and services the watchdog hardware within the permitted operating modes. |
MCU Driver (Mcu) |
Provides supported clock, reset and power-mode functions; ownership may be shared with boot firmware. |
Port and DIO Drivers (Port, Dio) |
Configure pins and access digital inputs and outputs where available to the island. |
This is a candidate set, not a mandatory inventory. Peripheral availability, core access and driver coverage must be checked against the selected SoC and software delivery. TI’s MCAL documentation illustrates how supported modules vary by device and core.
SoC fault controllers, self-test mechanisms and interprocessor mailboxes may require separate vendor software. They should not automatically be described as standard MCAL modules.
Why it looks like this
The island supports real-time control and safety monitoring, so bounded execution, predictable interrupts and controlled hardware access matter more than a broad peripheral ecosystem. Statically configured drivers help engineers reason about resource use and timing. Hardware timer behaviour also depends on the clock configuration, linking driver configuration directly to timing analysis. AUTOSAR GPT Driver specification
For functions with ASIL D requirements, driver suitability depends on the allocated safety requirements, integration evidence and supplier safety-manual assumptions. AUTOSAR conformance and lockstep execution alone do not establish software safety. ISO 26262-6 addresses development at the software level. ISO 26262-6:2018
Integrating the island into the HPC can reduce the need for a separate supervisory MCU, but creates dependencies that must be assessed. Separate cores do not automatically mean independent clocks, power, reset or interconnects. Available isolation mechanisms are device-specific. TI’s safety architecture overview
Keeping the driver configuration small reduces memory demand and verification effort. It is generally sensible to change this hardware-dependent baseline less frequently than application features, while still maintaining a controlled path for defect fixes and silicon errata.
How it connects
Above MCAL, basic-software interfaces and services organize access. A typical CAN transmit path is COM → PDU Router (PduR) → CAN Interface (CanIf) → CAN Driver (Can). Watchdog Manager (WdgM) supervision reaches watchdog hardware through Watchdog Interface (WdgIf) and the configured driver. Applications normally use the RTE and appropriate services rather than accessing peripheral registers directly. These boundaries belong to the AUTOSAR Classic architecture.
Below MCAL are peripheral registers, interrupts and hardware resources. Integration must define initialization order, interrupt routing, exclusive access and permitted core ownership.
Connections to other nodes pass through the physical network controller and transceiver. Communication with the application processor may instead use shared memory and mailboxes through a separate IPC implementation. Define message ownership, timeouts and fault handling explicitly; an on-chip connection still needs appropriate safety protection.
Compared with other node classes
- HPC application processor: BSP, Linux drivers and possibly VirtIO support a richer operating environment; the island uses drivers integrated for its real-time and safety requirements.
- Zone controller: MCAL often covers broader local sensor, actuator and network I/O, with I/O Hardware Abstraction and complex drivers above or alongside it.
- MCU-based ECU: The MCAL boundary is similar, but the safety island additionally requires careful coordination with other processors inside the SoC.
- Smart node / LIN slave: A small peripheral-driver set or ASIC logic may provide the required behaviour without AUTOSAR MCAL.
Best practices
- Record peripheral, clock, reset, pin and interrupt ownership across all processors and boot stages.
- Match drivers, configuration tools, silicon revision and errata handling to a controlled baseline.
- Apply supplier safety-manual assumptions and trace driver integration to allocated safety requirements.
- Measure interrupt latency and driver execution under representative shared-resource contention.
- Verify startup, watchdog expiry, peripheral faults and application-processor restart behaviour against the intended safe or degraded state.
Common pitfalls
- Assuming every peripheral in the SoC is accessible from the safety island or covered by its MCAL delivery.
- Allowing application-processor firmware to change clocks or reset peripherals still used by the island.
- Treating lockstep cores, MCAL conformance or a supplier safety claim as sufficient evidence for the complete safety function.