esp-idf/components/esp_system
Mahavir Jain 6d2153d703 fix(ota): additional checks for secure version in anti-rollback case
Some additional checks related to secure version of the application in
anti-rollback case have been added to avoid any attempts to boot lower
security version but valid application (e.g., passive partition image).

- Read secure_version under sha256 protection

- First check has been added in the bootloader to ensure correct secure
  version after application verification and loading stage. This check
  happens before setting up the flash cache mapping and handling over
  the final control to application. This check ensures that application
  was not swapped (e.g., to lower security version but valid image) just
  before the load stage in bootloader.

- Second check has been added in the application startup code to ensure
  that currently booting app has higher security version than the one
  programmed in the eFuse for anti-rollback scenario. This will ensure
  that only the legit application boots-up on the device for
  anti-rollback case.
2024-02-15 15:23:19 +02:00
..
include feat(wifi): optimize iperf performance (Backport V4.4) 2023-10-13 11:36:03 +08:00
ld fix(memory): no enough memory for rodata 2023-10-25 08:02:02 +00:00
port fix(clk): clear all lpclk source at clk init 2024-02-06 16:07:40 +08:00
test
test_apps
test_eh_frame_parser
CMakeLists.txt
Kconfig fix(rtc): fixed bbpll not calibrated from bootloader issue 2024-01-16 18:09:48 +08:00
Makefile.projbuild
README.md brownout: Disable the hardware BOD when BOD interrupt is enabled 2023-11-28 17:01:19 +08:00
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 fix(ota): additional checks for secure version in anti-rollback case 2024-02-15 15:23:19 +02:00
system_time.c
task_wdt.c fix(wdt): fixed potential WDT timeout when deinitializing task watchdog 2023-09-14 13:16:46 +08:00
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.