ESP32 CAM Driver Issues?

Hello I getting the following error message everytime I try to compile this sample WifiScan code:

ERROR CODE
Arduino: 1.8.19 (Windows Store 1.8.57.0) (Windows 10), Board: "ESP32S3 CAM LCD, Core 1, Core 1, Default 4MB with spiffs (1.2MB APP/1.5MB SPIFFS), 921600, None, Disabled"

Sketch uses 672681 bytes (51%) of program storage space. Maximum is 1310720 bytes.

Global variables use 43396 bytes (13%) of dynamic memory, leaving 284284 bytes for local variables. Maximum is 327680 bytes.

esptool.py v4.5.1

Serial port COM9

Connecting......................................

A fatal error occurred: Failed to connect to ESP32-S3: No serial data received.

For troubleshooting steps visit: Troubleshooting - ESP32 - — esptool.py latest documentation

the selected serial port For troubleshooting steps visit: Troubleshooting - ESP32 - — esptool.py latest documentation

does not exist or your board is not connected

This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.
ERROR CODE END

I am using a ESP32 Cam connected to a FTDI. I am connected to COM 9, which based on my device manager, is the "USB Serial Port" that showed up when I attached the FTDI by USB cable to my computer.

On Arduino IDE, I am using the board "ESP32S3 CAM LCD".

I have tried "update driver" for this port in the device manager to add the CP210x_Universal_Windows_Driver and it just says that Windows thinks this port is up to date.

Am I updating the driver in the correct place? Am I using the correct "board" name in Arduino IDE? Any other mistakes or advice would be greatly appreciated. Thanks!

Hi @bgreiner999. Try this:

  1. Disconnect the USB cable of the FTDI from your computer.
  2. Use a jumper wire to connect the pin labeled "IO0" on the ESP32-CAM board to the pin labeled "GND".
    This is required to put the ESP32 microcontroller into the boot mode that allows the upload. On a self-contained board, there is a circuit that does this automagically, but with your setup of just using an "FTDI" you must do it manually.
  3. Connect the USB cable of the FTDI to your computer.
  4. Select Sketch > Upload from the Arduino IDE menus.
  5. Wait for the upload to finish successfully.
  6. Remove the jumper wire from the "IO0" and "GND" pins on the ESP32-CAM board.

If the upload fails, post the new upload error and we'll investigate further.

rather than using a FTDI programmer I find it simpler to use a ESP32-CAM-MB micro USB programmer

ptillisch,

To be totally clear, I connected the GND pin on my FTDI to the IO0 on the ESP32-CAM. Then I tried uploading a blank sketch. I got the following error:

Sketch uses 247221 bytes (7%) of program storage space. Maximum is 3145728 bytes.
Global variables use 21040 bytes (6%) of dynamic memory, leaving 306640 bytes for local variables. Maximum is 327680 bytes.
esptool.py v4.5.1
Serial port COM9
Connecting......................................

A fatal error occurred: Failed to connect to ESP32: No serial data received.
For troubleshooting steps visit: Troubleshooting - ESP32 - — esptool.py latest documentation
Failed uploading: uploading error: exit status 2

If I am still clueless on this by the end of the day. I just might take your advice on this.

I agree with @horace's recommendation about using the ESP32-CAM-MB. It makes the ESP32-CAM into an easy to use standalone board as we are used to working with in the Arduino ecosystem. I definitely recommend anyone who is purchasing an ESP32-CAM to spend a little bit more to get the package that includes the ESP32-CAM-MB along with the ESP32-CAM component.

That said, it is definitely possible to use a USB to serial bridge module or cable such as those based on the FTDI FT232R chip in place of the ESP32-CAM-MB. It just makes things a bit more complicated and less convenient.

Please provide a list of the exact connections between the two.

If you are seeing a serial port in Device Manager then it should not be necessary to install a driver. You say you are using an "FTDI". If by that you mean that you have one of the common modules or cables based on the FTDI FT232R chip, then installing the CP210x would be pointless because that driver is for a completely different chip.

That should be fine. The ESP32 not being in boot mode due to the "IO0" not being grounded is only one of the possible causes of the upload failure you are experiencing. We will consider that potential cause to be eliminated and now look elsewhere for the cause of the upload failure.

Thank you sm for the detailed response.

I am using the set up found in the following link:

I have tried using different GNDs on the ESP32 Cam as well.

Also I bought the parts off Amazon here in case that is helpful:

https://a.co/d/6M249ID

The wiring shown in the tutorial looks fine. Please double check to make sure you have it exactly as shown there.

Something that is maybe a bit confusing is that you must make the connections like this:

FTDI ESP32-CAM
RX U0T
TX U0R

Should I keep the IO0 and the GND connected like you said in a previous post or should i do exactly like the schematic on that link I sent says? I am making sure those tx and rx pins are correct as well.

Hi I have ESP32 CAM like yours from AI thinker, and lost 2 days trying to upload the firmware and had the same problem...it was frustrating, I hope it's corrected with new models, but maybe you have the older one.
There is a error on the pcb, the thing is that there are two GND pins on the pcb and one of them is not the real GND! Check with DMM, to measure resistance between two GND pins, it should be zero but is not.
I don't remember exactly, (it was year ago) but I think that the real GND is the one next to 5V pin. Use that one and it should work.
Cheers!

GPIO0 should be connected to GND only when uploading the firmware.

Wow this worked! Thank you all for all the help!!!! One of the most helpful forums I have ever used. Might have to check it out more often.

Haha, thanks, what are you using the camera for? I still haven't found what to do with mine...
When the problem is found, you have the button "Solution" , click on it so, the next one with the same problem can easily find it.
Cheers!

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.