Hi，nxp
I'm testing the pfe_master project, using the MasterProject_RDB2 project from PFE-DRV_S32G_M7_MCAL_1.3.0, and I found that the initialization initialized the clock McuClockSettingConfig_0 first, and then re-initialized the clock after doing some module initialization McuClockSettingConfig_1, may I know the reason for this?
Why do I need to initialize the clock twice?
Hello, @youke
Thanks for your reply.
From my understanding, it is difficult to do it once, since several steps needed for initializing the related clock.
Regarding to the method of initializing it, theoretically, it could be done either from the bootloader or the M core application itself, it depends only on your design.
If putting all clock init phase to the bootloader, then you may need to implement similar steps from teh PFE example to the bootloader to initialize the pfe, and then remove the corresponding phase from the M core application itself(pfe master exmaple.) to avoid any conflict.
BR
Chenyin
Thank you for your reply
How do I need to do to initialize the clock only once?
Or can you help me to explain how I need to do the whole initialization logic if I use bootloader to boot the M core and use the pfe_master function?
Hello, @youke
Thanks for your post.
The first init could initialize clock for serdes module, while the second one is used for initializing serdes for the MUX.
I hope it will help.
BR
Chenyin