a421e30cf2
Functions used for burning this efuse would log, but at this point esp_log is not initialized. Moved to a later point in the startup process. Closes https://github.com/espressif/esp-idf/issues/9457 |
||
|---|---|---|
| .. | ||
| include | ||
| ld | ||
| port | ||
| test | ||
| test_apps | ||
| test_eh_frame_parser | ||
| CMakeLists.txt | ||
| Kconfig | ||
| Makefile.projbuild | ||
| README.md | ||
| app.lf | ||
| component.mk | ||
| crosscore_int.c | ||
| debug_stubs.c | ||
| eh_frame_parser.c | ||
| esp_err.c | ||
| esp_system.c | ||
| fpga_overrides.c | ||
| freertos_hooks.c | ||
| int_wdt.c | ||
| linker.lf | ||
| panic.c | ||
| sdkconfig.rename | ||
| stack_check.c | ||
| startup.c | ||
| system_time.c | ||
| task_wdt.c | ||
| ubsan.c | ||
| xt_wdt.c | ||
README.md
System Notes
Timekeeping
The following are the timekeeping mechanisms available and their differences:
- System time (
esp_system_get_time)
Time with the origin at g_startup_time. The implementation is not handled by esp_system,
but it does provide a default implementation using RTC timer. Currently, esp_timer
provides system time, since the hardware timers are under the control of that
component. However, no matter the underlying timer, the system time provider
should maintain the definition of having the origin point at g_startup_time.
esp_timertime (esp_timer_get_time)
This is the time read from an underlying hardware timer, controlled through config. Origin is at the point where the underlying timer starts counting.
newlibtime (gettimeofday)
Timekeeping function in standard library. Can be set (settimeofday) or moved forward/backward (adjtime);
with the possibility of the changes being made persistent through config.
Currently implemented in terms of system time, as the point of origin is fixed.
If persistence is enabled, RTC time is also used in conjuction with system time.
- RTC time (
esp_rtc_get_time_us)
Time read from RTC timer.