Cannot get WLED flashed on ESP32-Mini-1

Hello - I was told this wasn’t appropriate for a github issue so I am asking for help here - has anybody tried this particular board? Is an ESP32-Mini-1 different enough from an ESP32 that it would cause issues?

What happened?

Tried to flash WLED to ESP32-DevKitM-1 board, firmware flashes successfully but afterward the board is endlessly rebooting.

To Reproduce Bug

First tested using the https://install.wled.me/ website - flashing completed successfully but the console log view showed the ESP32 endlessly rebooting
Next I tried to use esptool - ran the command esptool write_flash 0x0 .\esp32_bootloader_v4.bin followed by esptool write_flash 0x10000 .\WLED_0.14.0_ESP32.bin and got the same result.
Finally I tried using esptool on a different ESP32-DevKitM-1 board in case it was a hardware issue but I got the same result

Expected Behavior

The ESP32 should boot up and start running the WLED program

Install Method

Binary from WLED . me

What version of WLED?

WLED_0.14.0_ESP32.bin

Which microcontroller/board are you seeing the problem on?

ESP32

Relevant log/trace output

--Flashing Firmware--
esptool write_flash 0x10000 .\WLED_0.14.0_ESP32.bin
esptool.py v4.6
Found 3 serial ports
Serial port COM6
Connecting....
Detecting chip type... Unsupported detection protocol, switching and trying again...
Connecting....
Detecting chip type... ESP32
Chip is ESP32-U4WDH (revision v3.0)
Features: WiFi, BT, Dual Core, 240MHz, Embedded Flash, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: c8:f0:9e:47:e5:98
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Flash will be erased from 0x00010000 to 0x00148fff...
Compressed 1278256 bytes to 848392...
Wrote 1278256 bytes (848392 compressed) at 0x00010000 in 75.4 seconds (effective 135.6 kbit/s)...
Hash of data verified.

--Console output after flashing--

Rebooting...
ets Jul 29 2019 12:21:46

rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 188777542, 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:0x3fff0018,len:4
load:0x3fff001c,len:1044
load:0x40078000,len:10124
load:0x40080400,len:5828
entry 0x400806a8
Guru Meditation Error: Core  1 panic'ed (LoadProhibited). Exception was unhandled.
Core 1 register dump:
PC      : 0x40145a60  PS      : 0x00060730  A0      : 0x80143c96  A1      : 0x3ffb1d70
A2      : 0x3ff440c0  A3      : 0x00000000  A4      : 0x00060b20  A5      : 0x00000001
A6      : 0x00060b20  A7      : 0x00000000  A8      : 0x00000000  A9      : 0x3ffb1d50
A10     : 0x00000000  A11     : 0x00060b23  A12     : 0x00060b20  A13     : 0x3ffb1efc
A14     : 0x000000ff  A15     : 0x00000000  SAR     : 0x00000010  EXCCAUSE: 0x0000001c
EXCVADDR: 0x0000001c  LBEG    : 0x4000c46c  LEND    : 0x4000c477  LCOUNT  : 0x00000000

ELF file SHA256: 0000000000000000

Backtrace: 0x40145a5d:0x3ffb1d70 0x40143c93:0x3ffb1d90 0x4014401a:0x3ffb1db0 0x400eea3b:0x3ffb1de0
0x400ef026:0x3ffb1e30 0x400f0d26:0x3ffb1e70 0x400f0e62:0x3ffb1e90 0x400f0f01:0x3ffb1ec0
0x400ebe22:0x3ffb1ee0 0x401123c1:0x3ffb1f20 0x40112616:0x3ffb1f40 0x401136ca:0x3ffb1f90
0x401316da:0x3ffb1fb0 0x4008b5d2:0x3ffb1fd0

Anything else?

Board info

Have you tried an older firmware?

I should have tried that before posting - I flashed 0.13.3 and it seems to work just fine - it creates the AP and I can log in. Thanks for the help!