esp-idf/components/esp_system
Alexey Lapshin a120ea823e Merge branch 'contrib/github_pr_11569' into 'master'
[GDBStub] kconfig gdbstub runtime should be separate bool (GitHub PR)

Closes IDF-7846 and IDFGH-10309

See merge request espressif/esp-idf!24775
2023-08-02 07:50:47 +08:00
..
include feat(esp_system): base support on p4 2023-07-25 05:59:10 +00:00
ld feat(esp_system): base support on p4 2023-07-25 05:59:10 +00:00
port feat(cache): added cache init configurations on p4 2023-07-25 05:59:10 +00:00
task_wdt feat(esp_system): base support on p4 2023-07-25 05:59:10 +00:00
test_apps remove(pm/deep_sleep): enable CI test for esp32h2 deepsleep 2023-07-27 12:11:35 +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 feat(esp_system): implement hw stack guard for riscv chips 2023-07-01 16:27:40 +00:00
Kconfig feature(gdbstub): Move runtime gdbstub out of panic config 2023-08-01 14:28:07 +04:00
README.md brownout: Disable the hardware BOD when BOD interrupt is enabled 2023-04-21 10:22:59 +08:00
app.lf feat(tcm): added tcm basic support on esp32p4 2023-07-25 05:59:10 +00:00
check_system_init_priorities.py
crosscore_int.c feat(esp_system): base support on p4 2023-07-25 05:59:10 +00:00
debug_stubs.c esp_system: fix and reenable no-format warning 2023-03-28 13:42:44 +02:00
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 refactor(freertos): Refactor usage of portBASE_TYPE to BaseType_t 2023-07-31 17:10:34 +02:00
esp_system.c System: remove digital-system reset within OS restart when Memprot on 2023-06-26 20:22:59 +02:00
fpga_overrides.c feat(gptimer): driver support on esp32p4 2023-07-26 19:27:49 +08:00
freertos_hooks.c
hw_stack_guard.c feat(esp_system): implement hw stack guard for riscv chips 2023-07-01 16:27:40 +00:00
int_wdt.c feat(esp_system): base support on p4 2023-07-25 05:59:10 +00:00
linker.lf feat(esp_system): implement hw stack guard for riscv chips 2023-07-01 16:27:40 +00:00
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 efuse: add efuse hal api 2023-04-18 13:47:00 +05:30
system_init_fn.txt feat(esp_system): implement hw stack guard for riscv chips 2023-07-01 16:27:40 +00:00
system_time.c feat(esp_system): base support on p4 2023-07-25 05:59:10 +00:00
systick_etm.c
ubsan.c
xt_wdt.c esp_system: fix and reenable no-format warning 2023-03-28 13:42:44 +02:00

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.