Mega Release 20231225 for ESP32 S2

[Oetsch]

Hi

based on hints I checked by myself the newest ESPEasy Release for my often used ESP32 S2 Mini and used the Webflasher with the Version "Normal 4M Little FS".

And also for me this Release does not work on this hardware. I was not able to connect to the access point because the connection was always dropped.

Might this be a result of the ESP ID 5.1 and the Wifi changes?

Then tested the 20231130 Release (ESP_Easy_mega_20231130_normal_ESP32s2_4M316k_CDC.factory.bin) and everthing works fine again.

Is there anything known?

Thx

P.S.: Similar issues with the newest Tasmota (13.3.0) release. So there must be sth. special for the S2 for the updated versions.

[Ath]

Have you also tried the non-LittleFS build, similar to the one you tried from the 20231130 release? (That still uses the IDF 4.4 release)

AFAIK, Tasmota has switched to IDF 5.1 in their latest releases, so it can't be excluded that this is caused by IDF 5.1, but it can also be a 'feature' of the S2 boards you have tested... WiFi stability is rather dependent on the quality of the 3.3V voltage regulator on board, and if that's of dubious capacity/quality then the potential changes in WiFi initialization may not be handled properly by that regulator, causing the WiFi to be dropped.

[TD-er]

We're using the platform_package based on the ESP-IDF5.1 + cherry picked commits from the Arduino repo.
I've been in close contact with Jason2866 from Tasmota who makes these for the last few months, so we made this possible in close coorporation.

About the WiFi issues, do you have one of those purple Wemos-like boards?
Those are very tricky regarding WiFi.

[Oetsch]

@Ath
Just checked because of issues with ESPEasy also tried with nearly the same result.

With tasmota I can join the web page of the access point point but the connection to my network is not accepted/stable and is disconnected and back to access-point-point within some seconds.

Wit ESPEasy I cannot join the accesspoint Wifi at all.

No, not tried the non Little-FS but will do. Because of this change in version/naming structure in ESPEasy the topic is new for me and have to understand first. But currently the webflasher says "ESP32-S2" and this seems not to be so different to my hardware

@TD-er
Yes, I´m using the purple Wemos copies.

[TD-er]

The web flasher detection is quite accurate.
I have not seen any incorrect detection on all (ESPEasy) supported hardware.

[Oetsch]

Hi

as suggested, tested the non LittleFS via manual selection (not automatic via web flasher) and this version works.

Used: ESP_Easy_mega_20231225_normal_ESP32s2_4M316k_CDC.factory.bin
For this device https://www.wemos.cc/en/latest/s2/s2_mini.html or better to say a chinese copy version which always worked fine before with ESPeasy (incl. auto detection by web flasher).

double checked with Little FS version (ESP_Easy_mega_20231225_normal_ESP32s2_4M316k_LittleFS_CDC.factory.bin) and yes this still has a problem with wifi/network. According message the IP-adress assignment to client from access point does not work and is canceled after some time.

According info from other users, they only had IPv6 adresses assigned from their Router/access point to this ESP32 S2 device with this FW version.

Would be great if you can consider for next releases a fix that make this hw devices still usable with ESPeasy.

Thx!

P.S.: If you need a test run, please inform but be careful due to my newbie and non programming skills

[Ath]

According info from other users, they only had IPv6 adresses assigned from their Router/access point to this ESP32 S2 device with this FW version.

Hm, IPv6 support should only be enabled in the ESP32 Custom LittleFS builds.
Some IPv6 issues have been resolved in this recently merged PR, available from this Actions run (You may need a (free) Github account and logged in to be able to download).
If you could please test that?

I installed the latest code on a very similar purple S2 mini board (Chinese clone), and it ran just fine, with a rapid WiFi connection.

[Oetsch]

Thx!

Tried ESP_Easy_mega_20240103_normal_ESP32s2_4M316k_LittleFS_CDC.factory.bin and result is same.

Try to connect to Access point of ESP from my Smartphone and all I see is IP adress assignment is started but after some seconds unseccesful determinated.

Tried connection from my desktop pc with same result but less information what has happened.

[Ath]

Try to connect to Access point of ESP from my Smartphone and all I see is IP adress assignment is started but after some seconds unseccesful determinated.

