2026-01-01 10:18 PM - last edited on 2026-01-02 11:35 AM by mƎALLEm
I am working on the NUCLEO-H755ZI-Q, which contains a dual-core STM32H755 (Cortex-M7 + Cortex-M4).
I configure the system clocks in CubeMX as follows:
However, when I debug or read the CM4 core clock, I always see:
Regards,
Prathiksha
2026-01-02 1:31 AM
How you "see" the 64Mhz ?
2026-01-02 6:31 AM
It's probably an issue with how you're running the program. If the CM7 core is doing the clock configuration, it needs to do that before the clock will be updated. Just running the CM4 side will use the default clock (64 MHz).
2026-01-02 11:35 AM
@Prathiksha wrote:However, when I debug or read the CM4 core clock, I always see:
- CM4 clock = 64 MHz
How did you check that?
2026-01-04 9:18 PM
These are the below functions used to verify the clock.
2026-01-04 9:19 PM
These are the below functions used to verify the clock.
2026-01-04 9:39 PM
Yes, I’m aware that the CM7 core needs to configure the clocks for CM4. While debugging both CM7 and CM4, I ran CM4 to verify the clock because it was showing 64 MHz. I was using DMA for ADC in our project, and since DMA requires a higher frequency, I suspected a clock issue. However, the actual problem was related to DMA.
2026-01-05 12:50 AM - edited 2026-01-05 12:55 AM
What API you have used to get the CM4 clock?
Please share your project so we can reproduce the behavior and understand what is going on...
2026-01-05 5:53 AM
2026-01-05 6:29 AM
Hello and thank you for the sharing. I don't see where do you get the CM4 in the attached firmware. Could you please clarify?