Closed sagar448 closed 4 years ago
Thanks for reporting.
@sagar448 Thanks for reporting, would you please help provide simple working example to reproduce this issue? Thanks.
@Alvin1Zhang I think we had the same issue but not exactly in the ESP-IDF. We are using Arduino with the leatest versions (for the board and for the Arduino env itself).
We investigated that this issue is only happened when we are on battery power (3.3V). I do not want to falme this thread, so here is the link where I wrote the symptomps: https://github.com/espressif/arduino-esp32/issues/796#issuecomment-678757960
If I can try or check anything for you to help solving the problem please let me know. Thanks.
@zonehun stop hijacking my post please. Post your issue in the arduino section.
@Alvin1Zhang I cannot provide an example because its very random. But I think we have solved this issue. For anyone experiencing the same, we essentially stripped down the esp32 from the menuconfig. Disabling features we did not need.
git describe --tags
to find it): v3.3.2-14-g6c9c253edxtensa-esp32-elf-gcc --version
to find it): 1.22.0-80-g6c4433a5Problem Description
Sorry for the long explanation.
We were using Arduino and our code involves interfacing with the two sensors, BME680 and TCS. We wake up every 5 minutes from deep sleep take readings, send them via esp now and go back to deep sleep. Issue was that after a random amount of wakeups the esp32 would just get stuck after waking up and not produce any error and be halted. Here is the Arduino issue, still not been resolved. https://github.com/espressif/arduino-esp32/issues/796
Seeing as how we never had this issue with ESP-IDF we decided to switch to ESP-IDf. Now it feels like the issue persists. It would get stuck and not wake up. The worst of it is that when we turn on verbose logging to get further information we have further complications. We had to change the partition offset from 0x8000 to 0x10000. When we did so, a line in our code esp_light_sleep_start() started giving us abort issues in regards to the lock.c file. Trying to do verbose with 0x8000 offset, causes issues. So we are unable to see the logs for when it gets stuck in deep sleep reset.
Expected Behavior
It should not get stuck after deep sleep reset.
Actual Behavior
After a random number of cycles it gets stuck in deep sleep reset.
Code to reproduce this issue
This is the main.c file
This is the sensor begin file
Any help will be greatly appreciated.
It is also very hard to reproduce because it gets stuck sporadically and not after the same number of cycles.