Few years ago, I implemented communiication with ArduCam 2MP mini (Rev.B) in embedded linux module. Everything worked fine - device captured jpeg pictures in different resolutions.
Now I got new pieces of ArduCam (module UC.474 Rev.D) and with these, communication via I2C (SCCB) is not working corretly.
For example I cannot read some ov2640 register values. I can write registers and different settings, but soon the bus became stucked - clock signal is low until power down/up camera.
I2C signals seems to be ok, clock frequency 400kHz (I tried lower with no diffrence in communication).
Has anyone encountered this kind of camera behavior?
Hello I faced the same problem. I have SPI 2MP Plus Rev. D and I can’t even run test examples from the official repo.
Hi,I have the same problem with the ov2640 mini 2mp plus Rev. D (Rev. A Rev. B working fine) i can’t write registers, any new insights?
Hi @josh,
The 2MP MINI SPI camera is officially optimized to run using our standard library found here:
Regarding low-level register access:
Direct modification of sensor registers falls outside the scope of our public drivers and documentation. If your project specifically requires this level of advanced control (e.g., for writing custom registers), please contact our Sales Team to discuss this as a customization request.
Hi Dion,
I have tried using the library for my project and still I am unable to receive any acknowledgement from the sensor, and I2C is not working any further. Could you please help me with this issue. I am using UC 474 Rev D.
Could you plz elaborate on your setup? Including the hardware and the software.
Yes, I have been using CY8CPROTO-062S2-43439 PSoC™ 62S2 Wi-Fi Bluetooth prototyping kit and Arducam Mini Sheild 2MP Plus Camera ( Rev D). The software I am using is Modus Toolbox. I am connecting the I2C and SPI pins via jumpers to the microcontroller. It is in FreeRTOS and C language.