Esp camera init camera probe failed with error 0x20004 - Исправление ошибок и поиск оптимальных решений проблем

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

Comments

E][camera.c:1049] camera_probe(): Detected camera not supported.
[E][camera.c:1249] esp_camera_init(): Camera probe failed with error 0x20004

sure… but what camera address did it find? what is the board you are using, the example… just by those two lines you can not be helped

Hi,
I get the same error. Board is an ESP32 -Cam with AI Thinker ESP32-S chip. The camera on board says it is an ov-2640 v2.0, or TY-OV2640-V2.0 to be exact. Below is the spit out from Serial Monitor.

Have ESP32 1.0.4 installed, and using the ESP32 WRover Module Board.
Have #define CAMERA_MODEL_AI_THINKER , uncommented.
Using Arduino 1.8.10. Trying to run the CameraWebServer example.

I also get the «Brownout detector was triggered» error a couple of times before the below info, but I know how to turn that off if needed.

rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0018,len:4
load:0x3fff001c,len:1216
ho 0 tail 12 room 4
load:0x40078000,len:9720
ho 0 tail 12 room 4
load:0x40080400,len:6352
entry 0x400806b8

[E][camera.c:1049] camera_probe(): Detected camera not supported.
[E][camera.c:1249] esp_camera_init(): Camera probe failed with error 0x20004

Hi,

Thought I would follow up. I have changed so many things, that I can’t say for certain what fixed it. The last thing I changed was the usb cable, as I am powering up an arduino UNO instead of an ftdi adapter to program the esp-cam board. Once I changed the cable, and made sure it was getting enough power, it seems to of have resolved itself. I still got SCCB errors etc for a while, but that all seemed to have fixed itself after reloading up the CameraWebServer sketch. Cheers.

@projectgus @kedars @mahavirj @bkeevil @igrr

Same error

[E][camera.c:1049] camera_probe(): Detected camera not supported.
[E][camera.c:1249] esp_camera_init(): Camera probe failed with error 0x20004

Camera label:

HW-297
OV2640

In program:

#define CAMERA_MODEL_AI_THINKER

Board selection:

ESP32 Wrover Module

esse erro pode ocorrer pela alimentação inapropriada tente a alimentação de 5V em vez de 3.3V

The camera error is probably the wrong camera setting in the sketch. The brownout will be happening when the ESP starts WiFi. Most usb leads and ports struggle with the 200ma+ peak load when it connects. Place a Serial.print («before wifi») then say a 1000ms delay in the code just before wifi.begin. Then another after. I bet it hangs before the second print.

Power the board from a 5v PSU and disconnect the vcc from the FTDI programmer if you like.

I got the same error.
But power off and on ESP32-CAM, the error is no longer there.
hummm….

I solved this problem using the USB port of the PC without hub.
For performance use a PowerBank

Hi i came across this error with the same board . the cause was in the sketch i was using
#define CAMERA_MODEL_WROVER_KIT was enabled by default i had to add // like this
//#define CAMERA_MODEL_WROVER_KIT to disable it

rfox12, zakkie, svrlopatrik, dmack3, Eashan4, black-jk, Manoj-Madushantha, larkingabout, Python-insta, hotkeymuc, and steveseguin reacted with thumbs up emoji

yes, thank you! I had same problem.

Power the board from a 5v PSU and disconnect the vcc from the FTDI programmer if you like.

How do I get the localhost address from COM if I power it separately?

Hi,, I have same problem with ESP32-S CAM
My error like this ;

Brownout detector was triggered

ets Jun 8 2016 00:22:57

[E][camera.c:1049] camera_probe(): Detected camera not supported.
[E][camera.c:1249] esp_camera_init(): Camera probe failed with error 0x20004

Please help me to solved this problem..

Hy, I had same problem but now it is work. Try this:
On board select: ESP32 Wrover Module
and
in program select: #define CAMERA_MODEL_AI_THINKER
I changed also: Partition Scheme: Huge APP (3MB no OTA/1MB SPIFFS).
Good luck.

hey there iam having problem —
[E][camera.c:1049] camera_probe(): Detected camera not supported.
[E][camera.c:1249] esp_camera_init(): Camera probe failed with error 0x20004

Hy, I had same problem but now it is work. Try this:
On board select: ESP32 Wrover Module
and
in program select: #define CAMERA_MODEL_AI_THINKER
I changed also: Partition Scheme: Huge APP (3MB no OTA/1MB SPIFFS).
Good luck.

Already use this, but got the same problem like before

thanks for your suggestion but i have uploaded code from this specification
and it is not working and sorry for late response i have solved thisproblem

…

On Tue, 7 Jul 2020 at 00:48, Bamzz027 ***@***.***> wrote:
Hy, I had same problem but now it is work. Try this:
On board select: ESP32 Wrover Module
and
in program select: #define CAMERA_MODEL_AI_THINKER
I changed also: Partition Scheme: Huge APP (3MB no OTA/1MB SPIFFS).
Good luck.

Already use this, but got the same problem like before

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#102 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQFYPGUAIXGDWJFP4GW6DPDR2IPR3ANCNFSM4J2IPY7A>
.

@Bamzz027

Brownout detector was triggered

You have power supply issues. Use a seperate 5v supply, do not try to power the board from the serial adapter.

I powered the ESP32CAM from a wallwart, and the FTDI via USB, connecting the two only by Rx/Tx. That seems to work fine, except possibly for the gibberish that comes out on the serial monitor after it starts working. Camera data I presume, in which case no problem.

I have the same problem here. But in my case, I am sure that my software setup worked before. Cable is OK, power supply is OK as well.

I am starting to suspect a broken hardware. If I add support for software PWM LED, I can succeed sometimes, but only if PWM is set to 84% off, 16% on. It sounds very strange. I measured all camera power voltages, and everything seems to be OK.

To confirm hardware issue, I am waiting for a new module.

I had the same errors
solution for me:
On board select: ESP32 Wrover Module
and
in program select: #define CAMERA_MODEL_AI_THINKER
I changed also: Partition Scheme: Huge APP (3MB no OTA/1MB SPIFFS).

AND I HAVE TO USE AN OLDER BOARD DRIVER (1.0.2) — only this worked

after flash:
if it was connected on the FTDI via USB — it worked only a couple of seconds (but the ip address was visible)- then — with an own powersupply — it is working

I had same issues as noted above, tried everything, nothing worked, then I tried a new fdti adaptor and worked 1st time, pretty sure it was a voltage issue

I had same issues as noted above, tried everything, nothing worked, then I tried a new fdti adaptor and worked 1st time, pretty sure it was a voltage issue

I will try a different power source. But I measured voltage and even voltace fluctuation (with 1 ms resolution), and everything was OK. (And the board worked with the same convertor few weeks ago.)

Yes, there is some type of voltage problem, as the camera makes a snapshot in the moment of turning LED on, and I am even able to make camera temporarily working with the big LED in a PWM mode somewere between 16 to 20% on.

My ESP32-CAM is not made by AI Thinker. It is a clone with a module with the Espressif logo.

after check all found that is power issue, check and/or replace the usb serial adapter, this base on computer that you use and the USB power supply, many case two usb nearby into a pc cannot supply approriate power for camera.

