Replies: 1 comment
-
The function you are looking for is defined here: arduino-esp32/cores/esp32/esp32-hal-time.c Lines 48 to 61 in c93bf11 And I suspect the esp_netif_init(); to crash your program as
(See IDF docs), but the function is already called for the WiFi stuff: You may need to create an issue and/or PR for this... |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've been trying to trace why a program with several running tasks has one low priority task that never gets serviced. I found by a process of elimination that if I simply comment out the line: configTime(gmtOffset_sec, daylightOffset_sec, ntpServer) everything works as I would expect, except for the time being wrong (obviously). All my tasks yield at some point and let execution take place at all priority levels so long as I don't call configTime(). I even tried calling it from a lowest priority task of its own but that made no difference.
I haven't had any success trying to find the inner workings of NTP for arduino-esp32 as some important links seem to be to esp8266 code and some are broken. Is anyone familiar with the way NTP time is handled and how it might interfere with the task scheduler?
Beta Was this translation helpful? Give feedback.
All reactions