alex/esp-idf
alex/esp-idf
1
0
Fork 0
mirror of https://github.com/espressif/esp-idf.git synced 2024-10-05 20:47:46 -04:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity
299fa49d75
esp-idf/components/esp_system
History
Mahavir Jain 67a1fe6373 fix(startup): flip the security configuration check order 
For cases where the bootloader is not enabled with the security features
ends up receiving an incorrect application with flash encryption enabled
should not really program any security efuses.

In the startup sequence, we first used to program the ROM DL mode
configuration but now we check for the flash encryption related checks
first. If the flash encryption related checks finds that flash
encryption is not enabled on the device then it aborts the boot process.
This is the case with `CONFIG_SECURE_FLASH_CHECK_ENC_EN_IN_APP` enabled.

This would at-least ensure that accidental program of security enabled
application does not really program any ROM DL mode efuses and there is
chance to recover the device.
2023-10-09 03:30:11 +00:00
..
include fix(esp_system): suppress compiler warning if ESP_SYSTEM_PANIC_SILENT_REBOOT is enabled 2023-09-28 02:53:07 +00:00
ld Merge branch 'bugfix/incorrect_time_after_ota_v5.0' into 'release/v5.0' 2023-08-23 16:34:43 +08:00
port Merge branch 'bugfix/esp32s3_usb_otg_console_v5.0' into 'release/v5.0' 2023-08-21 10:37:29 +08:00
task_wdt esp_system: Fix TIMG0 still enabled after Timer is freed 2023-03-07 10:02:06 +08:00
test Change: rewrite EXT1 triggle mode all_low to any_low when not esp32 2023-07-25 17:53:33 +08:00
test_apps TWDT: Use the new TWDT Kconfig options in the examples and tests 2023-03-07 10:23:43 +08:00
test_eh_frame_parser esp_hw_support/esp_system: Re-evaluate header inclusions and include directories 2022-03-07 11:18:08 +05:30
.build-test-rules.yml feat: use standalone project idf-build-apps for find/build apps utils 2022-07-14 08:26:31 +08:00
app.lf esp32: move common fragment definitions 2021-03-31 19:17:33 +08:00
check_system_init_priorities.py esp_system: add a script to check the startup priorities 2022-07-12 16:58:14 +02:00
CMakeLists.txt TWDT: the Kconfig option ESP_TASK_WDT_EN is now used to enable Task Watchdog 2022-12-01 10:45:35 +00:00
crosscore_int.c TWDT: the Kconfig option ESP_TASK_WDT_EN is now used to enable Task Watchdog 2022-12-01 10:45:35 +00:00
debug_stubs.c debug_stubs: Refactor and add support for RISCV 2021-11-04 01:33:24 +03:00
eh_frame_parser.c esp_hw_support/esp_system: Re-evaluate header inclusions and include directories 2022-03-07 11:18:08 +05:30
esp_err.c esp_system: fix address printed by ESP_ERROR_CHECK 2022-07-12 17:01:47 +02:00
esp_ipc.c ipc: Increase stacksize when compiling with -O0 2022-07-18 13:55:03 +08:00
esp_system.c system: disable interrupts in esp_restart_noos_dig 2022-12-22 11:34:38 +01:00
fpga_overrides.c ESP8684: add freertos, hal, esp_system support 2021-11-06 17:33:44 +08:00
freertos_hooks.c hal: Deprecate interrupt_controller_hal.h, cpu_hal.h and cpu_ll.h interfaces 2022-07-22 00:06:06 +08:00
int_wdt.c WDT: implement interrupt wdt and task wdt for ESP32-C2 2022-12-01 10:45:35 +00:00
Kconfig konfig: make rtc fast mem related kconfig depend on SOC_RTC_FAST_MEM_SUPPORTED 2023-03-06 11:53:35 +08:00
linker.lf esp_system: usb_console: fix restart when Wi-Fi is working 2022-07-28 17:15:03 +02:00
panic.c mcpwm: reset peripheral in restart, panic and halt 2023-05-18 04:56:34 +00:00
README.md brownout: Disable the hardware BOD when BOD interrupt is enabled 2023-07-11 14:46:30 +08:00
sdkconfig.rename TWDT: Use the new TWDT Kconfig options in the examples and tests 2023-03-07 10:23:43 +08:00
sdkconfig.rename.esp32 kconfig: move remaining kconfig options out of target component 2022-05-23 17:57:45 +08:00
sdkconfig.rename.esp32c3 soc: moved kconfig options out of the target component. 2022-04-21 12:09:43 +08:00
sdkconfig.rename.esp32h2 soc: moved kconfig options out of the target component. 2022-04-21 12:09:43 +08:00
sdkconfig.rename.esp32s2 soc: moved kconfig options out of the target component. 2022-04-21 12:09:43 +08:00
sdkconfig.rename.esp32s3 soc: moved kconfig options out of the target component. 2022-04-21 12:09:43 +08:00
stack_check.c esp_system: fix placement of __stack_chk_fail from flash to RAM 2022-12-14 12:37:23 +01:00
startup.c fix(startup): flip the security configuration check order 2023-10-09 03:30:11 +00:00
system_init_fn.txt esp_system: usb_console support for ESP32-S3 2023-07-18 18:15:37 +02:00
system_time.c esp8684: rename target to esp32c2 2022-01-19 11:08:57 +08:00
ubsan.c hal: Deprecate interrupt_controller_hal.h, cpu_hal.h and cpu_ll.h interfaces 2022-07-22 00:06:06 +08:00
xt_wdt.c bugfix (esp_system): made xt_wdt spinlock static 2022-07-22 08:17:59 +00: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.