ina addtinal you can amend code for fix ip adress too.

thanks to all of your suggestions but I solved this problem earlier and
sorry for the late response

…

Same issue (VSYNC failures) figured using this call in setup() was causing the issue:
randomSeed(analogRead(0));

// randomSeed(analogRead(0)); fixed that

I will try a different power source. But I measured voltage and even voltace fluctuation (with 1 ms resolution), and everything was OK. (And the board worked with the same convertor few weeks ago.)

Yes, there is some type of voltage problem, as the camera makes a snapshot in the moment of turning LED on, and I am even able to make camera temporarily working with the big LED in a PWM mode somewere between 16 to 20% on.

My ESP32-CAM is not made by AI Thinker. It is a clone with a module with the Espressif logo.

In my case nothing helped except board replacement. The new board with the old camera works.

ok…. i used this esp32 cam a long time ago. it worked then with a 5 v power supply. now, with my laptop, it is not working. try connecting it to a 5 v power supply.

I will try a different power source. But I measured voltage and even voltace fluctuation (with 1 ms resolution), and everything was OK. (And the board worked with the same convertor few weeks ago.)
Yes, there is some type of voltage problem, as the camera makes a snapshot in the moment of turning LED on, and I am even able to make camera temporarily working with the big LED in a PWM mode somewere between 16 to 20% on.
My ESP32-CAM is not made by AI Thinker. It is a clone with a module with the Espressif logo.

In my case nothing helped except board replacement. The new board with the old camera works.

well… then you have a worng code in your old one.

In my case nothing helped except board replacement. The new board with the old camera works.

well… then you have a worng code in your old one.

Both boards have exactly the same code uploaded.

In my case nothing helped except board replacement. The new board with the old camera works.

well… then you have a worng code in your old one.

Both boards have exactly the same code uploaded.

well………………… i meant bootloader. try uploading a new bootloader.

I solved it by supplying MLX90640 ground via TFT backlight and switching backlight on after camera init.

I had similar problems. The WIFI «brownout» issues and permanent rebooting I solved by connecting an external
3.3v supply to the ESP32 (lower left in picture above). Still connecting simultaneously with the IDE via USB8 on the laptop..

The code i used is a bastradization of «https://www.electronics-lab.com/project/video-streaming-server-esp32-cam/»
to which i added some SSD1306 display features to do debugging while not connected to the USD serial console.

The issue with error 0x20004 was solved by defining the correct I/O. I modified the «defines» as follows:

#if defined(CAMERA_MODEL_WROVER_KIT)
#define PWDN_GPIO_NUM 26
#define RESET_GPIO_NUM -1
#define XCLK_GPIO_NUM 32
#define SIOD_GPIO_NUM 13
#define SIOC_GPIO_NUM 12

#define Y9_GPIO_NUM 39
#define Y8_GPIO_NUM 36
#define Y7_GPIO_NUM 23
#define Y6_GPIO_NUM 18
#define Y5_GPIO_NUM 15
#define Y4_GPIO_NUM 4
#define Y3_GPIO_NUM 14
#define Y2_GPIO_NUM 5
#define VSYNC_GPIO_NUM 27
#define HREF_GPIO_NUM 25
#define PCLK_GPIO_NUM 19

that matches the «datasheet» from the manufacturer:

wrover

I had the same problem being reported on a ESP32-CAM board as well. Eventually, I noticed that the error went away when I applied pressure to a specific part of the board during initialisation. Upon closer inspection, I was able to identify several pins of the FPC connector on the ESP32 board that were not soldered correctly from the factory. Once I had fixed the problem by reflowing the connector with a heat gun, the camera came to life.

[E][camera.c:1049] camera_probe(): Detected camera not supported.
[E][camera.c:1249] esp_camera_init(): Camera probe failed with error 0x20004

This error goes away when I switch to 5V from 3.3V power supply

@ManeaFlorin ahhh! Thank you for that hint, I get this error sometimes but as I was adapting the code I thought I had broken something software wise. I didn’t think to check if it might be a hardware issue…

@ManeaFlorin if you scroll up the error. it state
«Brownout detector was triggered»

meaning under voltage

Is there a way to confirm whether this is a hardware issue? I suspect my camera or its connectors are faulty.

Hy, I had same problem but now it is work. Try this:
On board select: ESP32 Wrover Module
and
in program select: #define CAMERA_MODEL_AI_THINKER
I changed also: Partition Scheme: Huge APP (3MB no OTA/1MB SPIFFS).
Good luck.

This works.

Hi to all,
I have had the same error, but solved quickly adding delay(1000); before WiFi.begin(ssid, password);

E][camera.c:1049] camera_probe(): Detected camera not supported.
[E][camera.c:1249] esp_camera_init(): Camera probe failed with error 0x20004

A little of history.
The way to work with ESP32-CAM before was like this:

You had to choose as board the «ESP32 Wrover Module«.
Choose as camera model «#define CAMERA_MODEL_WROVER_KIT«.

If you update your Arduino IDE Software to the latest version (1.8.15 in my case), and also add the latest Additional Boards Manager with https://dl.espressif.com/dl/package_esp32_index.json
Install the esp32 board manager to the latest version (1.0.6 in my case).

Now you will find as board the «ESP32 Arduino > AI Thinker ESP32-CAM«.
Run the sample code in «File > Examples > ESP32 > Camera > CameraWebServer«.
Then, in the code for selecting the camera should look like this:
// Select camera model
//#define CAMERA_MODEL_WROVER_KIT // Has PSRAM
//#define CAMERA_MODEL_ESP_EYE // Has PSRAM
//#define CAMERA_MODEL_M5STACK_PSRAM // Has PSRAM
//#define CAMERA_MODEL_M5STACK_V2_PSRAM // M5Camera version B Has PSRAM
//#define CAMERA_MODEL_M5STACK_WIDE // Has PSRAM
//#define CAMERA_MODEL_M5STACK_ESP32CAM // No PSRAM
#define CAMERA_MODEL_AI_THINKER // Has PSRAM
//#define CAMERA_MODEL_TTGO_T_JOURNAL // No PSRAM

After this you shouldn’t have problems.

First, I would like to thank everyone for your comments.

My ESP32-cam work one day. Left running overnight — nothing touched. The next morning only the error 0x20004.

I’ve tried all Your ways, but none of them worked.
I checked all electronic paths, whether there were breaks in the contacts and soldering — everything was OK.

I started checking the electronic components and found a damaged C12 capacitor for RESET CAM — it made a short circuit. Link: https://randomnerdtutorials.com/esp32-cam-ai-thinker-pinout/
I desoldered it and everything works fine. If nothing helps, check the electronic connections and electronic components.

Greetings from Poland: Jacek.

I will try a different power source. But I measured voltage and even voltace fluctuation (with 1 ms resolution), and everything was OK. (And the board worked with the same convertor few weeks ago.)
Yes, there is some type of voltage problem, as the camera makes a snapshot in the moment of turning LED on, and I am even able to make camera temporarily working with the big LED in a PWM mode somewere between 16 to 20% on.
My ESP32-CAM is not made by AI Thinker. It is a clone with a module with the Espressif logo.

In my case nothing helped except board replacement. The new board with the old camera works.

