Can follow this issue via Github
https://github.com/espressif/esp-mesh-lite/issues/193

Hi all,

I've been trying to see what actually needs to be de-initialised or destroyed when changing Wi-Fi details and so far i've got to the stage of

E (11:59:21.497) esp_netif_lwip: esp_netif_new_api: Failed to configure netif with config=0x3fcce150 (config or if_key is NULL or duplicate key ...

Update:

Calling or setting the below will have an adverse affect on the mesh ocnfig,

Hi All,

Consider the issue solved! Well at least half solved, I've found the code where just not found a way to fully patch it yet :lol:

The issue, bizarrely was caused due to the Mesh_lite config being called and set via a function call in app_main() instead of being set via menuconfig or prior ...

Update:
I've found that the IRAM interrupt was a contributing factor but not the cause of the issue. Since removing it I've had a mixture of failed writing to flash or the same guru errors.

Update 2:
I've stitched HTTPS_OTA into the local_control example of mesh_lite v1.0.2 with MQTT over TCP, and ...

```
D (00:33:29.842) main: HTTP_EVENT_ON_DATA, len=512
D (00:33:29.847) event: no handlers have been registered for event ESP_HTTP_CLIENT_EVENT:4 posted to loop 0x3fca99c0
D (00:33:29.861) esp_https_ota: Written image length 210944
D (00:33:29.864) event: no handlers have been registered for event ...

images attached

backtrace image 1
debugger image 2

ESP-IDF v5.3.2
ESP32S3 chip rev v0.2
partition table: 2 large OTA partitions no factory partition

Hi all,

I've been wrestling this guru error for some time and I'm stuck not knowing what is calling cached memory during the update.

I'm using the following within my code:
esp_mesh_lite (master v1 ...

Update - SOLVED:
I've since resolved this issue by altering the position of where the channels are initalised; By initialising them outside of the setup function and along with the global variables, the LEDC_get_duty function can correctly see the GPIO that the channel is associated with.

Update:
I've since moved to a mesh network of all S3's and none of the nodes see or connect to each other. ESP-WROOM-32s see each other... is the mesh_lite library bugged with S3 hardware?