Hi Guenter,
I've done some tests looking at CP_LOCK_RAW, with CP_LOCK_UNLOCK_EDGE_SEL set to both 1 and 0. The behavior made more sense with it set it to 0, though the CP LOCK event never occurs: it unlocks, but never locks. What does that mean? It doesn't sound good.
I also tried looking at STDI_DATA_VALID_RAW, and this looks a bit better (it locks after the v filter), but it still isn't waiting long enough for the measurements to be valid.
I'm not clear whether the HDMI Synchronization Parameters are measured by the CP Block or somewhere else. It looks like the CP block provides some measurements (Vsync, Vtotal). Is the STDI algorithm using the same measurements that are reported as HDMI Synchronization Parameters, or are these from a totally different block?
Tim