ESP-32s - broken ? troubleshooting

Development Tools IDE 1.x
1

Hello,
i bought ESP-32s CAM with ESP32-CAM-MB and both items seems broken to me.

  1. ESP32-CAM-MB pluged in and i have: usb device descriptor failed. (checked on 2 pc and few cables) and also this seller already have one comment saying esp32cam-MB isnt recognized... so i guess this part is broken. But at least it gives 5V (confirmed by multimeter), so i could use it as a power supply board.

  2. But now ESP-32s CAM board. Fortunatelly i have in home FTDI, so i plugged in and i was able even to program that board but after that only reboot loop...

i choosed board: AI Thinker ESP32-CAM, cpu freq:240, flash freq:80, flash mode:QIO, partition scheme: (tested: huge, regular, minimal).

code:

void setup() {
  // put your setup code here, to run once:
  Serial.begin(115200);
 
}

void loop() {
  // put your main code here, to run repeatedly:
  Serial.println("Hello World!");
  delay(2000);
}

upload process:

Sketch uses 262537 bytes (8%) of program storage space. Maximum is 3145728 bytes.
Global variables use 16520 bytes (5%) of dynamic memory, leaving 311160 bytes for local variables. Maximum is 327680 bytes.
esptool.py v4.2.1
Serial port COM3
Connecting.....
Chip is ESP32-D0WD-V3 (revision 3)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: c0:49:ef:f1:b1:e8
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
Configuring flash size...
Flash will be erased from 0x00001000 to 0x00005fff...
Flash will be erased from 0x00008000 to 0x00008fff...
Flash will be erased from 0x0000e000 to 0x0000ffff...
Flash will be erased from 0x00010000 to 0x00050fff...
Compressed 18912 bytes to 13025...
Writing at 0x00001000... (100 %)
Wrote 18912 bytes (13025 compressed) at 0x00001000 in 0.6 seconds (effective 270.6 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 128...
Writing at 0x00008000... (100 %)
Wrote 3072 bytes (128 compressed) at 0x00008000 in 0.1 seconds (effective 394.5 kbit/s)...
Hash of data verified.
Compressed 8192 bytes to 47...
Writing at 0x0000e000... (100 %)
Wrote 8192 bytes (47 compressed) at 0x0000e000 in 0.1 seconds (effective 594.7 kbit/s)...
Hash of data verified.
Compressed 262928 bytes to 143301...
Writing at 0x00010000... (11 %)
Writing at 0x0001ce69... (22 %)
Writing at 0x00024e26... (33 %)
Writing at 0x0002a2b0... (44 %)
Writing at 0x0002f604... (55 %)
Writing at 0x00037e90... (66 %)
Writing at 0x00040e23... (77 %)
Writing at 0x00046854... (88 %)
Writing at 0x0004bf20... (100 %)
Wrote 262928 bytes (143301 compressed) at 0x00010000 in 3.5 seconds (effective 603.6 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...

and serial monitor output:

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:0x3fff0030,len:1344
load:0x40078000,len:13864
load:0x40080400,len:3608
entry 0x400805f0

assert failed: do_core_init startup.c:298 (flash_ret == ESP_OK)

Backtrace:0x40083521:0x3ffe3aa00x40089171:0x3ffe3ac0 0x4008dec5:0x3ffe3ae0 0x400d94f2:0x3ffe3c10 0x40082c3d:0x3ffe3c40 0x400792ca:0x3ffe3c90 |<-CORRUPTED

ELF file SHA256: 0000000000000000

Rebooting...
2

on other forum some one suggested that many USB->UART modules have a LDO power regulator which is insufficient for an ESP32, so i tested it with direct usb power supply, but same result.

3

Help with understanding a backtrace - ESP32 Forum

4

That is unlikely.

It is more likely that you failed to carefully observe all the rules: strict 3.3V logic levels, power supply capable of delivering at least 500 mA, etc.

For informed advice, post the details of your setup, and a clear, focused picture of it.

5

When a blank sketch is loaded and all the connections have been removed, except power and serial, does the ESP32 still act up?

One possibility is that one of the don't use pins is being used. gpio_num 6, 7, 8, 11, 10, and 9. Also gpio num 13 and 12 can be problematic under certain circumstances.

Post an image of your project, all wired up.

6

I'm connection only 5V and GND next to it and UOT,UOR and closing or opening GPIO0 that's all.
Dont worry about my cable connection. If i would messed up i would not be capable to upload anything to ESP32, right ??

I already wrote that after uploading blank sketch i can read from serial monitor that ESP32 is up and it is in reboot loop. Once again example of serial output:

ets Jul 29 2019 12:21:46

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:0x3fff0030,len:1344
load:0x40078000,len:13864
load:0x40080400,len:3608
entry 0x400805f0

assert failed: do_core_init startup.c:298 (flash_ret == ESP_OK)

Backtrace:0x400839f1:0x3ffe3aa00x40090dc1:0x3ffe3ac0 0x4009681d:0x3ffe3ae0 0x400dfa2a:0x3ffe3c10 0x400830f2:0x3ffe3c40 0x400792ca:0x3ffe3c90 |<-CORRUPTED

ELF file SHA256: 0000000000000000

Rebooting...

I also wanted to expirement a little and checked what will happen if i will deliver 3.3V instead of 5V to pin 5V and i got this:

ets Jul 29 2019 12:21:46
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:0x3fff0030,len:1344
load:0x40078000,len:13864
load:0x40080400,len:3608
entry 0x400805f0

Brownout detector was triggered

which means: Brownout detection is a hardware feature that shuts down the processor if the system voltage is below a threshold - so at least i see that there is some response if i mess up.

Btw is there a similar protection if i give 5V to 3.3V pin?
I can not test it unfortunatelly because if i plug in 3.3V there is no response from ESP32. I can not upload sketch or read serial monitor.

IMG_20221227_002551_382
IMG_20221227_002551_3821920×1424 258 KB

7

Just to finish this topic i bought another set esp32 + flashing board and now i was able to get stream from my new esp32 in 5min. So maybe highly unlikly but definitelly both boards were broken right away. I found out one interesting thing, that flashing board (the one which doesnt work have blank chip instead of CH340C sign ,so i think that manufacturer used cheap replacements ? Also esp32 chip solders dont look as good as on working board (just first sight toughts).

Now one question about new working board. Is it normal that i can hear low sizzling sound when streaming ?

8

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