2026-06-07 11:21 AM
Hello,
I'm having trouble getting a lock with the DCMI. Lots of information below as required.
Has anyone seen ACTCLF permanently stuck at 0 on STM32N6 despite confirmed HS clock at the input? Are there any additional SNPS D-PHY initialization steps beyond what HAL_DCMIPP_CSI_SetConfig performs. For example, a calibration trigger or an additional register write needed for the clock lane specifically? The SNPS D-PHY databook is not publicly available for STM32N6; if there are clock-CDR-specific internal registers beyond 0xe2/e3/e4 (which appear to be DL0 DDL registers), we have no way to know without that document.
Hardware: STM32N657X0HxQ + Sony 12MP image sensor, 1-lane CSI-2, 1188 Mbps (27 MHz INCK × 44), continuous HS clock mode.
Symptom: The SNPS D-PHY clock CDR never acquires lock.
What IS working (confirmed):
STM32N6 DCMIPP/D-PHY configuration — all verified:
SNPS D-PHY internal registers (written while PWRDOWN=0):
Sensor-side timing registers (I2C readback confirmed):
- All 27 INCKSEL registers correct
- TLPX=0x003F, THS_ZERO=0x009F, TCLK_ZERO=0x014F, HMAX=0x0EF1 - all confirmed
SetConfig timing: Called during inter-frame LP-11 gap (confirmed by init_ulpn_wait_sr1=0x76101000 showing STOPCLF=1|STOPDL1F=1 at call time). init_setconfig_res=0x0 (HAL_OK). PEN=1 fires while clock is in LP-11, so the LP -> HS transition should be available for CDR acquisition. CDR still does not lock.
We’re moving the ST Community to a new platform to give you a better and more reliable community experience.