where did you get the new board?

these cameras are not worth the headaches they give you, the quality control must be terrible some work some fail. I found the TTGO version was the easiest, it even has the small oled and tells you the IP number the regular ESP32 cam deserves a Viking Funeral in a burn barrel. LOL

esse erro pode ocorrer pela alimentação inapropriada tente a alimentação de 5V em vez de 3.3V

Muito obrigado!
It is correct, you can solve it by connecting to 5 V
Es correcto, lo puede solucionear conectando a 5 V.
Thank you!!

Board: ESP32-CAM
Label cam: LA AF2569 0927XB
#define CAMERA_MODEL_AI_THINKER

Had the same problem: [E][camera.c:1379] esp_camera_init(): Camera probe failed with error 0x20004
Turned out the ESP32 module was not properly soldered, 4 pads was not connected. Re-soldered these and now it’s working fine.

For what it’s worth, I’m seeing this issue (Camera probe failed with error 0x20004) on the «ESP32 TTGO T-Camera with PIR Sensor and OLED Display Board » when I erroneously defined a reset pin on the ESPHome ssd130c_i2c component as GPIO23 🤦‍♂️🤦‍♂️

I share this only in hopes that someone may find it and waste far less time than myself 🤣

I had the same errors solution for me: On board select: ESP32 Wrover Module and in program select: #define CAMERA_MODEL_AI_THINKER I changed also: Partition Scheme: Huge APP (3MB no OTA/1MB SPIFFS).

AND I HAVE TO USE AN OLDER BOARD DRIVER (1.0.2) — only this worked

after flash: if it was connected on the FTDI via USB — it worked only a couple of seconds (but the ip address was visible)- then — with an own powersupply — it is working

For me this was the working workaround. I am currently using 1.0.6.

For me this was the working workaround. I am currently using 1.0.6.

please try 2.0.2

Hi i came across this error with the same board . the cause was in the sketch i was using #define CAMERA_MODEL_WROVER_KIT was enabled by default i had to add // like this //#define CAMERA_MODEL_WROVER_KIT to disable it

FacePalm time here too thankfully google and other folk ‘less complicated’ like myself came to the rescue in 5 mins.. Thanks for posting…

Sojourneer

try changing the baud rate to a higher one,.,if the serial is on 9600, move it to 115200.,

This issue has nothing to do with any settings, rather it’s a non-deterministic problem due to bad design of the esp32-cam module itself (the mcu and/or the camera are not getting enough power). All mentioned «fixes» above are just momentary strokes of luck that don’t really amount to a cause-effect (except indirectly, since various setttings changes can affect how the module draws power.

The problem is composed of two compounded parts. The detection failure of the camera, as well as the brownout. Both being sporadic. The only useful workarounds to ensure reliable startup, is to first disable wifi (which draws huge power on start), wait a bit, then initialize the camera, then wait a bit more, then start the wifi, possibly first setting its power level to low, then later increasing it after it is initialized. One can also disable the brownout if one is sure that the power supply can’t/won’t drop too low or if you just don’t care about its possible consequences (as a «true» brownout is usually rare compared to the frequency of failed start-ups).

Update: I changed my startup code so that it deinits the camera whenever a detection failure occurs, and then reinit it again, in a loop, until success. This however doesn’t work alone without also deinit the gpio isr handler. But even then, the esp still keeps failing on recognition, until a power cycle. This means that simply calling deinit/init isn’t enough to fully reset the state of the mcu and/or camera thus attempt to detect again. This means there is no silver bullet solution unless you design your own board, or someone provides insight as to whether deinit truly returns each gpio line state to the original, and which specifically are relevant, so these can be manually toggled. Only then is it possible to truly re-attempt camera detection from the beginning, such that it would complete successfully after a non-deterministic number of retries, with the guarantee that it would succeed in any case where a full reset would have. I personally have not delved deep enough to figure this out myself, it’s not a priority right now.

Hola tengo un error similar pero a mi me aprece asi el error.
[E][camera.c:222] skip_frame(): Timeout waiting for VSYNC
[E][camera.c:1406] esp_camera_init(): Camera init failed with error 0x20003
camera init state -1
Porfavor que alguien me ayude soy nuevo con ESP32

El «brownout» es un problema del power supply, a veces no es sufficente utilizar solo el puerto USB del ordenador. Trata de usar un USB HUB con fuente independiente.
El problema del VSYNC puede ser un problema del modulo cpu del ESP mismo pero a veces simplemtel el tipo the board que seleccionas y los parametros que usas ara ese board:Trata a ver «Wrover, 40mhz, QIO, Huge APP » prueba diferentes opciones, bajala la frequencia a la CPU

Hi i came across this error with the same board . the cause was in the sketch i was using #define CAMERA_MODEL_WROVER_KIT was enabled by default i had to add // like this //#define CAMERA_MODEL_WROVER_KIT to disable it

this work for me

I had the same errors… The solution is simply to take the camera out and put it back in, wiping off the dust

Источник

Содержание

ESP32 CAM — Detected camera not supported #118
Comments
ESP32 camera.c:1249] esp_camera_init(): Camera probe failed with error 0x20004

ESP32 CAM — Detected camera not supported #118

I always get the same errors:
[E][camera.c:1049] camera_probe(): Detected camera not supported.
[E][camera.c:1249] esp_camera_init(): Camera probe failed with error 0x20004

I´ve also tried this: #74 , but even this wasn´t helpful.

Can you help me with this?

The text was updated successfully, but these errors were encountered:

Hello lhadvab ,
1.Please Change your connecting USB Cable. may be it has some voltage problem so your USB Cable not working properly .
2.Change your connecting port. Use laptop port .

Please try this.

I´ve skipped this important step:

Go to Tools > Board and select AI-Thinker ESP32-CAM.
Before that, I had selected Wrover module.

This was very important thing because I have AI-Thinker module.
But I have some problem:
[E][camera.c:1049] camera_probe(): Detected camera not supported.
[E][camera.c:1249] esp_camera_init(): Camera probe failed with error 0x20004

I also tried different USB cable, but with no result.

#define CAM_PIN_PWDN 32 #define CAM_PIN_RESET -1

reset is -1 not 32
32 is pwdn this is alway LOW

#define CAM_PIN_PWDN 32 #define CAM_PIN_RESET -1

reset is -1 not 32
32 is pwdn this is alway LOW

@liuandong Is it in the camera_pins.h file ?

@liuandong I´ve tried it, but I still have same problem. I´ve also tried 5V instead of 3,3V. Any of these are not working. I´am not using original blue arduino usb cable, maybe this is reason why it isn´t working.

Please try this. I solved the problem. 😁 😁
#66 (comment)

My problem same as you «Detected camera not support». Many way I’ve try still can get it working untill today 😁 . I do some google and find out at the website maybe esp pin not solder properly and some say camera pins code not same as on board. So it is true about the camera pin and i make a test. first find esp32 cam circuit diagram, take your multimeter, check camera pin to esp32 pin, check the camera_pins.h, and make the correction on gpio num.. Goodluck buddy 👍

Yes these little esp32-cam boards are ..delicate 🙂
There is always the chance to have hardware issues.
Mine had bad i2c SDA signal being clamped to 1.2V. so it could not probe the camera.

