esp-idf/components/esp_system
Konstantin Kondrashov f875978fb3 Merge branch 'bugfix/incorrect_time_after_ota' into 'master'
esp_hw_support: Fix invalid system time if s_esp_rtc_time_us & s_rtc_last_ticks were moved around

Closes IDFGH-7930

See merge request espressif/esp-idf!23030
2023-06-09 00:30:52 +08:00
..
include Merge branch 'feature/libunwind_backtracing' into 'master' 2023-05-16 14:19:16 +08:00
ld esp_hw_support: Fix invalid system time if s_esp_rtc_time_us & s_rtc_last_ticks were moved around 2023-06-08 21:59:21 +08:00
port Merge branch 'feature/esp_ipc_isr_fix' into 'master' 2023-05-24 23:17:37 +08:00
task_wdt
test_apps ci: re-enable reset reason tests for all targets except H2. 2023-05-12 19:00:27 +08:00
test_eh_frame_parser System: implement libunwind library for RISC-V backtracing 2023-05-15 11:19:03 +08:00
.build-test-rules.yml ci: fix invalid kconfig options in system test apps 2023-05-09 11:27:55 +08:00
CMakeLists.txt esp_app_format: IRAM space optimization 2023-05-17 23:40:59 +08:00
Kconfig
README.md
app.lf
check_system_init_priorities.py
crosscore_int.c
debug_stubs.c
eh_frame_parser.c System: implement libunwind library for RISC-V backtracing 2023-05-15 11:19:03 +08:00
esp_err.c
esp_ipc.c
esp_system.c
fpga_overrides.c
freertos_hooks.c
int_wdt.c
linker.lf
panic.c esp_app_format: IRAM space optimization 2023-05-17 23:40:59 +08:00
sdkconfig.rename
sdkconfig.rename.esp32
sdkconfig.rename.esp32c3
sdkconfig.rename.esp32s2
sdkconfig.rename.esp32s3
stack_check.c
startup.c
system_init_fn.txt
system_time.c
systick_etm.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.

Brownout

on some boards, we name BOD1 as ana_bod, to unify the usage, using BOD1 in following passage.

BOD1 will be a little faster then BOD0, but BOD0 can be widely used(can reset rf, flash, or using interrupt, etc.) So, in IDF code, we use BOD1 in bootloader and BOD0 in the app.