Closed ndfred closed 1 year ago
Tried with --flash_size 16MB
and that doesn't solve it, and tried with the latest ebus-v3_lolin32_factory.bin
(size 948960 bytes), no luck with that either.
It seems obvious in retrospect, but I didn't realise you needed the eBUS Adapter to deal with 24V, and the board only accommodates the D1 mini format directly. So if I don't want a mess of wires, that board would work best.
you can also use a D1 mini 32. anyway, the flash size needs to match of course
I have been flashing the
ebus-v3_lolin32_factory.bin
D32 firmware onto my D32 Pro, which has 16MB of flash instead of 4MB (ESP32-WROVER
rather thanESP32-WROOM-32
), and am running into a boot loop:I know the D32 Pro is not officially supported, but I am wondering if there is a way to make it work given both boards are so similar. I tried flashing
tasmota32.factory.bin
and that works no problem. I thought I would rebuild the image for my own board, but the source code is not available.If I flash
tasmota32.factory.bin
(which supports both D32 and D32 Pro boards among many others) with the exact same procedure, then I get a normal boot:Here is the flashing procedure I have used on macOS (
screen
command commented, that is what I use to identify the boot loop):I have also looked at
flash.sh
that I modified to reuseesptool.py
in the venv set up above, and that gives me a flash error mismatch (16MB rather than 4MB). Since the size is larger I reckon it shouldn't be a problem, so I just commented that test and got this command line, which I flashed my board with, again without success (boot loop):ebus-v3_lolin32_factory.bin
is 946112 bytes which matches the file on the repo. Any suggestions on how to make this work? Thanks!