s32k312 mcal Autosar pre compile variant handling not working as expected

[Azharudeen47]

Problem: It is expected that MCAL modules from NXP is also configurable for variant pre compile support from Da vinci configurator But MCAL modules are not generated as expected with variant precompile support configuration  ,

In eb tresos  '.c' files are generated sepererately for each variant (eg: port_pcCfg_Xvariant.c and port_pcCfg_Yvariant.c) for each mcal modules . 

expectation: The expectation from Davinci configurator generation step is that that, the ‘.c’ file generated for a particular module which is configured for different variants with precompile variants support (say for x and y variants) will have the configuration for each variants (configuration for x and configuration for y) stored separately in unique array index (say index 0 for x variant and index 1 for y variant) of  the configuration pointers array, all in the same .c file for that module.

Even though, for non mcal modules this is how '.c' files are generated in Davinci configurator, For MCAL modules even with enabling support and configuring for different variants there were no difference in how '.c' files were generated wrt to how '.c' were generated when no variants were configured (neither configuration pointer array having each index corresponding to each variant nor separate '.c' files for each variants were generated)

Even though, this is different from how '.c' files were generated for non MCAL modules in Davinci configurator. Seperate '.c' files for variants (eg: port_pcCfg_Xvariant.c and port_pcCfg_Yvariant.c) in mcal modules are not generated from Davinci configurator, and this behaviour for mcal modules were only observed from eb tresos

Query: I would like to know whether it will be possible to make sure MCAL modules will generate '.c' files from Davinci configurator as per the expectation i.e, for a particular mcal module the generated '.c' file will have configuration pointer created as an array with each index element corresponding to a particular variant (eg: index 0 for x variant and index 1 for y variant)?

If NXP mcal does not support this, will it be possible for Davinci configurator to resemble the behavior shown when files where generated from EB-Tresos with variant pre compile support (ie seperate .c files for each variant eg: port_pcCfg_Xvariant.c and port_pcCfg_Yvariant.c)

S32K312EVB-Q172 

[Julián_AragónM]

Hi @Azharudeen47,

In the MCAL package, there are some specific configuration files used to import the modules and variants into Davinci. If you have issues configuring Davinci, please contact Vector expert team for support.

Here are some related community posts:

• How to integrate the EB Tresos generated code into S32DS? - NXP Community
• Solved: MCAL Variant Handling in EB Tresos - NXP Community

Best regards,
Julián