Arducam Mini 5MP OV5642 not detected by Arduino - ACK CMD SPI Error

Hi everyone, I’m stuck with my Arducam Mini Module Camera Shield 5 MP OV5642 Camera Module for Arduino. The controller just doesn’t detect it. In the serial monitor I keep getting ACK CMD SPI interface Error! END, and the exact same error shows up when I run the Arducam_host_v2 application. Has anyone run into this before?

Welcome to the forum. That error usually means the host isn’t getting a proper ACK back from the camera over SPI. Can you tell me a bit more about your setup? Which Arduino board are you using, and how is the camera connected to it?

I’m using an Arduino as the controller, running the Arducam_host_v2 application. The ACK CMD SPI interface Error! END message appears both in the serial monitor and in the host application. I’ve re-checked the wiring a few times and it looks correct, but the module just won’t respond.

Thanks. Before we dig into the module itself, let’s rule out the test setup. Do you have another OV5642 module you can try with the exact same wiring and the same code? That would help narrow it down to the module vs. the controller/wiring side.

Good idea - I tested another module of the same type using the same test procedure and it worked fine. So it really seems like the problem is with this particular module. I’ve attached a couple of screenshots showing the error I’m getting:

Screenshot 2025-03-10 170940.png
Screenshot 2025-03-10 170812.png

Thanks for the screenshots. Since a second, identical module works fine on the same setup and with the same test procedure, the issue is isolated to this specific unit. The ACK CMD SPI interface Error means the SPI interface on the OV5642 module is not acknowledging commands, which points to a defective SPI communication/hardware on the camera module rather than a software or wiring problem.

Any update regarding the issue? I just want to confirm whether there’s anything I can still try on my end, or if this particular module is basically dead.

I’ve gone through the details again. With an identical module working under the same test conditions, the failure is isolated to this one hardware unit. There’s no configuration or code change that’s going to fix it - the SPI interface on this OV5642 module isn’t acknowledging commands, so the conclusion is a hardware fault on the module itself.