Boot fails when build v2.0-20180319 is burned into WROOM-02

[grhhm]

Boot fails when build v2.0-20180319 is burned into WROOM-02

Code: Select all

INIT : Booting version: v2.0-20180319
INIT : Warm boot #7
FS   : Mounting...
FS   : Mount successful, used 75802 bytes of 957314

Soft WDT reset

ctx: cont
sp: 3fff4a10 end: 3fff4ce0 offset: 01b0

>>>stack>>>
3fff4bc0:  40253c43 00000128 3fff0cd0 4021a2a7
3fff4bd0:  3fff6aa4 40201b0c 3fff4c30 3fff0d20
3fff4be0:  00000001 00000000 3fff363c 40233d43
3fff4bf0:  3fff4e88 00000025 00000025 4020f13c
3fff4c00:  3fff363c 3fff28ac 3fff4c30 4020f5a8
3fff4c10:  3fff6aa4 40201b0c 00000001 4020b0c0
3fff4c20:  3fff363c 3fff28ac 00000001 40234032
3fff4c30:  00000000 00000000 0000207e 40217ae7
3fff4c40:  3fff28cc 0000000c 00000000 40217b00
3fff4c50:  3ffe87a7 0000000c 3fff23fc 3fff3cb4
3fff4c60:  00000001 0000000c 00000000 40236d93
3fff4c70:  3fff5fac 0000000f 00000000 4021aa1f
3fff4c80:  3fff0f48 0000000c 00000001 40236e0f
3fff4c90:  3fff0f48 0000000c 3fff23fc 4023ec3a
3fff4ca0:  00000000 00000000 00000000 3fff61ac
3fff4cb0:  0000002f 00000015 feefeffe feefeffe
3fff4cc0:  3fffdad0 00000000 3fff3cae 4020c188
3fff4cd0:  feefeffe feefeffe 3fff3cc0 4020f6a4
<<<stack<<<

 ets Jan  8 2013,rst cause:2, boot mode:(3,6)

load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
v09826c6d

Might this be useful?

[TD-er]

There are some issues with the WiFi.
The last build without the major changes to WiFi, I made, is 20180316.
The last version 20180322, should also work, since I extended the wifi connect timeouts.
But some still report issues.

Just a quick question, do you use DHCP, or a fixed IP-address?

Build 20180319 will not work on a new device, without stored settings.

[grhhm]

Just a quick question, do you use DHCP, or a fixed IP-address?

DHCP. I recall painful experience of static addresses

BTW, is it possible somehow in Github to mark really unusable builds?
I think many people burning tons of neurons and time trying to ignite broken builds. So marking builds can be useful for all.

[TD-er]

That's something we should do I guess.

For now, I'm just asking people to test the current PR, before running into unusable versions again...

So could you test this PR: https://github.com/letscontrolit/ESPEasy/pull/1165

It's an entirely different approach of connection management and in theory simpler.

[papperone]

WROOM-02 has 2Mb flash and I'm not sure we have a 2Mb bin in the nightly build...
when I was testing a module with this chip I had to compile myself with the right flash size, else it won't work!

[TD-er]

And 1M flash versions? Then you cannot OTA, but at least you can try them.

[papperone]

And 1M flash versions? Then you cannot OTA, but at least you can try them.

can't test them as I don't have them anymore, I installed in a friend setup with selfcompiled ESPEasy with 2Mb Flash settings... happily running so far for him