Hi,
We are supporting a customer working with the S32K116 and the NXP MBDToolbox v4.3.0 for MATLAB/Simulink.
The customer experienced issues when switching from external to internal clocks, particularly with peripheral modules like ADC, LPIT, and FTM not being initialized correctly unless manually configured. To provide a more robust and maintainable approach, we proposed centralizing all peripheral clock settings using the clock_manager_user_config_t structure inside a custom s32k_clock_init.c file.
We have attached both the original file provided by the customer and a cleaned-up version we prepared, based on the recommended ClockManager structure and peripheral configuration approach.
We would appreciate your feedback on the following points:
1. Does this centralized configuration approach align with best practices for projects using the MBDToolbox?
2. Could there be any conflicts or unintended behavior when peripheral blocks in the Simulink model also generate their own initialization code?
3. Are there any known issues or constraints when using manual ClockManager-based configuration in parallel with Simulink-generated code?
If this falls outside the scope of your team, we would appreciate it if you could help redirect this to the appropriate contact within NXP.
Thank you in advance for your time and support.
Best regards
