For some of my test where I am using FreeRTOS, I need to set the CM7_CORE_CLK to the maxium frequency value (e.g., CM7_CORE_CLOCK=320MHz). Due to defined constraints the CORE_CLK needs to be set to CORE_CLK=160MHz.
As it looks like, the clock definition for FreeRTOS is fetched from CORE_CLK = 160MHz. Per my understanding, the provided "standard" implementation, FreeRTOS is using the SysTick timer to generate its RTOS tick. Furthermore, also per my understanding, the SysTick timer is driven by CM7_CORE_CLK and not by CORE_CLK. (As simple test showed the system running a double frequency when compiling this way.)
I can try to override the value using the CM7_CORE_CLK but get the warning as shown above. Is this an error of the S32DS configuration tool or do I miss anything else here?
Hi
Thank you for your report.
Let me contact the software team for a solution.
Best Regards,
Robin
My software colleague told me:
The warning is safe to be ignored, has no implications on software behavior.
The user should set the real clock frequency input as he already did and can safely ignore the warning.
Hi @Robin_Shen,
thanks for the reply. I understand I can enter the correct core frequency CM7_CORE_CLK into the field and safely ignore the resulting warning.
Is there a plan to fix that issue in the future? I am not a fan of unnecessary warnings as they may clutter other important warnings and create additional effort in the build process.
Thanks.
Thank you for the report! This will be corrected in the next FreeRTOS s32k3xx release.