Hello, I'm trying to develop a device with the OTA feature, and now using the below example.
https://github.com/espressif/esp-idf/tr ... system/ota
It rarely got success, but in almost all cases, I got the below message.
I tried to put vTaskDelay(10) and watchdog deinit or reset, but got nothing at all.
I don't know the exact reason and what I use now is the official example. The task does not come up again if it fall into that situation.
Any suggestions would be much appreciated.
Task watchdog got triggered with OTA example
Re: Task watchdog got triggered with OTA example
Try to see if any of the following modifications can suppress the issue:
- Increase Task Watchdog Timeout Period in menuconfig (e.g. from 5 seconds to 10)
- Add a short vTaskDelay(10) at the end of the while (socket_flag) { loop so that there is a short gap between every iteration
- Increase Task Watchdog Timeout Period in menuconfig (e.g. from 5 seconds to 10)
- Add a short vTaskDelay(10) at the end of the while (socket_flag) { loop so that there is a short gap between every iteration
Re: Task watchdog got triggered with OTA example
Sorry but both of what you suggested didn't work.
I already tried vTaskDelay with many values, but it doesn't affect anything.
After changing the time in menuconfig, the delay got longer after
<E (1794) wifi: pp.c 3379>.
But it still stops after some writings, and delay didn't recover the situation.
I think there might be some error in pp.c showed in that log message.
Thank you for your help, and let me know if you have any other ideas.
I already tried vTaskDelay with many values, but it doesn't affect anything.
After changing the time in menuconfig, the delay got longer after
<E (1794) wifi: pp.c 3379>.
But it still stops after some writings, and delay didn't recover the situation.
I think there might be some error in pp.c showed in that log message.
Thank you for your help, and let me know if you have any other ideas.
Re: Task watchdog got triggered with OTA example
Finally I got what the problem is.
The AP I connected to used WEP encryption, and somehow it makes the error above.
After chaning to WPA2PSK encryption, the error went away and didn't appear anymore.
You should write this somewhere in the docs or fix the issue with WEP encrypted AP to prevent others from getting the same errors.
Please let me know if there's any workaround for WEP, otherwise, it seems I have to handle this by counting the failures.
The AP I connected to used WEP encryption, and somehow it makes the error above.
After chaning to WPA2PSK encryption, the error went away and didn't appear anymore.
You should write this somewhere in the docs or fix the issue with WEP encrypted AP to prevent others from getting the same errors.
Please let me know if there's any workaround for WEP, otherwise, it seems I have to handle this by counting the failures.
Who is online
Users browsing this forum: Baidu [Spider], pbeam66 and 115 guests