Closed tmshlvck closed 2 years ago
i used
esptool --chip esp32 -p /dev/ttyUSB0 -b 921600 write_flash 0x00000 ebus-v3_lolin32_factory.bin
(base address for flash 0x0000) which worked for a esp32_devkit_c with wroom-32D chip (maybe a clone, but the pin-layout is as in the documentation)
I wanted to try the bin image out
using
esptool --chip esp32 -p /dev/ttyUSB0 -b 921600 write_flash 0x0 ebus-v3_lolin32_factory.bin
writes to esp32 with following log
`esptool.py v2.8
Serial port /dev/ttyUSB0
Connecting....
Chip is ESP32D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: xx:xx:xx:xx:xx:xx
Changing baud rate to 921600
Changed.
Enabling default SPI flash mode...
Configuring flash size...
Auto-detected Flash size: 4MB
Erasing flash...
Took 0.88s to erase flash block
Wrote 135168 bytes at 0x00000000 in 2.5 seconds (431.5 kbit/s)...
Hash of data verified.
Leaving... Hard resetting via RTS pin...`
gives me following error in the serial console
rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) flash read err, 1000 ets_main.c 371 ets Jun 8 2016 00:22:57
What I am wondering, is why the latest image is 131kB and the mentioned above is almost 850kB
maybe you want to have a look at the flash.sh script the binary isn't just 131kB, so you must have picked the wrong one or downloaded garbage
The README lacks flashing instructions for ESP32. I tried this to flash the Lolin32 binary to ESP32-DevKitC board:
After reset I am getting reboot loop:
I am using this version of esptool: