Skip to main content
Associate
January 22, 2026
Question

CubeMX does not validate CSI clock configuraiton on the STM32N6

  • January 22, 2026
  • 1 reply
  • 248 views

The STM32N6 reference manual shows that IC18 drives the CSI2Host and CSIPHY IP blocks at a maximum frequency of 200 MHz. CubeMX generates this clock configuration code but does not show the clock path in the clock configuration window. Additionally, it does not provide any error checking and will allow IC18 to be configured above 200 MHz.

Clock tree diagram:

xJIomqygrecz_0-1769099799615.png

Maximum clock rate spec:

xJIomqygrecz_1-1769099870696.png

CubeMX generated code in HAL_DCMIPP_MspInit:

PeriphClkInitStruct.PeriphClockSelection = RCC_PERIPHCLK_DCMIPP|RCC_PERIPHCLK_CSI;
PeriphClkInitStruct.DcmippClockSelection = RCC_DCMIPPCLKSOURCE_IC17;
PeriphClkInitStruct.ICSelection[RCC_IC17].ClockSelection = RCC_ICCLKSOURCE_PLL4;
PeriphClkInitStruct.ICSelection[RCC_IC17].ClockDivider = 1;
PeriphClkInitStruct.ICSelection[RCC_IC18].ClockSelection = RCC_ICCLKSOURCE_PLL4;
PeriphClkInitStruct.ICSelection[RCC_IC18].ClockDivider = 2;

 

1 reply

Ghofrane GSOURI
Technical Moderator
January 23, 2026

Hello @xJIomqygrecz 

I'm currently checking this behavior. I will get back to you asap.

THX

Ghofrane

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
Associate
January 29, 2026

@Ghofrane GSOURI, were you able to confirm this bug?