in general, a connected serial cable will cause wifi issues and slooow network transmissions.
(probably because the radio signal gets weekened by the cable)
Also a connected program-enable-cable will decrease the cam clock signal.(IO0)
The high power LED will cause power surges which causes unexpected malfunction.

The OV2640 to be probed,

needs an input clock signal XCLK
needs a powercycle (PWDN pin controls the 2 voltage regulators).
Then it needs some init being written to function (ie.VSYNC clocks visible)

Use USB to TTL convertor instead od ftdi. It works for me

I had this issue and after taking power from external power supply instead of the ftdi programmer, the issue got fixed

@lhadvab I had the same issue, but it was a pin configuration problem. Here is my code and configuration. I hope it helps.

using esp-idf, not arduino.
Remember to clone this repository on a folder called «components» in your project folder.

ESP32-CAM
Programmer: FTDI232
- in 3.3V config
- Only using GND, VCC, TX and RX

Component config > driver configurations > RTCI0 configuration > «Support array ‘rtc_gpio_desc’
Component config > Esp32-Specific > Support for external, SPI supported RAM

CODE
This code initializes the camera, takes a picture, and saves it on «fb» variable. Then it restarts. It does not do anything with the picture. Is just for testing purpose.

Gehe auf die camara Pins und kopiere die #elif defined(CAMERA_MODEL_AI_THINKER) in die #if defined(CAMERA_MODEL_WROVER_KIT) dann klappt es

Ich bekomme immer die
gleichen Fehler: [E][camera.c:1049] camera_probe(): Erkannte Kamera wird nicht unterstützt.
[E][camera.c:1249] esp_camera_init(): Kamerasonde mit Fehler 0x20004 fehlgeschlagen

Ich habe auch versucht: #74 , aber auch das war nicht hilfreich.

Können Sie mir dabei helfen?
Gehe in der Arduino IDE bei den Programm CameraWebserver auf die camera Pins und kopiere die #elif definiert(CAMERA_MODEL_AI_THINKER) Pins in die #if definiert(CAMERA_MODEL_WROVER_KIT) dann klappt es

I’ve worked this out for you know, uh. rx,tx This scalp was used for usb to ttl and powered by usb 5v succeeded.Thank you.

i bougth ESP32-CAM
On the other hand, it bought a power supply realy bad
said to deliver 2A with 6V
When used with ESP32-CAM i measure the VCC to 3.5V
So i change the power supply and problem 2004 disappears

Conclusion : check power supply. (

In my case i burn up the ground pin or area with reverse connection during pin connection time. Just upload the code and use another ground pin for ground terminal of power supply.
Solution is always beneath the problem.

I’m facing the same problem with my ESP32-CAM, here are the details:

Board: ESP32-CAM (ESP32S)
Camera module: TY-OV2640-V2.0
USB adapter: ESP32-CAM-MB

I’m using CameraWebServer example with AI_THINKER model defined:

Some comments suggested to change the USB cable, but the problem persists.

Here are my usual steps:

Reset the cam cable.
check power voltage
Try different cam

It does happen that the cam is DOA. In my case

I’m facing the same problem with my ESP32-CAM, here are the details:

Board: ESP32-CAM (ESP32S)
Camera module: TY-OV2640-V2.0
USB adapter: ESP32-CAM-MB

I’m using CameraWebServer example with AI_THINKER model defined:

Some comments suggested to change the USB cable, but the problem persists.

Hi, I just bought the same shield from Wish and found the same issue. After many hours thinking on software side I took the last chance that it maybe was a hardware problem. and that’s it. I just pushed down with my fingers the connector clip in order to keep down as much as possible the cable flat electric pins onto the related socket electric pins. Then I plug the uUSB connector to the Extended board to supply the module and magically the Serial Monitor of my Arduino IDE shows me the booting process and the CAM recognition and furthermore the DHCP address assigned by my router! So, in the end it’s because of the very bad connector and pins. very cheap material, like a toy! I must now think how to fix it in a proper way so the electric contacts can be blocked and have a good electric connection

Источник

ESP32 camera.c:1249] esp_camera_init(): Camera probe failed with error 0x20004

Dear Mr. Rui and Sara Santos
Please help,
I buy your book ESP32 Cam, I download your source code Modul 1 CameraWebServer. after input SSID then complie and download success, after reset at output serial come out error “ESP32 camera.c:1249] esp_camera_init(): Camera probe failed with error 0x20004”
Please help what is the problem my trial?
Thank you

Sometimes, resetting the ESP32-CAM several times solves the problem.

What is the ESP32-CAM model you’re using? If you’re using a different board, you need to change the pin assignment.

Additionally, it might be one of the following issues:

- Not enough power through USB source
  If you’re powering your ESP32 through a USB port on your computer, it might not be supplying enough power.
- Faulty FTDI programmer
  Some readers also reported this problem was solved by replacing their actual FTDI programmer with this one.
- The camera/connector is broken
  If you get this error, it might also mean that your camera or the camera ribbon is broken. If that is the case, you may get a new OV2640 camera probe.

Additionally, if you have the ESP32-CAM connected to your computer using an FTDI programmer, make sure you’re powering the board using the 5V pin.

I hope this helps.

I’m having this same problem here. The things were going well with my two ESP32-CAM modules, but now when I upload the code and open it on the Serial Monitor of Arduino IDE, I get this error messge.

I tryed the solutions above, but none of then changed the situation.
I Believe that is something relted to the configurations because I disn’t change anything in the code.

Hi Eduardo.
What code are you trying to run in your ESP32-CAM?
Can you share it?
To share your code use a link to github, pastebin, etc…
Regards,
Sara

Hi There,
Tonight I saw this same issue with a TTGO-Camera board. It is loaded with the code to send an email after PIR detects motion. (Module 3 Unit 2 in Cam course) The camera pin defines I used are right off the package the TTGO came in, and I updated the on board PIR to pin 33, OR SO I THOUGHT! In fact, I had neglected to update the pin # and it was set to the incorrect (for TTGO board) GPIO 13. After correcting and uploading, all seems good.
It is amazing that this handles gmail so well! And, gmail just adds subsequent picture attachments to the same conversation thread. So far it has been running flawlessly for about 20 minutes, and has sent 6 pictures when triggered.
Very useful project, and now that I have defined the pins properly, no more errors. Apparently the output of the PIR interferes with the camera initialization during wake up. Because even with the incorrect pin defined, the camera would send one picture after hard reset and go to sleep normally. The error appeared during wake up.
Thanks for a great project. Now to see how long my battery will last, then deploy it!
Cheers!
Dave K.

I’m glad you found the issue.
Not setting the pins properly for your board will result in “camera not detected” errors.
We have an article about the TTGO-Camera you are using with the pins definition and other information that might be useful: https://makeradvisor.com/esp32-ttgo-t-camera-pir-sensor-oled/

We also have another article with pin definitions for other boards: https://randomnerdtutorials.com/esp32-cam-camera-pin-gpios/

I was thrilled the problem was so simple!
I posted it so everyone would go back and check their pin defines if they see this error in the serial monitor.
In my case, the PIR was interfering with #define SIOD_GPIO_NUM 13, causing the error. I assume other mis-defined pins would create the same error.
Keep up the great work!
Dave K.

