ESP-32s - broken ? troubleshooting

[tomipol]

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

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.

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:

Code: Select all

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:

Code: Select all

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

continuation of code (forum is only allowing 13 lines of code ?)

Code: Select all

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)...

continue

Code: Select all

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 %)

continue...

Code: Select all

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:

Code: Select all

Rebooting...
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)

continue...

Code: Select all

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

ELF file SHA256: 0000000000000000

Rebooting...

[lbernstone]

Sounds like a power issue. Many USB->UART modules have a LDO power regulator which is insufficient for an ESP32. Try powering from a different source.

[tomipol]

You mean it's enough power to programm ESP, but not enought to run it ?
Anyways, i used now as a power source this ESP32-CAM-MB which is not recognized by windows, but gives 5V nicely.
I was even able to use both buttons (reset and IOO). So i read ESP32 by ftdi again (while ESP was powered by ESP32-CAM-MB) and again same looking boot loop. I also put ESP into download mode by presing IOO button and uploaded code again (with ftdi). This time empty code

Code: Select all

void setup() {
  // put your setup code here, to run once:
}
void loop() {
  // put your main code here, to run repeatedly:
}

and again checked monitor showing same boot loop.
Lastly i powered ESP directly from USB port (directly), connected only 5V and GND. And ftdi connected as monitor - same loop.

[tomipol]

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 ?