OTA update fails with XMC Flash chip

[Jason2866]

OTA update fails (used gz Tasmota firmware) when a XMC Flash is on the ESP board.
Module Model: ESP-12F Vendor: DOITING
Flash Chip Id 0x164020

To get it working (again) a serial flash is needed

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

load 0x4010f000, len 3656, room 16

tail 8

chksum 0x0c

csum 0x0c

v9c56ed1f

Basic Infos

• This issue complies with the issue POLICY doc.
• I have read the documentation at readthedocs and the issue is not addressed there.
• I have tested that the issue is present in current master branch (aka latest git).
• I have searched the issue tracker for a similar issue.
• If there is a stack dump, I have decoded it.
• I have filled out all fields below.

Platform

• Hardware: [ESP-12F]
• Core Version: [2.7.0]
• Development Env: [Platformio]
• Operating System: [Windows|Ubuntu]

Settings in IDE

• Module: [Generic ESP8266]
• Flash Mode: [DOUT]
• Flash Size: [4MB]
• lwip Variant: [LWIP2_HIGHER_BANDWIDTH_LOW_FLASH]
• Reset Method: [nodemcu]
• Flash Frequency: [40Mhz]
• CPU Frequency: [80Mhz]
• Upload Using: [OTA]
• Upload Speed: [115200] (serial upload only)

Problem Description

Flashing via serial does work and device works as expected.
Trying a OTA update results in this

Debug Messages

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

load 0x00000000, len 201326592, room 16

[Jason2866]

Did some test #6725 causes the issue. Using a eboot.elf version before this commit solves the problem

[d-a-v]

Thanks @Jason2866 for the bissect !
@ChocolateFrogsNuts Does it ring a bell ?

[crashcoq]

Same problem for me on OTA only

Start OK
`

21:38:58.882 -> ets Jan 8 2013,rst cause:2, boot mode:(3,6)
21:38:58.882 ->
21:38:58.882 -> load 0x4010f000, len 3656, room 16
21:38:58.882 -> tail 8
21:38:58.882 -> chksum 0x0c
21:38:58.882 -> csum 0x0c
21:38:58.882 -> v9c56ed1f
21:38:58.882 -> ~ld

Don't start after update

21:33:21.235 -> ets Jan 8 2013,rst cause:2, boot mode:(3,6)
21:33:21.235 ->
21:33:21.235 -> load 0x4010f000, len 3656, room 16
21:33:21.235 -> tail 8
21:33:21.235 -> chksum 0x0c
21:33:21.235 -> csum 0x0c
21:33:21.235 -> v9c56ed1f
21:33:21.235 -> @cp:0
21:33:25.407 -> ld
21:33:25.407 -> e:
21:33:25.407 -> ets Jan 8 2013,rst cause:3, boot mode:(3,6)
21:33:25.407 ->
21:33:25.407 -> ets_main.c nl ���o{⸮⸮⸮g���⸮��s⸮⸮o�⸮�⸮�쒌⸮⸮��⸮⸮�d⸮⸮o⸮�2
`

I can upgrade firmware with serial COM only on 2.7.0

On version 2.6.3, all is ok, serial and OTA

[ChocolateFrogsNuts]

Hmm, ok, testing of OTA updates was shall we say "severely limited".
Easiest way to verify if it's the XMC bootloader code is to comment out the #define XMC_SUPPORT at line 193 of eboot.c and see what that does.

There are two factors at play here -
The implementation of spi_flash_get_id() on eboot may not work (ie I'm pretty sure its dodgy), thus not detecting the XMC chip... this should only be a factor if power is cycled when an update is not complete, or if you do an OTA upgrade from a version of the core that has no XMC support at all, because the XMC chip won't be set to full output drive.
Failing to detect the XMC chip should make no difference to how it operated on the previous version, so I think it's something else happening.

OR it is working and the code that tries to slow down the access is messing up.

Either way, trying a build with XMC support disabled in the bootloader will give some insight.

[devyte]

To whoever will test, the previous means:

• modify eboot.c as explained
• rebuild eboot.elf
• rebuild your test sketch

[Jason2866]

Using a eboot.elf before the XMC PR works for my module with XMC flash (OTA with gzip and uncompressed too).
I just replaced the eboot.elf file. So IMHO for a Hotfix the PR should reverted
For building Tasmota we are using just this change. arendst/Tasmota#8342

@ChocolateFrogsNuts The OTA fails only if the XMC eboot.elf is used.
This is not the case

if you do an OTA upgrade from a version of the core that has no XMC support at all, because the XMC chip won't be set to full output drive.

I am not using Linux. So i cant use the provided Makefile to build eboot.elf...
If you provide a modified version i will test.

[Tech-TX]

All of my D1 Mini boards have XMC flash chips, if you need another test bunny. I'm not on Linux, either. 😄

I know I can OTA to the IP address directly, haven't been able to OTA via the GUI for some time; Bonjour Browser doesn't see it, nor does Service Browser on the Android phone.

I'm pretty sure I updated to 2.7.0 dev on Saturday.

edit: yep, I'm even with master, and it dies quietly after the OTA completes when going from the command line direct to the IP address with espota.py. It uploads, but the code doesn't run after the reset.