That’s great, thank you.
I’ll mark this issue as resolved. If you need further help, you just need to open a new question in our forum.
Regards,
Sara

Hi guys,
The code that I used is absolutely the same that used to work here in the past. And it’s not working im my two “AI Thinker ESP32-CAM” modules. I’m taking a look on David’s solution, looking for something weird in my code.

The code I used is this one below:

/******************************************
** Constants and global scope variables **
******************************************/
// define the number of bytes you want to access
#define EEPROM_SIZE 1

// Pin numbers in CAMERA_MODEL_AI_THINKER
#define PWDN_GPIO_NUM 32
#define RESET_GPIO_NUM -1
#define XCLK_GPIO_NUM 0
#define SIOD_GPIO_NUM 26
#define SIOC_GPIO_NUM 27

#define Y9_GPIO_NUM 35
#define Y8_GPIO_NUM 34
#define Y7_GPIO_NUM 39
#define Y6_GPIO_NUM 36
#define Y5_GPIO_NUM 21
#define Y4_GPIO_NUM 19
#define Y3_GPIO_NUM 18
#define Y2_GPIO_NUM 5
#define VSYNC_GPIO_NUM 25
#define HREF_GPIO_NUM 23
#define PCLK_GPIO_NUM 22

// Other constants
#define INTERVAL 15000 // Time interval (in milliseconds) between each picture

// Global scope variables
camera_config_t config; //Stores the camera configuration parameters
unsigned int pictureNumber = 0; //Picture number

/**************************
** Function prototypes **
**************************/
void config_and_initialize_camera( void );
void init_microSD_card( void );
void take_picture( void );

/******************
** setup() **
******************/
void setup() <
// Disable the ‘browout detector’
WRITE_PERI_REG(RTC_CNTL_BROWN_OUT_REG, 0);

// Turn off the flash
pinMode(4, INPUT);
digitalWrite(4, LOW);
//rtc_gpio_hold_dis(GPIO_NUM_4);

// Mnitor serial
Serial.begin(115200);
delay(10000);
Serial.println(“Initializing…”);

Serial.print(“Initializing the camera module…”);
config_and_initialize_camera();
Serial.println(“Ok!”);

//–> Inicializar o cartao MicroSD:
Serial.print(“Initializing the MicroSD card module…”);
init_microSD_card();
Serial.println(“”);

// Wait ” milliseconds before taking another picture
delay(INTERVAL);

/**************************
** Auxiliary Functions **
**************************/
// –> ‘config_and_initialize_camera()’ function
void config_and_initialize_camera( void ) <
// –> Configuracoes da camera
//camera_config_t config;
config.ledc_channel = LEDC_CHANNEL_0;
config.ledc_timer = LEDC_TIMER_0;
config.pin_d0 = Y2_GPIO_NUM;
config.pin_d1 = Y3_GPIO_NUM;
config.pin_d2 = Y4_GPIO_NUM;
config.pin_d3 = Y5_GPIO_NUM;
config.pin_d4 = Y6_GPIO_NUM;
config.pin_d5 = Y7_GPIO_NUM;
config.pin_d6 = Y8_GPIO_NUM;
config.pin_d7 = Y9_GPIO_NUM;
config.pin_xclk = XCLK_GPIO_NUM;
config.pin_pclk = PCLK_GPIO_NUM;
config.pin_vsync = VSYNC_GPIO_NUM;
config.pin_href = HREF_GPIO_NUM;
config.pin_sscb_sda = SIOD_GPIO_NUM;
config.pin_sscb_scl = SIOC_GPIO_NUM;
config.pin_pwdn = PWDN_GPIO_NUM;
config.pin_reset = RESET_GPIO_NUM;
config.xclk_freq_hz = 20000000;
config.pixel_format = PIXFORMAT_JPEG;

// –> Frame size:
if( psramFound() ) <
config.frame_size = FRAMESIZE_UXGA; // FRAMESIZE_ + QVGA|CIF|VGA|SVGA|XGA|SXGA|UXGA
config.jpeg_quality = 10;
config.fb_count = 2;
> else <
config.frame_size = FRAMESIZE_SVGA;
config.jpeg_quality = 12;
config.fb_count = 1;
>

// –> Inicialize Camera
esp_err_t err = esp_camera_init(&config);
if (err != ESP_OK) <
Serial.printf(“Camera init failed with error 0x%x”, err);
return;
>
>

// –> ‘init_microSD_card()’ function
void init_microSD_card( void ) <
Serial.println(“Starting SD Card”);
if(!SD_MMC.begin()) <
Serial.println(“SD Card Mount Failed”);
return;
>

uint8_t cardType = SD_MMC.cardType();
if(cardType == CARD_NONE) <
Serial.println(“No SD Card attached”);
return;
>
Serial.println(“Ok!”);
>

// –> ‘take_picture()’ function
void take_picture( void ) <
camera_fb_t * fb = NULL;

// Take Picture with Camera
fb = esp_camera_fb_get();
if(!fb) <
Serial.println(“Camera capture failed”);
return;
>
// initialize EEPROM with predefined size
EEPROM.begin(EEPROM_SIZE);
pictureNumber = EEPROM.read(0) + 1;

// Path where new picture will be saved in SD Card
String path = “/pic_” + String(pictureNumber) +”.jpg”;

fs::FS &fs = SD_MMC;
Serial.printf(“Picture file name: %sn”, path.c_str());

File file = fs.open(path.c_str(), FILE_WRITE);
if(!file) <
Serial.println(“Failed to open file in writing mode”);
>
else <
file.write(fb->buf, fb->len); // payload (image), payload length
Serial.printf(“Saved file to path: %sn”, path.c_str());
EEPROM.write(0, pictureNumber);
EEPROM.commit();
>
file.close();
esp_camera_fb_return(fb);

// Turns off the ESP32-CAM white on-board LED (flash) connected to GPIO 4
digitalWrite(4, LOW);
>

Thanks you very much,
Eduardo Alvim

Hi.
As mentioned previously, it might be a power issue.
Sometimes, you have to press the RST button several times until it finds the camera.
You may also need to disconnect the camera ribbon and connect again.
Regards,
Sara

I tried reconecting the camera and pressing the reset several times here. But nothing different tha the other times. I bought a TTGO ESP Camera here and I hope that I won’t have this issue again…

Thank you very much

Hi.
That’s weird.
Are you sure you didn’t change anything on the pin definition?
Did those cameras worked before?
Regards,
Sara

Yes, They worked very well before. I used it in july and they were working perfect. When I tried to use then again (by end of august or begining of september) they showed this problem here.
Yes, very very weird, but I’m moving it.
Thank you very much!

Hi.
I’m sorry, but besides the suggestions I’ve made before in the other issue, I’m out of ideas on how to solve your problem 🙁

I bought another OV640 camera module and tested in my ESP32-CAM. Yes, now they are working as it should (and used to work)!

The problem is related to the camera model XRZ00D1. I don’t have any ideia why it used to work perfectly and suddenly stoped.
The OV2640 camera module which worked fine I bought here: https://pt.aliexpress.com/item/4000035639017.html?spm=a2g0s.9042311.0.0.f1c3b90a9OTV0o
Well, thank you!

