Topic: Clock Configuration Tool
Customer: Internal
On copy: @rushikeshmunde
Issue identified when trying to use the Clock Tool to configure the CSI2 module via COREPLL_PHI4. The S32R47_Clocking.xlsx sheet attached to the RM states that the max frequency of this clock is 100MHz however they get an error that says the maximum frequency must be between 0-40MHz.
Hello Joe,
I can confirm that DDR_DFS1_CLK has the same error on my side. There is an error in C:\NXP\S32DS.3.6.1\eclipse\mcu_data\processors\S32R47\PlatformSDK_S32R4X\clocks\TOP.xml
You should replace the 530 Mhz with 800.
Hi Marius,
I have just tried to configure the DDR_CLK using the clocks tool and I am running into another error. I have only just updated to the latest RTD update sites so I am curious to see if you can replicate this on your side or if it is a package issue on my side.
Based on the RM I should be able to configure DDR_CLK up to a maximum of 800MHz. When trying todo this using the Clocks Tool I am getting an error on the output of the DDR_DFS1 frequency that says:
"The output frequency must be lower than or equal to 530 MHz" (see attached image)
This is in contradiction of the maximum stated output of the DDR_DFS1_CLK which is 800MHz as per RM.
Hello @JDonnelly ,
I have created a JIRA ticket for RTD to solve this in the future release: https://jira.sw.nxp.com/browse/ARTD-203323
For now the client can manually change the following files with the respective numbers in order to unblock them:
C:\NXP\S32DS.3.6.1\eclipse\mcu_data\processors\S32R47\PlatformSDK_S32R4X\clocks\TOP.xml
C:\NXP\S32DS.3.6.1\eclipse\mcu_data\processors\S32R47\PlatformSDK_S32R4X\clocks\MODULE_CLOCKS.xml
...
C:\NXP\S32DS.3.6.1\S32DS\software\PlatformSDK_S32R4X\RTD\Resource_TS_T40D95M8I0R0\resource\CORTEXM_S32R4X_s32r47_bga548.properties
MCU.SysClock.Limits.CSI_CFG_CLK.High:250000000
Once the new numbers are applied a restart of Design Studio should clear the error and be able to use the clocks at maximum frequency as the user manual says.
If you have any other questions please let me know.
--Marius
Hello @JDonnelly ,
I have reproduced the issue on my side as well and now we are investigating to see what causes this issue and even try to provide you a workaround until the fix is officially released.
I will come back with an answer as soon as possible.
--Marius
Closing this since there is nothing else the support team can do. The workaround was accepted and actual fix is tracked in JIRA ticket.