2025-03-19 4:14 AM
Hello,
I'm trying to generate code from a CubeMX project for STM32MP257f-ev1: my concern is that I've turn on PLLs from CubeMx Clock Configuration tab but code for PLLs clock configuration is not generated in SystemClock_Config function. In main.c I get only the following:
void SystemClock_Config(void)
{
__HAL_RCC_MCO1KERCLK_SETSOURCE(RCC_MCO1CLKOUTPUTSOURCE_CLK_MCO1);
}
Maybe I missed something but I can't find out, can someone please help me?
In attachment you can find the project .ioc file
Marco.
Solved! Go to Solution.
2025-03-19 9:49 AM
Hi @MBassi ,
Developer (Engineering) mode is not supported on MP2, you have to use "Production mode" where Linux setup the system and load the coprocessor.
CubeIDE integrate natively this way of working for M33 debugging.
Pay attention to properly allocate resource you want to use on M33 in CubeMX, and rebuild Linux A35 part with generated DeviceTree to apply change.
Hope it help,
Olivier
2025-03-19 4:25 AM
Hi @MBassi ,
You are refering to M33 corprocessor generated code.
On STM32MP25, with A35 as Trusted CID (only configuration supported today) all clock configurations are done on OpenSTLinux side running on A35.
All the clock tuning you made might be visible in the DeviceTree generated for the CA35.
For further information, please refer to our Wiki documentation starting from Yocto-based OpenSTLinux software architecture overview - stm32mpu
Hope it help
Olivier
2025-03-19 4:40 AM - edited 2025-03-19 4:41 AM
Ok, thank you very much @Olivier GALLIEN for fast replying,
I understand but now the question is: if I want to write code for M33 to test with the stm32mp257f-ev1 in developer (engineering) mode I have to write the code for Clock configuration by myself or I can use some other tool which help me writing clock configuration code?
Marco.
2025-03-19 9:49 AM
Hi @MBassi ,
Developer (Engineering) mode is not supported on MP2, you have to use "Production mode" where Linux setup the system and load the coprocessor.
CubeIDE integrate natively this way of working for M33 debugging.
Pay attention to properly allocate resource you want to use on M33 in CubeMX, and rebuild Linux A35 part with generated DeviceTree to apply change.
Hope it help,
Olivier
2025-03-19 11:12 AM
Thank you @Olivier GALLIEN,
Now I can understand why CubeMx do not generate code for PLLs clock in SystemClock_Config function. I will use "production mode" for debugging after updating linux device tree with changes from CubeMX.
Marco.