Hello,
I am developing using S32K314. My development environment uses S32DS 3.5 for IDE and SW32K3_RTD_R21-11_3.0.0_P07 for RTD.
I am setting up my development environment using ConfigTools.
The FreeRTOS component was added and set, and the FreeRTOS clock is set in the FreeRTOS configuration settings. I want to set the config mode to "Default Clock", but cpu clock [Hz] is only set to 0.
So, I am currently using it by forcibly setting the clock to “User Clock”. In this case, a warning message occurs.
Please tell me how to make the clock apply automatically when set to "Default clock".
Solved! Go to Solution.
Hello @jwkang,
After checking the freertos.component file, the default value of cpu clock was obtained from the symbol default "ClockConfig0". So, if you change to ClockConfig2 then the cpu clock can't get from clock configuration tool and this is a bug of freertos. And, the FreeRTOS team raised a bug ticket for this issue and it will be fixed on the releases in the future.
Best regards,
Dan
Hello @jwkang,
Did you enable the clocks?
Once it is enabled, you should see the core clock frequency there:
BR, Daniel
Yes, there is still a warning issue in the project.
I am using it as the "user clock" value. So there are no problems with the project progress.
I just want to know if it's a problem with my settings incorrectly or an SDK problem.
Please be specific, what kind of warning?
Thank you,
Daniel
Which version of SW32K3 FreeRTOS do you have?
Thank you
I mean the version of the SW32K3 not the Kernel
Also, have you tried creating a new FreeRTOS project from Example?
BR, Daniel
S32DS Project from Example
Hello @jwkang,
Your image indicated that you are using D2303 - SW32K3_RTD_4.4_R21-11_3.0.0 instead of D2306 - SW32K3_RTD_R21-11_3.0.0_P07 as you said. This is the correct package you need to install with FreeRTOS 10.5.1
I checked your issue on this package and there is no error occur with S32K314 (cpu clock always link correct the CORE_CLK value on the Clock tool configuration).
Best regards,
Dan
I tested it, and it doesn't seem to have anything to do with the update.
In the Functional Group of Clocks, the default name is ClockConfig0. Even if you change this name slightly, problems will arise.
It appears to be a problem related to the ClockConfig0 name.
ClockConfig0 -> OK
ClockConfig2 -> Not ok.
Hello @jwkang,
After checking the freertos.component file, the default value of cpu clock was obtained from the symbol default "ClockConfig0". So, if you change to ClockConfig2 then the cpu clock can't get from clock configuration tool and this is a bug of freertos. And, the FreeRTOS team raised a bug ticket for this issue and it will be fixed on the releases in the future.
Best regards,
Dan