esp-idf/components/esp_system
Armando 2655a506c9 mspi: support auto detect octal flash vendor 2021-10-08 15:59:57 +08:00
..
include
ld components/bt: move config BT_RESERVE_DRAM from bluedroid to ESP32 controller 2021-09-16 20:26:35 +08:00
port mspi: support auto detect octal flash vendor 2021-10-08 15:59:57 +08:00
test tests: refactoring of the gcc's inner functions, because clang doesn't support them 2021-09-10 19:51:27 +03:00
test_eh_frame_parser
CMakeLists.txt
Kconfig components/doc: Update doc about high-level interrupt 2021-09-09 20:40:09 +08:00
Makefile.projbuild
README.md
app.lf
component.mk esp_system: create ld template to abstract few common settings 2021-09-02 16:13:17 +08:00
crosscore_int.c
dbg_stubs.c
eh_frame_parser.c
esp_err.c
esp_system.c
fpga_overrides.c
freertos_hooks.c
int_wdt.c components/bt: add config option to choose Bluetooth intterupt level. 2021-09-09 11:29:17 +08:00
linker.lf
panic.c esp_system: make the abort operation compatible with clang 2021-09-16 11:07:54 +02:00
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:

  1. 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.

  1. esp_timer time (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.

  1. newlib time (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.

  1. RTC time (esp_rtc_get_time_us)

Time read from RTC timer.