Model configuration differs from the model used to generate the shared utility code folder

Hello,

So recently I update some model, and inside i brought some referenced models . Those referenced models have the configuration parameters exactly as the parent model, and configuration parameters were propagated though each referenced model.

When i m trying to generate the code ( embedded coder) basically the error showing is this: Error building model 'APP_SWC'. The current model configuration differs from

the model configuration used to generate the shared utility code folder,

APP_SWC\SourceCode\slprj\autosar\_sharedutils'.

Click here to review parameter differences between 'APP_SWC' and

APP_SWC\SourceCode\slprj\autosar\_sharedutils'.

The shared utility code folder also contains code from the model

'ReferencedMODEL'. However, the parameter settings of the referenced model

and the current model do not match.

The idea is that I have a Package for the memory sections, so when i press click here to review parameter different it shows the parent model with default value on UtilSecMemName .

I tried to delete all things generated in source code, no impact. No change in hardware or something similar, so i m not really sure how to approach this

Answer 1

[Isha]

Hello,

This error usually indicates a configuration mismatch somewhere in the model hierarchy. Even when configuration propagation is enabled, Embedded Coder requires the effective code generation settings of the parent model, referenced models, and generated _sharedutils artifacts to remain consistent.

Since the parameter difference report highlights UtilSecMemName, I would investigate the memory section configuration and Code Mappings/Embedded Coder Dictionary settings, as these can differ even when the visible configuration parameters appear identical.

As a troubleshooting step, try deleting all generated artifacts and caches before rebuilding:

• slprj
• <model>_ert_rtw (or corresponding code generation folder)
• All .slxc files

The .slxc cache files can contain shared utility and code generation artifacts for referenced models, so deleting only the generated source code folder may not be sufficient.

Relevant documentation:

• Set Configuration Parameters for Code Generation of Model Hierarchies
• Migration of Memory Section and Shared Utility Settings to Code Mappings.
• Simulink Cache Files for Incremental Code Generation

Given that the reported mismatch is specifically UtilSecMemName, verify that the same memory section package and shared utility memory section settings are being resolved by both the top model and all referenced models before regenerating code.

Hope this helps.