Boot Loop with ESP-WROOM-32

Issues
1

Hey!

I’m trying to install WLED (from binaries) to some ESP-Wroom-32 (aliexpress…), but they end up in a boot loop. Flashing looks good:

"> esptool.py write_flash -z 0x1000 ./WLED_0.14.3_ESP32.bin
esptool.py v4.7.0
Found 2 serial ports
Serial port /dev/ttyUSB1
Connecting…
Detecting chip type… Unsupported detection protocol, switching and trying again…
Connecting…
Detecting chip type… ESP32
Chip is ESP32-D0WD-V3 (revision v3.1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
Mac, etc
"

The board however ends up in a boot loop:
" rst:0x10 (RTCWDT_RTC_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:DOUT, clock div:2
load:0x3f400020,len:264984
ets Jul 29 2019 12:21:46"

During debuggin, I found this page an especially this
" If your ESP32 board has the GPIO6, GPIO7, GPIO8, GPIO9, GPIO10, and GPIO11 pins, you must not use them because they are connected to the flash memory of the ESP32"

In a minimal program, I could send the esp in the bootloop if I only configure one of those pins as output (pinmode(6, OUTPUT).

Is there any chance that WLED configures one of those pins as output during startup?

I’m a bit running out of ideas, anything else I could test?

2

did you try this to install? https://wled-install.github.io/

3

No, none of my boards (just also tested with an ESP8266 with a working WLED installation) is recognized as a device in Ubuntu/Chromium.

Which binary should I test and why would this give a different result than the esptool?

4

I think you should flash it at 0x10000 not 0x1000, i made that mistake just a few days ago.
Erase flash, flash bootloader again and flash wled at 0x10000

1 Like
5

You are right… It really was just a typo. Thanks!