| Source | Frequency | Accuracy | Use Case |
|---|---|---|---|
| Internal RC oscillator | 4-16 MHz (typical) | 1-3% | Startup only; too inaccurate for CAN/LIN |
| External crystal (XTAL) | 8-20 MHz typical | < 50 ppm | Primary clock source for all production ECUs |
| PLL (phase-locked loop) | Multiplies XTAL; up to 300+ MHz | Inherits XTAL accuracy | CPU core, fast peripherals |
| External oscillator input | From another IC or system clock | Depends on source | Gated clock for TSN, FlexRay |
| Low-power RC | 32-768 Hz or ~100 kHz | 2-5% | Standby/sleep oscillator; RTC |
Clock Sources and PLL
MCU Clock Tree: Aurix TC3xx Example
TC3xx Clock Distribution
XTAL 20 MHz
|
PLL0 (System PLL): 20 MHz * 30 / 2 = 300 MHz (fSYS)
|
+-- CPU0/1/2/3/4/5 cores: 300 MHz
+-- BBB (Backbone Bus): 150 MHz (fSYS/2)
+-- SRI bus: 150 MHz
+-- SPB bus: 100 MHz (fSYS/3) <-- peripheral bus
|
+-- UART/SPI/I2C peripherals: 100 MHz
+-- ADC: 100 MHz (pre-scaled per ADC module)
+-- CAN: 80 MHz (separate PLL1 optional)
PLL1 (Peripheral PLL): optional, for CAN FD / Ethernet
+-- CAN FD nodes: 80 MHz for accurate bit timing
+-- Ethernet: 25/50/125 MHz
MCU_Init sequence:
1. Mcu_Init(&McuConfig) -- configure PLL multiplier/divider
2. Mcu_InitClock(McuClockSetting) -- start PLL, wait for lock
3. Mcu_DistributePllClock() -- switch CPU from RC to PLL
4. (all other Init calls now safe)MCU Init Configuration (ARXML / C)
Cmcu_cfg_example.c
/* MCU configuration: PLL setup for Aurix TC387 */
/* Generated by EB tresos / Vector DaVinci Configurator */
#include "Mcu.h"
const Mcu_ClockSettingConfigType McuClockSettingConfig[] = {
{
.McuClockSettingId = MCU_CLOCKSETTING_NORMAL,
/* PLL0: XTAL=20MHz, N=30, K2=2 -> fSYS = 20*30/2 = 300 MHz */
.McuPll0_NDIV = 30u,
.McuPll0_K2DIV = 2u,
.McuPll0_PDIV = 1u,
/* BBB bus divider: 300/2 = 150 MHz */
.McuCpuClockDivider = 1u, /* CPU = fSYS/1 = 300 MHz */
.McuSriClockDivider = 2u, /* SRI = fSYS/2 = 150 MHz */
.McuSpbClockDivider = 3u, /* SPB = fSYS/3 = 100 MHz */
},
{
.McuClockSettingId = MCU_CLOCKSETTING_LOW_POWER,
/* Reduced speed for low-power standby */
.McuPll0_NDIV = 10u, /* fSYS = 20*10/2 = 100 MHz */
.McuPll0_K2DIV = 2u,
.McuPll0_PDIV = 1u,
},
};
/* Startup sequence (called from main.c before OS start) */
void McuStartup(void)
{
Mcu_Init(&McuConfig); /* step 1 */
Mcu_InitClock(MCU_CLOCKSETTING_NORMAL); /* step 2 */
while (Mcu_GetPllStatus() != MCU_PLL_LOCKED) {} /* wait lock */
Mcu_DistributePllClock(); /* step 3 */
/* Now CPU runs at 300 MHz -- all other Init calls safe */
}Summary
The MCU clock tree configuration is the first and most fundamental MCAL task. Every peripheral frequency - ADC conversion rate, CAN bit timing, SPI clock, PWM frequency - derives from the clock tree. A misconfigured PLL divider that produces 200 MHz instead of 300 MHz will cause CAN bit timing errors (the CAN module uses a fixed time quantum count, so frequency error directly translates to baud rate error), ADC conversion time errors, and PWM frequency errors. The MCU_Init sequence must always complete (including PLL lock wait) before any other MCAL module is initialised, because peripheral registers are only accessible after the peripheral bus clock is active.
🔬 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.