i.MX93 FRDM: OV5647 camera Module

[20DeViL00]

Board: i.MX93 11x11 FRDM
Kernel: linux-imx 6.6.36-lts-next-ga48f13726335 (Yocto)
Camera: OV5647 (Raspberry Pi compatible module)

Hi,

I am trying to bring up an OV5647 camera on the i.MX93 FRDM board.
At this stage, I would like to validate whether my device tree patch is correct before continuing further debugging, since the issue could be either in the patch or in the hardware integration.

I created a custom Yocto layer and added a new DTS file for the OV5647, based on the existing OV5640 reference design for this board.
The patch builds successfully and the DTB is generated, but the camera is not detected on the I²C bus.

Before investigating hardware or signal-level issues, I would like to confirm that the DTS structure and bindings are correct.

I've attached my patch as well as dts file.

Additional details:

• OV5647 driver is enabled in the kernel: CONFIG_VIDEO_OV5647=y

• I²C buses are present, but address 0x36 is not detected.

At this point, I would like to confirm:

1. Is the OV5647 sensor node structured correctly for the i.MX93 FRDM platform?

2. Is the clock configuration using CKO1 appropriate for this sensor?

3. Are any required properties missing compared to a typical i.MX camera integration?

Any feedback on the DTS patch structure would be appreciated.

Thanks.

[Chavira]

Hi @20DeViL00,

Thank you for contacting NXP Support!

At the moment, this specific camera module has not been validated with our BSP. Because of that, we are unable to provide an official or fully verified device tree configuration for this sensor.

However, after reviewing the files you shared, I noticed several issues that may be causing the behavior you're seeing:

1) CSI Connector Orientation
Please verify the orientation of the CSI connector on your board. The connector is keyed and can only be inserted in one direction. If the FPC cable is reversed, the contacts may not align properly, which prevents communication with the camera.

2) Incorrect Reset Pin
Your device tree sets:

reset-gpios = <&pcal6524 21 GPIO_ACTIVE_LOW>;

However, according to the board schematic, the correct CSI reset pin is 22, not 21.
Please double-check this against your hardware documentation.

3) You currently configure the clock pin as a GPIO. Please confirm whether this is actually required for your camera module. In many cases, the MCLK (camera clock) should not be controlled as a GPIO, and doing so may prevent proper sensor initialization.

For further reference, we recommend starting from the base device tree and applying modifications step by step, ensuring each signal matches the schematic and camera requirements.

Best Regards,

Chavira

[20DeViL00]

Hi Chavira

Thank you for your response and for reviewing the files I shared.

I tried the changes you suggested, but it did not work. The output is still the same.

Please let me know if there are any additional checks or logs you would like me to provide.

Best regards,
Aman Sharma

[Chavira]

Hi @20DeViL00,

At the moment, this specific camera module has not been validated with our BSP. Because of that, we are unable to provide an official or fully verified device tree configuration for this sensor