ESP-IDF Monitor freezes suddenly
Posted: Wed Mar 22, 2023 9:36 am
Hi
This is probably a very general and vague question but I'm having trouble with the ESP32-S3 [ESP_PRIMARY] idf monitor output suddenly freezes without any form of error messages. I would assume if anything critical would happen that it would return some kind of output indicating why the chip might have crashed. The flow sometimes works for a few minutes and then suddenly after some time it freezes.
The application is build up using tasks and FreeRTOS. Some of the tasks running are:
- A websocket interface tasks
- A SPI master tasks which sends commands to another ESP32-S3 [ESP_SECONDARY]
- A I2C slave tasks which recieves commands from the other ESP32-S3. [ESP_SECONDARY]
When I get a websocket message this is forwarded to the SPI tasks which will forward the data to the other ESP32. Then as a result the other ESP32 [ESP_SECONDARY] will send I2C messages back to the main ESP32 [ESP_PRIMARY] which are then forwarded back to the connected websocket.
The general questions then are:
Are there any of these steps that would most likely cause this monitor freeze/reboot of the ESP32?
And what would be a good way to debug this?
This is probably a very general and vague question but I'm having trouble with the ESP32-S3 [ESP_PRIMARY] idf monitor output suddenly freezes without any form of error messages. I would assume if anything critical would happen that it would return some kind of output indicating why the chip might have crashed. The flow sometimes works for a few minutes and then suddenly after some time it freezes.
The application is build up using tasks and FreeRTOS. Some of the tasks running are:
- A websocket interface tasks
- A SPI master tasks which sends commands to another ESP32-S3 [ESP_SECONDARY]
- A I2C slave tasks which recieves commands from the other ESP32-S3. [ESP_SECONDARY]
When I get a websocket message this is forwarded to the SPI tasks which will forward the data to the other ESP32. Then as a result the other ESP32 [ESP_SECONDARY] will send I2C messages back to the main ESP32 [ESP_PRIMARY] which are then forwarded back to the connected websocket.
The general questions then are:
Are there any of these steps that would most likely cause this monitor freeze/reboot of the ESP32?
And what would be a good way to debug this?