Hi rudi,

first a little update, I have 10 appliances running with the reconnect fix for about 7 days now including heavy application pSRAM usage (albeit with the LWIP and WiFi sRAM usage disabled) so I would say for v4.1 pSRAM is working fine.

At this moment I work without debugging but with the ...

Hi rudi,

for sure I can say that with my current ESP-IDF revision tags/v4.1 I have a crash if I call esp_netif_destroy from WIFI_EVENT_STA_DISCONNECTED. Now that I seem to have a stable revision I can try to test this also with other revisions.

I found one error that explains at least a big portion of the reboots, not yet sure if all. In case of a WIFI_EVENT_STA_DISCONNECTED event I used esp_netif_destroy in order to clean the old state and then esp_netif_create_default_wifi_sta to recreate the state. I was able to observe a crash every ...

From now on I will start to do all testing with tags/v4.1 to make sure I don't use any currently unsupported ESP-IDF version. With release/v4.2 I had very strange behaviour, for example the application worked with pSRAM disabled, with pSRAM enabled but not used (usage disabled everywhere in ...

do you get again a stack overflow in task LogWriterTask or was it an other?

I don't really know unfortunately. The way the UART output looks I see three scenarios:


LogWriterTask on CPU1 still runs and throws new exceptions (thats why there is no "bootup" output
The "bootup" output is ...

After flashing a firmware with pSRAM completely disabled in menuconfig and replacing all external with internal mallocs I was now able to see that overnight there were again reboots in 2 out of four electronics with ESP_RST_WDT as reset reason so I assume that the pSRAM is not at fault.

Hi rudi, thank you very much for your restless support :D

and edit this post, have read your post. in the meantime, can you check, which Pico SoC Version you use with this "error"? ( V0, V1, V3 ) ( you wrote: I have a version 1 , ) ok,

I think we ordered some "sample quantity" directly from ...

Hi rudi,

thanks for following up. This is our own design and unfortunately I can not easily share the schematics without an NDA. What I can say is that since I upgraded to the current master and enabled SPIRAM_CACHE_WORKAROUND it seems to be more stable. In general the application (now ported to ...

In addition this is in the v4.2-beta release notes:

The esp-2020r2 toolchain has been added in this release which includes some fixes for C++ exceptions, a fix for -O2 optimization of volatile word accesses, and an improved PSRAM fix. Extended stress testing of Wi-Fi & BT coexistence with heavy ...

Hi Sprite,

thank you very much for your answers. As you say there are different revisions for the Pico and I have a version 1 I expect I have to enable SPIRAM_CACHE_WORKAROUND in the sdkconfig, correct? My chips were purchased from Espressif very recently, I expect I can leave this option enabled ...