Hi Eduardo.
I’m glad everything is working now.
Thanks for the follow-up.
Regards,
Sara

Not an answer but another question, I used the code from the 4th module on streaming, loaded it up, but always get a camera fail init fail 20004 (surmised its related to the probe). when I started I was using a fisheye lens, changed to the stock lens and it worked, but when I switched back to the fish eye again same fail. When I compared the code to other code found on the website, there seemed to be bits missing about the init. is there different code I need for the fisheye?’

Hi.
I don’t think you need a different code for the fisheye. The cameras are the same in terms of hardware, only the lens is different (at least when I tried a fish eye lens, it was like that). Unless you have a different camera…

What bits of code do you think are missing?

Hello,
I am now waiting for my new cameras to be sure, but it does appear the cameras I have are in fact the wrong ones. I bought them before I got the bundle and was only looking for cameras compatible with the ESP32CAM, turns out I bought the ov5640 cameras. There wasn’t any identifying info on the bags they came in, but there was info on the mini ribbon cable. The code I thought was missing was

Hi.
That piece of code is optional and it changes the settings of the camera.
ov5640 cameras are not compatible with the codes we have, that are for OV2640 cameras.
Regards
Sara

Well, it’s my experience here Jon Ullom: when you face the 0x20004, it means that you camera is gonne. When it happened to me, I tried everything, change the ESP, disconnect and reconnect the camera, test the same camera in onther ESP etc. Nothing worked to me, except try a new OV2640 camera. Unfortunately.
I wish I could tell some better news here.

Источник

Содержание

0x20004 Esp32 cam error #174
Comments
ghost commented Sep 8, 2020
ghost commented Sep 11, 2020
anhangah commented Nov 27, 2020
FrancescoBaroneItaly commented Dec 4, 2020
gin66 commented Dec 8, 2020 •
gin66 commented Dec 8, 2020
Footer
ESP32 CAM — Detected camera not supported #118
Comments
lhadvab commented Feb 6, 2020
YashwantPanwar commented Feb 11, 2020
YashwantPanwar commented Feb 11, 2020 •
lhadvab commented Feb 12, 2020
lhadvab commented Feb 12, 2020
liuandong commented Feb 18, 2020
DoddyD commented Feb 20, 2020
lhadvab commented Feb 29, 2020
while0l1 commented Mar 1, 2020
jojos115 commented Mar 24, 2020
xenpac commented Mar 24, 2020 •
sarang-git commented Jun 10, 2020
rekomerio commented Jun 20, 2020
aamacaya commented Jun 29, 2020
Aikidet commented Jul 4, 2020
Aikidet commented Jul 5, 2020
lksmj commented Aug 12, 2020
kerauzen commented Nov 1, 2020
raijadas commented Nov 24, 2020
gdamoreira commented Apr 29, 2021
Schaggo commented Apr 30, 2021
bauhaus1977 commented May 7, 2021
LEDc configuration error and camera_probe failed #66
Comments
masterd89 commented Aug 27, 2019
mirronelli commented Aug 28, 2019 •
masterd89 commented Aug 29, 2019
jxyxg commented Aug 13, 2020
won0-kim commented Jun 23, 2021
github-actions bot commented Sep 12, 2021
yugandharc9 commented Dec 24, 2021
Morchack commented Jan 4, 2022

0x20004 Esp32 cam error #174

Hello, I’m using a esp32 cam. it suddenly threw this error at me,

can someone help me??

The text was updated successfully, but these errors were encountered:

I’m with same issue. I’ve a esp32cam (I think that it’s a AI TINKER clone) and got the same error code. I noticed too that the camera is very hot when esp is on 🙁

Did you solved this problem?

I’m trying to re-initialize the OV cam of AI-Thinker board after deep sleep wakeup, but I’m not able to initialize with camera probe error. I also tried to invoke an ESP.restart after wake up, but the only way to initialize the camera is an hardware reset ( and I didn’t understand, because hardware reset did not reset camera because camera reset pin is always pulled up ).
Any suggestion? thks!

1., do not let the camera driver power down the module.
2. power on the module before camera init
3. retry several times with power down/on, if init fails
4. entering deep sleep: ensure camera/board/camera module power line pull downs/ups set appropriately

search for init_camera() and case DEEPSLEEP

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

ESP32 CAM — Detected camera not supported #118

I always get the same errors:
[E][camera.c:1049] camera_probe(): Detected camera not supported.
[E][camera.c:1249] esp_camera_init(): Camera probe failed with error 0x20004

I´ve also tried this: #74 , but even this wasn´t helpful.

Can you help me with this?

The text was updated successfully, but these errors were encountered:

Hello lhadvab ,
1.Please Change your connecting USB Cable. may be it has some voltage problem so your USB Cable not working properly .
2.Change your connecting port. Use laptop port .

Please try this.

I´ve skipped this important step:

Go to Tools > Board and select AI-Thinker ESP32-CAM.
Before that, I had selected Wrover module.

I also tried different USB cable, but with no result.

liuandong commented Feb 18, 2020

#define CAM_PIN_PWDN 32 #define CAM_PIN_RESET -1

reset is -1 not 32
32 is pwdn this is alway LOW

#define CAM_PIN_PWDN 32 #define CAM_PIN_RESET -1

reset is -1 not 32
32 is pwdn this is alway LOW

@liuandong Is it in the camera_pins.h file ?

Please try this. I solved the problem. 😁 😁
#66 (comment)

Yes these little esp32-cam boards are ..delicate 🙂
There is always the chance to have hardware issues.
Mine had bad i2c SDA signal being clamped to 1.2V. so it could not probe the camera.

The OV2640 to be probed,

needs an input clock signal XCLK
needs a powercycle (PWDN pin controls the 2 voltage regulators).
Then it needs some init being written to function (ie.VSYNC clocks visible)

Use USB to TTL convertor instead od ftdi. It works for me

I had this issue and after taking power from external power supply instead of the ftdi programmer, the issue got fixed

@lhadvab I had the same issue, but it was a pin configuration problem. Here is my code and configuration. I hope it helps.

using esp-idf, not arduino.
Remember to clone this repository on a folder called «components» in your project folder.

ESP32-CAM
Programmer: FTDI232
- in 3.3V config
- Only using GND, VCC, TX and RX

Component config > driver configurations > RTCI0 configuration > «Support array ‘rtc_gpio_desc’
Component config > Esp32-Specific > Support for external, SPI supported RAM

CODE
This code initializes the camera, takes a picture, and saves it on «fb» variable. Then it restarts. It does not do anything with the picture. Is just for testing purpose.

Gehe auf die camara Pins und kopiere die #elif defined(CAMERA_MODEL_AI_THINKER) in die #if defined(CAMERA_MODEL_WROVER_KIT) dann klappt es

Ich bekomme immer die
gleichen Fehler: [E][camera.c:1049] camera_probe(): Erkannte Kamera wird nicht unterstützt.
[E][camera.c:1249] esp_camera_init(): Kamerasonde mit Fehler 0x20004 fehlgeschlagen

Ich habe auch versucht: #74 , aber auch das war nicht hilfreich.

I’ve worked this out for you know, uh. rx,tx This scalp was used for usb to ttl and powered by usb 5v succeeded.Thank you.

