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.

I Upgraded from 3.1, master is doing the same thing. Actually my previous thought was wrong, the issue had nothing to do with the interface call. The issue is ping process starting before wifi stack (I use ethernet interface as well). So what I did is put a flag so it waits for wifi to initialize a...

I Upgraded from 3.1, master is doing the same thing. Actually my previous thought was wrong, the issue had nothing to do with the interface call. The issue is ping process starting before wifi stack (I use ethernet interface as well). So what I did is put a flag so it waits for wifi to initialize an...

I found the issue! I was calling the following function in my ping task every 100 ms, and apparently calling this too often will choke the wifi stack in the new version of IDF, can someone please clarify why?

ESP_ERROR_CHECK(tcpip_adapter_get_ip_info(TCPIP_ADAPTER_IF_ETH, &ip));

It seems like there is an issue with the esp_ping that causes wifi driver to stop acting properly. I had a code that has been running for a while, but as soon as I updated to this version of IDF it stopped working. The program is running a task called main which checks for connectivity by pinging th...