Incompatibility with ESP32 Core 2.0 and Ethernet (Max token generation retry reached)

[Frtrillo]

So since I updated to arduino core 2.0 ethernet firebase stopped working.
Also I had to modify the events for it to start working (looks like Eth library was updated and changed event names?), don't know if it may be the cause of the issue.

I mean these events:
void WiFiEvent(WiFiEvent_t event)
{
//Do not run any function here to prevent stack overflow or nested interrupt
switch (event)
{
case SYSTEM_EVENT_ETH_START:

I had to change case SYSTEM_EVENT_ETH_START: to ARDUINO_EVENT_ETH_START.... etc and the rest of events.
(Like on this example: https://github.com/espressif/arduino-esp32/blob/mem-optimized/libraries/WiFi/examples/ETH_LAN8720/ETH_LAN8720.ino)

Serial log:
11:42:34.000 -> Firebase Client v2.5.5
11:42:34.000 ->
11:42:35.537 -> ETH Started
11:42:35.537 -> ETH Connected
11:42:35.537 -> ETH MAC: 94:B9:7E:D4:CA:8F, IPv4: 192.168.3.130, FULL_DUPLEX, 100Mbps
11:42:35.537 -> Token info: type = id token, status = error
11:42:35.537 -> Token error: code: -32, message: max token generation retry reached

[mobizt]

Thanks for reporting this.

The breaking changes in ESP32 core WiFi class.

The ethernet examples updated already.

[mobizt]

There are some incompatibilities and missing in the core macro definitions in ethernet phy driver between v2.0.0 and the later versions included alpha and rc which you should not use them because they're not final release.

in v2.0.1-rc1, WiFiClientSecure class added the argument for http2 protocol which is not compatible for all overridden functions that works in the past. This is not good design to add up argument to the virtual functions instead of providing the function to set these arguments separately.

The ESP-IDF framework v 4.4 has changed a lot from v3.3.5 and many things are break the compatibilities.

This Firebase library called ETH.linkup() to check the ethernet connection status which always return false instead of true in v2.0.x and that's why the internet connection is not recognized.

[Frtrillo]

There are some incompatibilities and missing in the core macro definitions in ethernet phy driver between v2.0.0 and the later versions included alpha and rc which you should not use them because they're not final release.

in v2.0.1-rc1, WiFiClientSecure class added the argument for http2 protocol which is not compatible for all overridden functions that works in the past. This is not good design to add up argument to the virtual functions instead of providing the function to set these arguments separately.

The ESP-IDF framework v 4.4 has changed a lot from v3.3.5 and many things are break the compatibilities.

This Firebase library called ETH.linkup() to check the ethernet connection status which always return false instead of true in v2.0.x and that's why the internet connection is not recognized.

So if I edit the library (for me as workaround) and remove ETH.linkup() to return true, the library should work for 2.0.X? I want to use it because 2.0.X somehow fixed/improved my modbus as it failed about 50% of requests and now barely 10% withouth touching anything

[mobizt]

The library was updated which this issue fixed, please update.

[Frtrillo]

The library was updated which this issue fixed, please update.

Hello thanks for the quick update, Ive tried with 2.0 and it works perfectly but Im still getting the WiFiClientSecure errors with 2.0.1 which I sadly need for the reduced size. I dont really know either if I should ask this to the esp32 core developers than you

[mobizt]

You should stay with v2.0.0 instead of 2.0.1-rc1 which contains bugs and not yet final release.

[mobizt]

The error when you compile the library with esp32 core v2.0.1-RC1 is about this workaround code

Firebase-ESP-Client/src/wcs/esp32/FB_TCP_Client.h

Line 91 in 142dd22

int ret = start_ssl_client(sslclient, host, port, _timeout, _CA_cert, NULL, NULL, NULL, NULL, _use_insecure);

that used to fix the serious memory leaks issue in core WiFiClientSecure class, which this issues have been report by me and others at esp32 repo

espressif/arduino-esp32#5480
espressif/arduino-esp32#5781
espressif/arduino-esp32#5826

Which start_ssl_client defined here in v2.0.1-RC1
https://github.com/espressif/arduino-esp32/blob/caa8d07aafa04441bb85e6046a795249c01d9e39/libraries/WiFiClientSecure/src/ssl_client.h#L32
which required extra argument **const char alpn_protos for http2 protocol and just added in v2.0.1-RC1.

If I remove the workaround, the library can compile in core v2.0.1-RC1 unless the bugs in core WiFiClientSecure class can make your device crashed due to out of memory.

There is no macro to check the Arduino core version at compile time unless the ESP-IDF version which is the same v4.4.0 for ESP32 core v2.0.0 and v2.0.1-RC1.

[Frtrillo]

Well then I take we will have to wait for esp 32 core to fix wificlientsecure leaks? So far Ive managed to use ESP32 2.0, by taking only the 2.0.1 memory optimize commit, it was on this branch but it was removed: espressif/arduino-esp32#5697, althought I managed to download it before if someone needs it as well

[mobizt]

Now I fix the ESP32 memory leaks workaround in the v2.6.4 to support ESP32 core v2.0.1-RC1.

You can update the library.

[mobizt]

Thank you for your support.