Conclusion : check power supply. (

I’m facing the same problem with my ESP32-CAM, here are the details:

Board: ESP32-CAM (ESP32S)
Camera module: TY-OV2640-V2.0
USB adapter: ESP32-CAM-MB

I’m using CameraWebServer example with AI_THINKER model defined:

Some comments suggested to change the USB cable, but the problem persists.

Here are my usual steps:

Reset the cam cable.
check power voltage
Try different cam

It does happen that the cam is DOA. In my case

I’m facing the same problem with my ESP32-CAM, here are the details:

Board: ESP32-CAM (ESP32S)
Camera module: TY-OV2640-V2.0
USB adapter: ESP32-CAM-MB

I’m using CameraWebServer example with AI_THINKER model defined:

Some comments suggested to change the USB cable, but the problem persists.

Источник

LEDc configuration error and camera_probe failed #66

i have an issue with ESP32-CAM module with OV2640:

E (1582) ledc: requested frequency and duty resolution can not be achieved, try reducing freq_hz or duty_resolution. div_param=3
E (1592) camera_xclk: ledc_timer_config failed, rc=ffffffff
I (1602) sccb: pin_sda 26 pin_scl 27

I’ve tried everything: enable/disable all camera module support and hw I2C from menuconfig, tried with 3 different unit and different cameras. Tried custom firmware and examples firmware, examined the code and the pin configuration, different USB to serial boards, powering the boards with external PSU. and yet i still get that error.
I also updated esp-idf framework by deleting and re cloning the repo. No luck with that also.

Any idea?
Thanks,
D

The text was updated successfully, but these errors were encountered:

there was a change in ledc driver that is used to drive the clock

to work with the current version a one line of code needs to be added into xclk.c
the line is:

put in in the block bellow

you will find the the file in yourproject/components/esp32-camera/driver/xclk.c

use of the APB clock was assumed in previous commit to ledc.c and now it needs to be explicitly set

Thanks @mirronelli, i already figured it out though (while i used LEDC_AUTO_CLK).

Strange thing is, if i ran the ledc initialization snippet (whitout setting the clock source) from the app-main it didn’t give any error at all.

Moreover, while this solution solves the duty cycle — frequency error, in my case it still hangs in «skip_frame()» function, thowing a timeout error. I found out this occurred because the VSYNC pin wasn’t actually clocking, even though it was correctly initialized.

I solved it by moving the pheripheral enable command at the end of the function, after the parameters assignment:

The other issue i found (the one that caused error 0x20004), which is however related to the circuit, is that camera wasn’t responding to i2c commands, thus preventing the software to recognize the correct model.

ESP32-CAM board has camera PWDN pin tied to GND (so camera is always powered) while camera RST is passively deasserted a little time afte 3.3V supply is started. However, GPIO32 controls the power supply enable of the camera by means of a transistor. Thus, if GPIO32 is not set low before calling camera_init(), the camera is powered down and cannot reply to i2c commands of course. This solved the issue:

Hello, sorry to bother you guys, now i am writing a driver code of the ov2640 with esp32cam, but actually i have no idea and donnot know how to start and i have found that there is few material about writing a driver code from scratch, I wondering whether you have some experience or have some useful tutorial material, can you share them with me ? Many thanks ! @masterd89 @mirronelli

// Select camera model
// #define CAMERA_MODEL_WROVER_KIT // Has PSRAM
//#define CAMERA_MODEL_ESP_EYE // Has PSRAM
//#define CAMERA_MODEL_M5STACK_PSRAM // Has PSRAM
//#define CAMERA_MODEL_M5STACK_V2_PSRAM // M5Camera version B Has PSRAM
//#define CAMERA_MODEL_M5STACK_WIDE // Has PSRAM
//#define CAMERA_MODEL_M5STACK_ESP32CAM // No PSRAM
#define CAMERA_MODEL_AI_THINKER // Has PSRAM
//#define CAMERA_MODEL_TTGO_T_JOURNAL // No PSRAM

@jxyxg I think.. this problem could be solved easily by only changing these comments like that.

This issue appears to be stale. Please close it if its no longer valid.

yugandharc9 commented Dec 24, 2021

In my case I had to comment
#define CAMERA_MODEL_WROVER_KIT // Has PSRAM
and uncomment

#define CAMERA_MODEL_AI_THINKER // Has PSRAM

Obrigado @mirronelli , eu já descobri (enquanto usava LEDC_AUTO_CLK).

O estranho é que, se eu executei o snippet de inicialização do ledc (sem definir a fonte do relógio) do app-main, não deu nenhum erro.

Além disso, embora esta solução resolva o erro de ciclo de trabalho — frequência, no meu caso ela ainda trava na função «skip_frame ()», resultando em um erro de tempo limite. Descobri que isso ocorreu porque o pino VSYNC não estava realmente sincronizando, embora tenha sido inicializado corretamente.

Resolvi movendo o comando de habilitação de pheripheral no final da função, após a atribuição dos parâmetros:

O outro problema que encontrei (o que causou o erro 0x20004), porém relacionado ao circuito, é que a câmera não respondia aos comandos do i2c, impedindo que o software reconhecesse o modelo correto.

A placa ESP32-CAM tem o pino PWDN da câmera ligado ao GND (para que a câmera esteja sempre ligada), enquanto a câmera RST é desativada passivamente um pouco depois que o fornecimento de 3,3 V é iniciado. No entanto, o GPIO32 controla a ativação da fonte de alimentação da câmera por meio de um transistor. Portanto, se o GPIO32 não estiver definido como baixo antes de chamar camera_init (), a câmera será desligada e não poderá responder aos comandos i2c, é claro. Isso resolveu o problema:

Источник

Munque: Posts: 25; Joined: Mon Feb 10, 2020 11:38 pm

Problem flashing ESP32Cam — «Detected camera not supported»

Able to flash the device, but can’t get the device started (See serial output below):

Tech specs:
MCU: AI Thinker ESP32Cam (that has worked just fine in the past)
Computer: MacBook Pro using on OS 10.15.4 (latest)
Arduino IDE: v1.8.12 (latest)
SiLabs Driver: v5.3.5 (latest)
ESP32 board package version 1.0.4 (latest)
Tools > Board > «AI Thinker ESP32-Cam»

Serial Monitor Output after flash:

Code: Select all

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0018,len:4
load:0x3fff001c,len:1216
ho 0 tail 12 room 4
load:0x40078000,len:9720
ho 0 tail 12 room 4
load:0x40080400,len:6352
entry 0x400806b8

[E][camera.c:1049] camera_probe(): Detected camera not supported.
[E][camera.c:1249] esp_camera_init(): Camera probe failed with error 0x20004

jwaresolutions: Posts: 1; Joined: Sat May 02, 2020 5:32 am

Re: Problem flashing ESP32Cam — «Detected camera not supported»

Postby jwaresolutions » Sat May 02, 2020 5:40 am

I just had this issue. i got it working

1) choose the «AI Thinker ESP-32 CAM»
2) remove the comment for «#define CAMERA_MODEL_AI_THINKER»
3) make sure all other devined models are commented out <<<< this was my mistake WROVER_KIT was still uncommented. by the camera logic on the camera_pins.h page it didnt matter that i had uncommented out anything else it hit the first if statement and exited selecting the WROVER_KIT every time.