Tried connection from my desktop pc with same result but less information what has happened.

Hm, are you talking about the ESPEasy access point that is started on a clean ESPEasy install, when no WiFi is configured yet for the unit, or the regular web UI you can reach via WiFi once the unit is connected to the WiFi?

As the AP is not started if the WiFi connection is successful, after an upgrade (either via OTA or when using serial or web-flash without a wipe/erase of the unit).
When the flash is wiped then the AP should indeed start.

[TD-er]

I will dig up one of those purple S2 boards and do some tests here.
I did test with some S2 boards, but not recently with those purple ones.

[Oetsch]

Hm, are you talking about the ESPEasy access point that is started on a clean ESPEasy install, when no WiFi is configured yet for the unit, or the regular web UI you can reach via WiFi once the unit is connected to the WiFi?

Talking about clean ESPeasy installation without any pre-configuration of e.g. network credentials or sth. like this. Just the next step after flashing the file from github.

When the flash is wiped then the AP should indeed start.

Erased the memory before flashing and the AP seems ok, but no connection is possible. As indicator I only see the IP-adress asignment without success.



@TD-er THX!

[Ath]

@Oetsch

Q: Besides your mobile phone, are you using Windows, Mac or Linux as your Computer operating system? And what webbrowser(s) to connect to ESPEasy?

[Oetsch]

@Oetsch

Q: Besides your mobile phone, are you using Windows, Mac or Linux as your Computer operating system? And what webbrowser(s) to connect to ESPEasy?

PC is Windows 10 22H2 and Firefox or Chrome as browser. For Flashing used Chrome and https://esp.huhn.me/ to flash manual selected bin files (beside stable mega release and auto selected where I used https://td-er.nl/ESPEasy/).

[Ath]

... For Flashing used Chrome and https://esp.huhn.me/ to flash manual selected bin files...

That's a really useful link, thanks!

[TD-er]

Which binary do you use when using this other flash tool?
The factory bin at address 0 I assume?

The reason I'm asking is that this factory file also includes the bootloader and it erases the NVS and OTA partitions.

[Oetsch]

Which binary do you use when using this other flash tool?
The factory bin at address 0 I assume?

Yes the factory bin, please see also:

[TD-er]

Just another question as my purple ESP32-S2 board works just fine on an IDF5.1 based build using LittleFS ( )

How is your board powered? Via USB or external power?
Do you have a log console open on the USB port?
(thinking about a buffer not being read, thus ESPEasy might be pushing log messages but hits a timeout....)

[Oetsch]

Thanks for testing.

Mine is powered by USB Port and I opened console window. By the end I tried several times connecting to the AP which was terminated and no new outputs on the console:

Code: Select all

01.226 : (159476) Info   : Using PSRAM

01.229 : (159316) Info   : 



INIT : Booting version: ESP_Easy_mega_20240103_normal_ESP32s2_4M316k_LittleFS_CDC, (GitHub Actions) mega_69184ff (ESP32 SDK 5.1.2.231216)

01.232 : (159172) Info   : INIT : Free RAM:159172

01.233 : (159092) Info   : INIT : Cold Boot - Restart Reason: CPU0: Vbat power on reset

01.235 : (158980) Info   : FS   : Mounting...

01.242 : (157000) Info   : FS   : Mount successful, used 151552 bytes of 323584

01.261 : (156784) Info   : CRC  : Settings CRC           ...OK

01.277 : (156128) Info   : ESPEasy console using ESPEasySerial

01.300 : (156128) Info   : ESPEasy console fallback enabled

01.310 : (156076) Info   : CRC  : SecuritySettings CRC   ...OK 

01.323 : (156092) Info   : INIT : SPI not enabled

01.324 : (156092) Info   : Set Network mode: WiFi

01.427 : (156092) Info   : WIFI : Set WiFi to STA

01.578 : (128380) Info   : WiFi : Start network scan all channels

04.580 : (126564) Info   : WiFi : Scan finished, found: 21

04.718 : (127160) Info   : WiFi : Start network scan all channels

07.796 : (125652) Info   : WiFi : Scan finished, found: 18

07.815 : (127184) Info   : Setup: Scan all channels

07.845 : (127172) Info   : ESPEasy console using ESPEasySerial

