Required to lock TCPIP core functionality!

[RoelHermus]

The installing the latest 3.1.0 version of ESP32 by ESpressif System continuously restarts the esp32 with the error:

assert failed: tcp_alloc /IDF/components/lwip/lwip/src/core/tcp.c:1851 (required to lock the TCPIP core functionality!)

After reinstalling version 3.0.7, the problem was solved.

[me-no-dev]

will be fixed/updated to work with core 3.1.0

[xinkiknix]

Same issue on ESP32S3

[bilalakhtar]

@lbernstone Thank you for pointing this out. I reviewed the ESPAsyncWebServer repository, and it seems the issue is indeed related to the "Required to lock TCPIP core functionality!"

[bilalakhtar]

Same issue with esp32, @me-no-dev Kindly look into this issue.

[shortrangetech]

confirming I am also getting the same "Required to lock TCPIP" issue on an ESP32-WROOM-32D. Downgrading to the previous version of esp32 by espressif also solved the problem for me.

[bilalakhtar]

@sh0rtrange Thank you! I'll try that as a temporary workaround. I really appreciate your input!

[micha6554]

ESP32C6 error on "tcp.c:1851"
Thanks for help

[enotanet]

3.1.1 - no fix changes, still "required to lock the TCPIP core functionality!"

[sudo-Mystic]

3.6.0 , facing same issue

[jp-stewart]

++ Adding that I see the same on the waveshare esp32 c3 and that downgrade worked. Thank you!

[sudo-Mystic]

++ Adding that I see the same on the waveshare esp32 c3 and that downgrade worked. Thank you!

Hey can you tell me which version are you using? thank you

[jp-stewart]

++ Adding that I see the same on the waveshare esp32 c3 and that downgrade worked. Thank you!

Hey can you tell me which version are you using? thank you

Hmmm -- investigating this question has shown me that it seems I stopped updates at some point. I have version 3.1.2 of espasyncwebserver. Which means I must have encountered other errors that caused me to stop at this version (and I don't remember why anymore :/)

But confirming that the 3.1.0 to 3.0.7 downgrade of esp sdk fixed the errors.

[ceewanna]

@me-no-dev My chips were on pioarduino of older version https://github.com/pioarduino/platform-espressif32/releases/download/51.03.07/platform-espressif32.zip without the TCPIP issue.

1. Recently I tried uploading from an esp32 library builder which happened to be based on idf 5.3 and was hit by a problem saying something like asserting TCPIP .... The chips kept rebooting with the error message.

2. Using pioarduino 53.03.11 causes this same issue.
   assert failed: tcp_alloc /IDF/components/lwip/lwip/src/core/tcp.c:1851 (Required to lock TCPIP core functionality!)

[mathieucarbou]

FYI: you can have a look at the community maintained forks here where several people are collaborating towards maintaining these 2 good libraries with a frequent release cycle:

• https://github.com/mathieucarbou/AsyncTCP/
• https://github.com/mathieucarbou/ESPAsyncWebServer/

This issue is fixed since October 2024 in these repos above and they always tested in CI against latest Arduino RC.
Ref: espressif/arduino-esp32#10526

[ceewanna]

@mathieucarbou
I am testing yours.
What should I set to get rid of these? I am not familar with RP2040W and only run ESP32 and ESP8266.

In file included from .pio/libdeps/release_upload/AsyncTCP_RP2040W/src/AsyncPrinter.h:51, from .pio/libdeps/release_upload/AsyncTCP_RP2040W/src/AsyncPrinter.cpp:51: .pio/libdeps/release_upload/AsyncTCP_RP2040W/src/AsyncTCP_RP2040W.h:73:4: error: #error For RASPBERRY_PI_PICO_W board using CYW43439 WiFi only 73 | #error For RASPBERRY_PI_PICO_W board using CYW43439 WiFi only | ^~~~~ Compiling .pio/build/release_upload/libeaa/AsyncTCP_RP2040W/AsyncTCP_RP2040W_buffer.cpp.o In file included from .pio/libdeps/release_upload/AsyncTCP_RP2040W/src/AsyncTCP_RP2040W.cpp:104: .pio/libdeps/release_upload/AsyncTCP_RP2040W/src/AsyncTCP_RP2040W.h:73:4: error: #error For RASPBERRY_PI_PICO_W board using CYW43439 WiFi only 73 | #error For RASPBERRY_PI_PICO_W board using CYW43439 WiFi only