It should look like this and it flashes a lot faster than the WROVER model. for some reason i also had to reboot it twice after it flashed.

// Select camera model
//#define CAMERA_MODEL_WROVER_KIT
//#define CAMERA_MODEL_ESP_EYE
//#define CAMERA_MODEL_M5STACK_PSRAM
//#define CAMERA_MODEL_M5STACK_WIDE
#define CAMERA_MODEL_AI_THINKER

Who is online

Users browsing this forum: Bing [Bot], Google [Bot] and 29 guests

Источник

LEDc configuration error and camera_probe failed #66

Comments

masterd89 commented Aug 27, 2019

i have an issue with ESP32-CAM module with OV2640:

Any idea?
Thanks,
D

The text was updated successfully, but these errors were encountered:

mirronelli commented Aug 28, 2019 •

there was a change in ledc driver that is used to drive the clock

to work with the current version a one line of code needs to be added into xclk.c
the line is:

put in in the block bellow

you will find the the file in yourproject/components/esp32-camera/driver/xclk.c

use of the APB clock was assumed in previous commit to ledc.c and now it needs to be explicitly set

masterd89 commented Aug 29, 2019

Thanks @mirronelli, i already figured it out though (while i used LEDC_AUTO_CLK).

Strange thing is, if i ran the ledc initialization snippet (whitout setting the clock source) from the app-main it didn’t give any error at all.

I solved it by moving the pheripheral enable command at the end of the function, after the parameters assignment:

jxyxg commented Aug 13, 2020

won0-kim commented Jun 23, 2021

@jxyxg I think.. this problem could be solved easily by only changing these comments like that.

github-actions bot commented Sep 12, 2021

This issue appears to be stale. Please close it if its no longer valid.

yugandharc9 commented Dec 24, 2021

In my case I had to comment
#define CAMERA_MODEL_WROVER_KIT // Has PSRAM
and uncomment

#define CAMERA_MODEL_AI_THINKER // Has PSRAM

Morchack commented Jan 4, 2022

Obrigado @mirronelli , eu já descobri (enquanto usava LEDC_AUTO_CLK).

O estranho é que, se eu executei o snippet de inicialização do ledc (sem definir a fonte do relógio) do app-main, não deu nenhum erro.

Resolvi movendo o comando de habilitação de pheripheral no final da função, após a atribuição dos parâmetros:

Источник

ESP32 CAM — Detected camera not supported #118

Comments

lhadvab commented Feb 6, 2020

I always get the same errors:
[E][camera.c:1049] camera_probe(): Detected camera not supported.
[E][camera.c:1249] esp_camera_init(): Camera probe failed with error 0x20004

I´ve also tried this: #74 , but even this wasn´t helpful.

Can you help me with this?

The text was updated successfully, but these errors were encountered:

YashwantPanwar commented Feb 11, 2020

Hello lhadvab ,
1.Please Change your connecting USB Cable. may be it has some voltage problem so your USB Cable not working properly .
2.Change your connecting port. Use laptop port .

YashwantPanwar commented Feb 11, 2020 •

Please try this.

lhadvab commented Feb 12, 2020

I´ve skipped this important step:

Go to Tools > Board and select AI-Thinker ESP32-CAM.
Before that, I had selected Wrover module.

lhadvab commented Feb 12, 2020

I also tried different USB cable, but with no result.

liuandong commented Feb 18, 2020

#define CAM_PIN_PWDN 32 #define CAM_PIN_RESET -1

reset is -1 not 32
32 is pwdn this is alway LOW

DoddyD commented Feb 20, 2020

#define CAM_PIN_PWDN 32 #define CAM_PIN_RESET -1

reset is -1 not 32
32 is pwdn this is alway LOW

@liuandong Is it in the camera_pins.h file ?

lhadvab commented Feb 29, 2020

while0l1 commented Mar 1, 2020

Please try this. I solved the problem. 😁 😁
#66 (comment)

jojos115 commented Mar 24, 2020

xenpac commented Mar 24, 2020 •

Yes these little esp32-cam boards are ..delicate 🙂
There is always the chance to have hardware issues.
Mine had bad i2c SDA signal being clamped to 1.2V. so it could not probe the camera.

The OV2640 to be probed,

needs an input clock signal XCLK
needs a powercycle (PWDN pin controls the 2 voltage regulators).
Then it needs some init being written to function (ie.VSYNC clocks visible)

sarang-git commented Jun 10, 2020

Use USB to TTL convertor instead od ftdi. It works for me

rekomerio commented Jun 20, 2020

I had this issue and after taking power from external power supply instead of the ftdi programmer, the issue got fixed

aamacaya commented Jun 29, 2020

@lhadvab I had the same issue, but it was a pin configuration problem. Here is my code and configuration. I hope it helps.

using esp-idf, not arduino.
Remember to clone this repository on a folder called «components» in your project folder.

ESP32-CAM
Programmer: FTDI232
- in 3.3V config
- Only using GND, VCC, TX and RX

Component config > driver configurations > RTCI0 configuration > «Support array ‘rtc_gpio_desc’
Component config > Esp32-Specific > Support for external, SPI supported RAM

CODE
This code initializes the camera, takes a picture, and saves it on «fb» variable. Then it restarts. It does not do anything with the picture. Is just for testing purpose.

Aikidet commented Jul 4, 2020

Gehe auf die camara Pins und kopiere die #elif defined(CAMERA_MODEL_AI_THINKER) in die #if defined(CAMERA_MODEL_WROVER_KIT) dann klappt es

Aikidet commented Jul 5, 2020

Ich bekomme immer die
gleichen Fehler: [E][camera.c:1049] camera_probe(): Erkannte Kamera wird nicht unterstützt.
[E][camera.c:1249] esp_camera_init(): Kamerasonde mit Fehler 0x20004 fehlgeschlagen

Ich habe auch versucht: #74 , aber auch das war nicht hilfreich.

lksmj commented Aug 12, 2020

I’ve worked this out for you know, uh. rx,tx This scalp was used for usb to ttl and powered by usb 5v succeeded.Thank you.

kerauzen commented Nov 1, 2020

Conclusion : check power supply. (

raijadas commented Nov 24, 2020

gdamoreira commented Apr 29, 2021

I’m facing the same problem with my ESP32-CAM, here are the details:

Board: ESP32-CAM (ESP32S)
Camera module: TY-OV2640-V2.0
USB adapter: ESP32-CAM-MB

I’m using CameraWebServer example with AI_THINKER model defined:

Some comments suggested to change the USB cable, but the problem persists.

Schaggo commented Apr 30, 2021

Here are my usual steps:

Reset the cam cable.
check power voltage
Try different cam

It does happen that the cam is DOA. In my case

bauhaus1977 commented May 7, 2021

I’m facing the same problem with my ESP32-CAM, here are the details:

Board: ESP32-CAM (ESP32S)
Camera module: TY-OV2640-V2.0
USB adapter: ESP32-CAM-MB

I’m using CameraWebServer example with AI_THINKER model defined:

Some comments suggested to change the USB cable, but the problem persists.

Источник