f2743707b8
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. |
||
|---|---|---|
| .. | ||
| include | ||
| ld | ||
| port | ||
| task_wdt | ||
| test | ||
| test_apps | ||
| test_eh_frame_parser | ||
| .build-test-rules.yml | ||
| app.lf | ||
| check_system_init_priorities.py | ||
| CMakeLists.txt | ||
| crosscore_int.c | ||
| debug_stubs.c | ||
| eh_frame_parser.c | ||
| esp_err.c | ||
| esp_ipc.c | ||
| esp_system.c | ||
| fpga_overrides.c | ||
| freertos_hooks.c | ||
| int_wdt.c | ||
| Kconfig | ||
| linker.lf | ||
| panic.c | ||
| README.md | ||
| sdkconfig.rename | ||
| sdkconfig.rename.esp32 | ||
| sdkconfig.rename.esp32c3 | ||
| sdkconfig.rename.esp32h2 | ||
| sdkconfig.rename.esp32s2 | ||
| sdkconfig.rename.esp32s3 | ||
| stack_check.c | ||
| startup.c | ||
| system_init_fn.txt | ||
| system_time.c | ||
| ubsan.c | ||
| xt_wdt.c | ||
System Notes
Timekeeping
The following are the timekeeping mechanisms available and their differences:
- 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.
esp_timertime (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.
newlibtime (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.
- 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.