espressif / esp32-camera

Apache License 2.0
1.85k stars 632 forks source link

Camera init failed with error 0x105 #572

Closed Akifuuu closed 9 months ago

Akifuuu commented 11 months ago

// Helpp, i cant configure whats wrong , for my fyp.

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) 15:53:35.932 -> configsip: 0, SPIWP:0xee 15:53:35.932 -> clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 15:53:35.932 -> mode:DIO, clock div:1 15:53:35.932 -> load:0x3fff0030,len:1344 15:53:35.932 -> load:0x40078000,len:13964 15:53:35.932 -> load:0x40080400,len:3600 15:53:35.932 -> entry 0x400805f0 15:53:36.401 -> E (494) esp_core_dump_f⸮6⸮⸮ No core dump partition found! 15:53:36.401 -> E (494) esp_core_dump_flash: No core dump partition found! 15:53:36.453 -> E (332) psram: PSRAM ID read error: 0xffffffff 15:53:36.453 -> 15:53:36.493 -> E (396) camera: Camera probe failed with error 0x105(ESP_ERR_NOT_FOUND)

WangYuxin-esp commented 11 months ago

May I know which development board and camera sensor you are using?

Strat00s commented 11 months ago

I now have the same problem. It worked the first time I flashed it but flashing it for a second time gives me just 0x105. I have ESP32-CAM from aithinker.

WangYuxin-esp commented 11 months ago

The prompt 0x105 means that the detection signal sent by ESP32 to the sensor through I2C has not received a response. There are many reasons why the sensor failed to reply to the ACK signal, such as issues with its power on sequence, register not reset, and unstable clock signal provided by ESP32.

Alepha0 commented 11 months ago

I had the same errors, I solved two of them but I found a bigger one. For the "E (494) esp_core_dump_flash: No core dump partition found!" I searched in the files created by the code for one called "partitions.cvs" and added the last line (the one that says "coredump"). The values of size and offset should be modified according to the size of your memory ( in my case 4 M)

Name, Type, SubType, Offset, Size, Flags

nvs, data, nvs, 0x9000, 0x5000, otadata, data, ota, 0xe000, 0x2000, app0, app, ota_0, 0x10000, 0x140000, app1, app, ota_1, 0x150000,0x140000, spiffs, data, spiffs, 0x290000,0x160000, coredump, data, coredump,0x3F0000,0x10000,

the problem I found is that my board has something with the PSRAM (probably it doesn't have one or doesn´t work properly ). I changed the device for one that says: WROOM (no PSRAM) instead of Wrover (has PSRAM) in the settings of the board and the error stopped appearing, but I still have the 0x105. I tried to use other camera configurations with no PSRAM, change the I2C speed frequency, and change the power supply to 5v but still doesn't work, some other tip?

WangYuxin-esp commented 11 months ago

This issue should actually be investigated from two aspects, one is ESP32, and the other is the camera sensor. You can use an oscilloscope to check whether ESP32 has indeed sent an I2C signal and whether the sensor has responded to ACK.

WangYuxin-esp commented 11 months ago

Yes, you can definitely do this, and you can add your configuration in the components/esp32-camera directory.

github-actions[bot] commented 9 months ago

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