6.8. MCU Module Migration

Migration Approach: Follow sequential migration for clear understanding of changes at each version. Each migration is organized by individual changes with description, old vs new comparison, and migration actions.

6.8.1. v02.02.00 (i.e release v26.00.00) from v02.01.01 (i.e release v01.04.01) Migration

6.8.1.1. Summary

Version v02.02.00 introduces the following changes to the MCU module:

Automatic CPUSEL/FRAMESEL Register Writes via ResourceAllocator: Mcu_Init() now writes CPUSEL and FRAMESEL peripheral ownership registers from ResourceAllocator configuration
McuSysClkDiv Recommended Configuration Update (Errata Advisory): Configurator now warns when McuSysClkDiv = 1; recommended to use McuSysClkDiv >= 2 to avoid XRSn reset errata

6.8.1.2. Change 1: Automatic CPUSEL/FRAMESEL Register Writes via ResourceAllocator

6.8.1.2.1. Description

Version v02.02.00 extends Mcu_Init() to write CPUSEL (CPU selection) and FRAMESEL (frame selection) peripheral ownership registers for all peripherals configured in the ResourceAllocator plugin. The configuration is generated into a new Mcu_PeripheralConfigSet[] array and Mcu_PeripheralConfig struct in Mcu_Cfg.c.

Projects that previously wrote CPUSEL/FRAMESEL registers manually must remove those manual writes to avoid conflicts.

6.8.1.2.2. Old vs New

Behavior	v02.01.01	v02.02.00
CPUSEL/FRAMESEL register writes	Application responsibility (manual)	Written automatically by `Mcu_Init()` from ResourceAllocator config

Warning

If your application or any BSW module manually writes CPUSEL or FRAMESEL registers, those writes must be removed. Duplicate writes after Mcu_Init() may overwrite the generated ownership configuration and cause unexpected peripheral behavior.

6.8.1.2.3. Migration Actions

Verify ResourceAllocator configuration: Confirm that the ResourceAllocator plugin is configured with the correct CPU and frame ownership for each peripheral used in your project
Identify manual CPUSEL/FRAMESEL writes: Search your application code and any BSW integration code for direct writes to CPUSEL and FRAMESEL registers for the peripherals listed above
Remove manual register writes: Delete or disable all manual CPUSEL/FRAMESEL register writes that are now handled by Mcu_Init()
Regenerate MCU configuration files: Regenerate Mcu_Cfg.c and Mcu_Cfg.h using the updated generator (see Change 1, step 1 — this step is shared)
Verify Compilation and runtime behavior: Clean build, run on target, and confirm all peripherals are accessible from the expected CPU after Mcu_Init() completes

6.8.1.3. Change 2: McuSysClkDiv Recommended Configuration Update (Errata Advisory)

6.8.1.3.1. Description

Due to a silicon errata, issuing a device reset (XRSn — internal or external) can put the device into an unexpected fault state when SYSCLKDIVSEL.PLLSYSCLKDIV = 0, which corresponds to McuSysClkDiv = 1 (divide by 1). To address this, the recommended default value of McuSysClkDiv has been changed from 1 to 2 across all example presets. The configurator tool now displays a warning whenever McuSysClkDiv = 1 is configured.

No automatic migration is performed — users who currently have McuSysClkDiv = 1 must manually update their configuration to avoid the errata condition.

Warning

Silicon errata advisory: “System: Issuing device reset (XRSn) can cause unexpected fault if SYSCLKDIVSEL.PLLSYSCLKDIV = 0”. If your configuration uses McuSysClkDiv = 1, update it to 2 or higher to avoid this condition.

6.8.1.3.2. Old vs New

Behavior	v02.01.01	v02.02.00
`McuSysClkDiv` default value	`1` (divide by 1)	`2` (divide by 2)
Configurator warning when `McuSysClkDiv = 1`	Not present	Warning shown

6.8.1.3.3. Migration Actions

Check current McuSysClkDiv value: Open your Mcu plugin configuration and check the value of McuSysClkDiv in each clock setting
Update if set to 1: If McuSysClkDiv = 1, change it to 2 or higher. Using a value of 1 (divide by 1) triggers the silicon errata condition where a device reset (XRSn) can cause an unexpected fault state
Regenerate and rebuild: Regenerate configuration files and do a clean build

Note

For full details on this errata, refer to the silicon errata document: https://www.ti.com/lit/er/sprz569c/sprz569c.pdf

6.8.2. v02.00.00 (i.e release v01.03.00) from v01.01.00 (i.e release v01.02.00) Migration

6.8.2.1. Summary

Version v02.00.00 introduces configuration structure name changes to comply with AUTOSAR requirement TPS_ECUC_08011:

Configuration Structure Name Change: MCU configuration structure names updated for AUTOSAR TPS_ECUC_08011 compliance

6.8.2.2. Change 1: Configuration Structure Name Change

6.8.2.2.1. Description

Version v02.00.00 changes the configuration structure names for AUTOSAR TPS_ECUC_08011 compliance. This change ensures compliance with AUTOSAR naming conventions and requires updates to application code that references the MCU configuration structures. The specific structure names depend on the clock source being used in your configuration.

6.8.2.2.2. Old vs New Configuration Structure

Configuration Structure Name Mapping:

v01.01.00 and older	v02.00.00
`McuConf*`	`Mcu_Config*`

Note

The name of the configuration structures depends on the clock source being used.

Code Examples:

// v01.01.00 and older
Mcu_Init(&McuConf*);

// v02.00.00
Mcu_Init(&Mcu_Config*);

6.8.2.2.3. Migration Actions

Identify Current Structure Names: Determine the exact configuration structure names used in your project based on your clock source configuration
Search Application Code: Find all references to McuConf* patterns in your application code
Replace Structure Names: Update all references from McuConf* pattern to Mcu_Config* pattern
Update Function Calls: Ensure all MCU initialization calls use the new structure names
Update Upper Modules: Update any upper modules that reference the MCU configuration structures to use the new structure names
Verify Compilation: Clean build and verify no compilation errors related to MCU configuration structures