You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it makes sense, because the timer is first started for 200 ms, so after a 550 ms delay, it is not running. Hence, we can start it again without getting an error.
If you want to start an already-running timer, you first need to call esp_timer_stop to cancel it.
@diplfranzhoepfinger Closing this issue as it's not a bug. ESP Timer start APIs are designed to return ESP_ERR_INVALID_STATE if the timer is already running.
Answers checklist.
General issue report
using this:
https://github.com/diplfranzhoepfinger/esp_timer_example
it is the Example:
https://github.com/espressif/esp-idf-cxx/blob/main/examples/esp_timer_cxx/main/esp_timer_example.cpp
and modify it like this:
and it works, the Timer can be started 2 times.
but in another Application i get this:
Exception with error: 259 ESP_ERR_INVALID_STATE
ESP_ERR_INVALID_STATE if the timer is already running
The text was updated successfully, but these errors were encountered: