Hands-On: Cross-Platform MCAL Project - MCAL & Driver Development

Capstone Project: Cross-Platform MCAL Configuration

Attribute	Value
Goal	Configure identical functionality on both Aurix TC387 and NXP S32K358
Functionality	CAN FD (500k/2M), ADC 4-channel group, PWM fan output, GPT 1ms tick
Platform A	Infineon Aurix TC387 (EB tresos MCAL)
Platform B	NXP S32K358 (NXP RTD MCAL)
Test	Same application code runs unchanged on both platforms
Deliverables	Two MCAL config files, one shared application, porting notes

Exercise 1: Platform Abstraction for Application Code

Cplatform_abstraction.h

/* Platform abstraction: same application code runs on TC387 and S32K358 */
/* All MCU-specific details hidden behind this header */

#ifndef PLATFORM_ABSTRACTION_H
#define PLATFORM_ABSTRACTION_H

#include "Std_Types.h"

/* CAN channel IDs: platform-specific in implementation, abstract here */
#define PLATFORM_CAN_CHANNEL_MAIN    ((uint8)0u)

/* ADC group IDs */
#define PLATFORM_ADC_GROUP_SENSORS   ((uint8)0u)

/* PWM channel IDs */
#define PLATFORM_PWM_CH_FAN          ((uint8)0u)

/* GPT channel IDs */
#define PLATFORM_GPT_CH_1MS          ((uint8)0u)

/* Startup: call before any other MCAL */
extern void Platform_Init(void);

/* CAN: abstract over Can_Init differences (RTD vs standard) */
extern Std_ReturnType Platform_Can_Start(uint8 channel);
extern Std_ReturnType Platform_Can_Send(uint8 channel,
                                        uint32 id,
                                        const uint8 *data,
                                        uint8 dlc);
/* ADC: abstract over group configuration */
extern Std_ReturnType Platform_Adc_GetResults(uint8 group,
                                               uint16 *buf,
                                               uint8 count);
/* PWM */
extern void Platform_Pwm_SetDuty(uint8 ch, uint8 duty_pct);

#endif /* PLATFORM_ABSTRACTION_H */

Exercise 2: MCAL Porting Checklist

Markdownmcal_porting_checklist.md

# MCAL Porting Checklist: Aurix TC387 to NXP S32K358

## Clock Tree
[ ] Recalculate PLL settings for new MCU crystal frequency
[ ] Update all peripheral clock dividers (CAN, ADC, SPI, GPT)
[ ] Verify CPU frequency matches original design

## Port / GPIO
[ ] Map all ECU signals to new MCU pin numbers (schematic review)
[ ] Verify alternate function numbers match peripheral connections
[ ] Check drive strength requirements for high-speed signals

## CAN Bit Timing
[ ] Recalculate prescaler + segments for new CAN clock frequency
[ ] Verify sample point is 75-87.5% for all baud rates
[ ] Recalculate TDC (Transmitter Delay Compensation) for FD data phase
[ ] Check CAN transceiver (TJA1044) EN/STB pin mapping to new GPIO

## ADC
[ ] Verify ADC channel numbers for same physical pins on new MCU
[ ] Recalculate sampling time for new ADC clock frequency
[ ] Confirm ADC reference voltage (VREF) is same on new board

## PWM / ICU / GPT
[ ] Map timer channels: GTM (TC387) -> FTM/EMIOS (S32K358)
[ ] Recalculate period/duty registers for new timer clock
[ ] Verify PWM output polarity matches actuator requirements

## Flash / EEPROM
[ ] Update FLS base address and sector size for new MCU
[ ] Reconfigure Fee virtual address space if flash size changed
[ ] Verify EEP (DFLASH or SPI) mapping is preserved

## Watchdog
[ ] Recalculate reload value for same timeout window
[ ] Verify WDG ISR priority assignment on new MCU

## Safety
[ ] Map SMU (TC387) alarms to S32K358 equivalent fault management
[ ] Verify ECC configuration is active on RAM and flash
[ ] Confirm lockstep mode enabled (S32K358 requires explicit config)

Summary

The cross-platform MCAL project is where all course concepts converge. The platform abstraction header (Platform_Can_Start, Platform_Adc_GetResults) is the practical embodiment of the AUTOSAR portability promise: application code calls these functions without any knowledge of whether it is running on Aurix or S32K. The porting checklist reveals that most porting effort is in two areas: clock tree recalculation (every baud rate, sample time, and PWM frequency depends on the peripheral clock, which changes with the MCU) and pin mapping (every ECU signal may move to a different pin number and alternate function number on the new MCU). These two areas account for 80% of MCAL porting bugs, which is why the checklist approach - reviewing every peripheral systematically rather than only the ones that obviously changed - is the industry-standard porting methodology.

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