Why is it hardcoded to use <modelname>.sldd as data store?

[Henrik-Wires]

Why does the NXP MBDT hardcode <modelname>.sldd as external data store?

This conflicts with other uses of external model data store, and makes using referenced configurations harder than it needs to be.

Mathworks recommended setup for referenced configurations is to use a common shared sldd for the configurations in the project, and link this to each model. But if you do this method with NXP MBDT then MBDT overrides the data store next time you open the model, and MBDT also gets very confused.

[dragostoma · Accepted solution]

Hi, @Henrik-Wires,

For reference, you can review the s32k3xx_refconfig_s32ct model structure located in the model_ref folder. This example illustrates how referenced configurations are applied within a model‑reference hierarchy: the top‑level model’s SLDD is referenced by the subordinate models through the use of Referenced Dictionaries.

If you prefer to apply the referenced‑configuration approach within a standard model hierarchy (rather than a model‑reference hierarchy), you can create a standalone SLDD file and reference it from each model‑specific SLDD that requires this configuration. This is done using the same mechanism described earlier, through the Referenced Dictionaries section.

Hope this helps, 

Dragos

[Henrik-Wires]

Thanks. I'll give it a try.