ESP32-P4 CSI no fram callback with TI DS90UB954

[otalkaline]

Hi everyone,

I’ve been testing the ESP32-P4 CSI-2 controller for a few weeks. I adapted the official examples and some test apps to replace a regular MIPI camera with a TI DS90UB954 deserializer.
The issue: the frame callback never fires on ESP32-P4, while the same 954 output works fine on an FPGA/SoC and looks healthy on the scope.

Setup
SoC: ESP32-P4 evboard 1.5.2
Deserializer: TI DS90UB954
954 output data rate: 400 / 800 / 1600 Mbps (per lane); tried 400 and 800 → no frames on ESP
Test patterns (CEA-compliant):
1280×720 @ 60 Hz, RAW12 (CSI-2 DataType 0x2C)
1920×1080 @ 30 Hz, RGB888 (CSI-2 DataType 0x24)

What I observe / already checked
954 does generate a valid test pattern (verified with FPGA/SoC).
On ESP32-P4 I never get the first frame (no callback/event), init completes without errors.


I’m basing my tests on this IDF example (exact commit): components/esp_driver_cam/test_apps/csi/main/test_csi_ov5647.c @ 25c40d4563be7d4caf375b59c52283ff80c62d08.
I just changed the sensor resolution and added a frame/byte counter that prints FPS/throughput every second. Once the example is compiled, everything works as expected.

Frames OK: 0 | +0 fps | Frame size: 4147200 B | Total bytes: 0 | ~0 B/s
Frames OK: 30 | +30 fps | Frame size: 4147200 B | Total bytes: 124416000 | ~124416000 B/s
Frames OK: 60 | +30 fps | Frame size: 4147200 B | Total bytes: 248832000 | ~124416000 B/s

In the ub954 version, I completely removed the example_sensor_init(&sensor_config, &sensor_handle) and replaced it with the ub954 programming. Unfortunately, I can't see any input bytes. I also modified isp accordingly, removing it completely if I entered rgb888 directly.

Do you have any tips to share on how to figure out what is preventing the callback from triggering?

Regards

[otalkaline]

Hi,

do you have any suggestions on which registers I should check to investigate further?
I’ve run additional tests, but I still can’t manage to trigger the event.

Thanks for your help!