I am trying to set up the webserver to be able to receive a file from the web page and then be able to query the progress from the web page to the webserver. Before I was using the async feature addition in 5.2 I had been able to upload the file from v 5.0. I had been reading that I had to upgrade ...

Hello,
Is it possible to send this privately in chat or email? the entire log has company sensitive information.

Both cores run freertos, core 1 has some of the tasks pinned to it including LWIP.

Hello,
interesting thing is when this happens I get no trace of any shape since CPU locks up, it just reboots and on the next boot it prints the PC mentioned above. Is there any other method to get more info from it to send you?

Hello, We have built a product using ESP32-PICO-V3-MINI module. We do use the 2MB PSRAM mostly for a large queue and also Task stacks. We get lots of watch dog resets related to live lock(Using IDF V5.1 stable release): 0x40081c84: .handle_livelock_int at C:/Espressif/frameworks/esp-idf-v5.1/compone...

I have been successfully using my PICO-D4 with PSRAM for 2 years on hundreds of boards now, however once I updated IDF to master branch (v4.1-dev-1891-g3634192de-dirty) which is supposed to have PSRAM support for PICO-D4, my code broke and is crashing with this error on boot: E (1220) memory_layout:...

Hello ESP experts. I have tested the modbus slave example with Uart2 and everything works fine. However I need to use Uart0 instead. I have changed the console port to uart1 and changed modbus port to uart0. Even though the console is now successfully moved to uart1, but modbus doesn't work on uart0...

I have the same issue. As soon as I enable the option for Wifi and LWIP stack to allocate from PSRAM, weird things such as WiFi not connecting starts happening. Were you ever able to figure this out?

Yes, I have a better idea of where the issue is now. Like @ESP_Sprite mentioned, I knew that disabling the workaround will most likely cause unrecoverable issues in the future, and since my device is in the field, it will be hard to deal with. I dug a bit deeper, just messing around with sdkconfig p...

I found the issue ! Under menu config, if I enable any or both of the following two options, weird things such as the one I explained starts happening: -- CONFIG_SPIRAM_CACHE_WORKAROUND As soon as I turn it off, things start working again!! So between idf 3.1 and 3.3 someone has changed something in...

Still looking. I think I will have to dig deeper into the API source, but I have to narrow it down first. I'm thinking it is most likely in WiFi, LWIP modules.