07.883 : (127152) Info   : ESPEasy console fallback enabled

07.898 : (127168) Info   : INIT : Free RAM:127168

07.928 : (127152) Info   : ESPEasy console using ESPEasySerial

07.967 : (127152) Info   : ESPEasy console fallback enabled

07.982 : (127104) Info   : INFO : Plugins: 48 [Normal] (ESP32 SDK 5.1.2.231216)

08.006 : (127268) Error  : WIFI : No valid wifi settings

08.023 : (127256) Info   : WiFi : WiFiConnected(), start AP

08.140 : (127268) Info   : WIFI : Set WiFi to AP+STA

08.264 : (125428) Error  : WIFI : [AP] softAPConfig failed!

08.287 : (125304) Info   : WIFI : AP Mode enabled. SSID: ESPEasy- IP: 192.168.4.1 ch: 1

08.311 : (125224) Info   : WIFI : Arduino wifi status: WL_DISCONNECTED 6 ESPeasy internal wifi status: DISCONNECTED

08.340 : (121128) Info   : Webserver: start

[TD-er]

And you did try to set the WiFi credentials either via the setup page on your phone, or via the serial console?

Code: Select all

wifissid,MyWiFiNetworkName
wifikey,MySecretWiFiPassword
save

And then a reboot to make sure....

[Oetsch]

And you did try to set the WiFi credentials either via the setup page on your phone, or via the serial console?

Code: Select all

wifissid,MyWiFiNetworkName
wifikey,MySecretWiFiPassword
save

And then a reboot to make sure....

None, tried via the setup page but no connection possible so so far to dot. Wether by smarthone nor via desktop pc.

Via serial console is new to me.
Tried according your guideline and this works stable!

Thanks!

[TD-er]

OK, so it is merely a problem using the WiFi AP mode of the ESP board and running the setup there.

This could be a power problem as the AP mode does draw the maximum amount of power and I think there have been some changes in IDF code related to this which may cause an even higher power consumption.

I will hook up an USB power meter to perform some tests to see how much difference this makes.
And I can reduce the TX power during setup to lower power consumption as you're likely close to the ESP during setup.

[TD-er]

I am now testing to connect to it via my phone.
However it seems like I don't get an IP.
Was that what you also experienced?

[Oetsch]

I am now testing to connect to it via my phone.
However it seems like I don't get an IP.
Was that what you also experienced?

yes, this was the issue also here:

[TD-er]

working on it
Not 100% sure yet where the bug is, it might even be in Arduino or IDF code, but I will find it!

[Oetsch]

Thx for taking Care!

Only as remark to Support. As mentioned also Tasmota 13.3.0 does not Work. I could Access the Access Point Setup Page but after entering my credentials it gets quickly kicked Out of my Network. Maybe it's the same reason and you mentioned before both are based one idf 5.1 now which is new in both Releases. Don't know, just as Info and hope this helps.

[TD-er]

It seems to be a change in LWIP, which requires different use of the code which wasn't changed in Arduino.
Made an issue for it: https://github.com/espressif/arduino-es ... 1879364014

[TD-er]

OK, I have a fix ready.
Either this fix will be implemented in Arduino code, or Jason2866 will implement it in a new platform_package for me.

Problem is that we're using a slightly newer version of the ESP-IDF code compared to what the ESP32/Arduino folks are using.
So it is not yet their problem, but it will soon be.
This makes it a bit unclear whether they will already fix it or that we must patch it ourselves until it is fixed in that repo.

[TD-er]

Can you do a check based on the build here:
https://td-er.nl/ESPEasy/latest/
Or the GH Actions builds: https://github.com/letscontrolit/ESPEas ... 7433945595
It should have been fixed on the ESP32 "LittleFS" builds.

[Oetsch]

THANK YOU VERY MUCH!
This version works for me. Was a little bit confused because never tried a Neopixel version before and so the SSID is also Neopixel not "Easy-
". But after I´ve found it the connection worked and also connection to my network seems to be very stable.

Thanks!

[TD-er]

There is also the "Normal" build in the selector
"NeoPixel" is just the first when sorting alfabetically ("Custom" has its own subsection)

[Oetsch]

oh.... normal version also works fine