S32G2 CMU - how to validate correct behavior?

[justinlydick]

Customer Ford is configuring S32G CMU_FC with the RTD 1.0.0 package, using Mcu driver.  They plan to use it to monitor several clock frequencies during run-time.

Question: what methods are available to verify CMU is behaving correctly?  Customer would like to verify the software configuration is correct by running through all monitored clocks and verify CMU generates reset or interrupt when monitored clock goes out of configured threshold range. What can be done to verify this, with the exception of manually changing clock register values?

[martinkaspar-r3 · Accepted solution]

NXP provides a method to verify CMU_FC by the SAF sCheck module. sCheck is able to verify CMU_FC at startup/runtime/shutdown phase using CMU_FC tests. At the runtime the tests initialize CMU_FC to raise fault either to FCCU or to GIC500. Tests handles the faults and check if expected fault flags are set to handle that correct threshold has been crossed.
The SAF sBoot module provides capability to check at the startup that CMU_FC thresholds are correctly configured.