No response from OV5640

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

No response from OV5640

Jump to solution
1,824 Views
t-sugiyama
Contributor II

Hello,
I am making a program that uses MINISASTOCSI (OV5640) and cortex-M4 to communicate by I2C with iMX8MminiEVK.
However, I cannot confirm the response from the I2C camera.
The I2C driver uses MCUexpressoSDK (SDK_2.7.0).
When I use an oscilloscope to look at the I2C SDA and SCL lines, I have confirmed that the OV5640 does not respond with an ACK to the I2C slave ID but becomes a NACK.
Slave address is set to 0x3c.
"PWDN" and "RESETB" of OV5640 are controlled by referring to "ov5640_probe" of "ov5640_v2.c" of "i.MX Linux Rev. L4.19.35_1.1.0, 11/2019".
Is there anything else to be aware of?

Thanks.
Tetsuya.

Tags (2)
0 Kudos
1 Solution
1,645 Views
igorpadykov
NXP Employee
NXP Employee

Hi Tetsuya

it works fine with Demo Image, had you tried it.

Linux Binary Demo Files - i.MX 8MMini EVK

Best regards
igor

View solution in original post

0 Kudos
7 Replies
1,645 Views
igorpadykov
NXP Employee
NXP Employee

Hi Tetsuya

so do you see i2c signals from i.MX side ?

One can check hardware, if i2c has correct voltages and sensor connections.

For software one can try to test i2c3 running only linux, without FreeRTOS

fsl-imx8mm-evk.dts\freescale\dts\boot\arm64\arch - linux-imx - i.MX Linux kernel 

Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

0 Kudos
1,645 Views
t-sugiyama
Contributor II

Hello igor,

Thank you for taking the consultation.
I confirmed that a normal I2C signal was output when the "OV5640" was connected by operating "i.MX8MminiEVK" with "i.MX Linux Rev. L4.19.35_1.1.0, 11/2019" .
The attached file is the first I2C signal that “i.MX Linux” outputs to “OV5640”.
I don't think there is a hardware problem.
I anticipate that the way I am currently challenged lacks the conditions to launch the OV5640.

IMX2OV5640.jpg

Best Regards,
Tetsuya

0 Kudos
1,645 Views
igorpadykov
NXP Employee
NXP Employee

Hi Tetsuya

 

what board used in the case: custom ot i.MX8M Mini EVK ?

 

Best regards
igor

0 Kudos
1,645 Views
t-sugiyama
Contributor II

Hello igor

The board used in this case is 8MMINILPD4-EVK.

It is a board of the following site.

https://www.nxp.com/design/development-boards/i-mx-evaluation-and-development-boards/evaluation-kit-...

In particular, we have not modified the board.

Best regards

Tetsuya


0 Kudos
1,645 Views
igorpadykov
NXP Employee
NXP Employee

Hi Tetsuya

please try with Demo Images

Linux Binary Demo Files - i.MX 8MMini EVK

OV5640 camera can be tested using MINISASTOCSI daughter card

Design Files for the Camera Module (MINISASTOCSI)

for test use the fsl-imx8mm-evk.dtb with command :
gst-launch1.0 v4l2src device=/dev/video0 ! autovideosink

Best regards
igor

0 Kudos
1,644 Views
t-sugiyama
Contributor II

Hello igor,

I found that "MIPI_CSI_MCLK" of "MINISASTOCSI" did not occur.
Since "24MHz DNP" is not implemented in "MINISASTOCSI", I think that clock will be generated if "GPIO1_IO14" of i.MX8Mmini is set to "CCM_CLKO1" by "IOMUXC".
However, I do not know the frequency setting for "CCM_CLK01".
Where can I find the frequency setting for “CCM_CLK01” in “i.MX 8M Mini Applications Processor Reference Manual, Rev. 2, 08/2019”?

Best Regards,
Tetsuya

0 Kudos
1,646 Views
igorpadykov
NXP Employee
NXP Employee

Hi Tetsuya

it works fine with Demo Image, had you tried it.

Linux Binary Demo Files - i.MX 8MMini EVK

Best regards
igor

0 Kudos