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
9ee667eb15
esp-idf/components/esp_system/system_init_fn.txt

108 lines
6.1 KiB
Plaintext
Raw Normal View History

esp_system: add a script to check the startup priorities
2022-05-18 11:25:38 -04:00
# This file documents the expected order of execution of ESP_SYSTEM_INIT_FN functions.
#
# When adding new ESP_SYSTEM_INIT_FN functions or changing init priorities of existing functions,
# keep this file up to date. This is checked in CI.
# When adding new functions or changing the priorities, please read the comments and see if
# they need to be updated to be consistent with the changes you are making.
#
# Entries are ordered by the order of execution (i.e. from low priority values to high ones).
# Each line has the following format:
refactor(startup): implement registration of core init functions Similar to how the secondary init functions were already registered via ESP_SYSTEM_INIT_FN, do the same for the core init functions. This MR doesn't actually move the init functions into respective components yet. This has to be carefully done in follow-up MRs.
2023-11-24 12:32:37 -05:00
# stage: prio: function_name in path/to/source_file on affinity_expression
esp_system: add a script to check the startup priorities
2022-05-18 11:25:38 -04:00
# Where:
refactor(startup): implement registration of core init functions Similar to how the secondary init functions were already registered via ESP_SYSTEM_INIT_FN, do the same for the core init functions. This MR doesn't actually move the init functions into respective components yet. This has to be carefully done in follow-up MRs.
2023-11-24 12:32:37 -05:00
# stage: which startup stage the function is executed in (CORE or SECONDARY)
esp_system: add a script to check the startup priorities
2022-05-18 11:25:38 -04:00
# prio: priority value (higher value means function is executed later)
# affinity_expression: bit map of cores the function is executed on
refactor(startup): implement registration of core init functions Similar to how the secondary init functions were already registered via ESP_SYSTEM_INIT_FN, do the same for the core init functions. This MR doesn't actually move the init functions into respective components yet. This has to be carefully done in follow-up MRs.
2023-11-24 12:32:37 -05:00
########### CORE startup stage ###########
# [refactor-todo]: move init calls into respective components
feat(efuse): Move efuse-related init steps into the component
2024-01-11 07:59:08 -05:00
CORE: 1: init_efuse_check in components/efuse/src/esp_efuse_startup.c on BIT(0)
refactor(startup): implement registration of core init functions Similar to how the secondary init functions were already registered via ESP_SYSTEM_INIT_FN, do the same for the core init functions. This MR doesn't actually move the init functions into respective components yet. This has to be carefully done in follow-up MRs.
2023-11-24 12:32:37 -05:00
# Log some information about the system
CORE: 10: init_show_cpu_freq in components/esp_system/startup_funcs.c on BIT(0)
refactor(esp_app_format): Move esp_app_format-related init steps into the component
2024-02-05 01:10:30 -05:00
CORE: 20: init_show_app_info in components/esp_app_format/esp_app_desc.c on BIT(0)
feat(efuse): Move efuse-related init steps into the component
2024-01-11 07:59:08 -05:00
CORE: 21: init_efuse_show_app_info in components/efuse/src/esp_efuse_startup.c on BIT(0)
refactor(startup): implement registration of core init functions Similar to how the secondary init functions were already registered via ESP_SYSTEM_INIT_FN, do the same for the core init functions. This MR doesn't actually move the init functions into respective components yet. This has to be carefully done in follow-up MRs.
2023-11-24 12:32:37 -05:00
# Initialize heap allocator. WARNING: This *needs* to happen *after* the app cpu has booted.
# If the heap allocator is initialized first, it will put free memory linked list items into
# memory also used by the ROM. Starting the app cpu will let its ROM initialize that memory,
# corrupting those linked lists. Initializing the allocator *after* the app cpu has booted
# works around this problem.
# With SPI RAM enabled, there's a second reason: half of the SPI RAM will be managed by the
# app CPU, and when that is not up yet, the memory will be inaccessible and heap_caps_init may
# fail initializing it properly.
refactor(heap): decouple heap_init from esp_system
2024-02-12 05:10:33 -05:00
CORE: 100: init_heap in components/heap/heap_caps_init.c on BIT(0)
refactor(startup): implement registration of core init functions Similar to how the secondary init functions were already registered via ESP_SYSTEM_INIT_FN, do the same for the core init functions. This MR doesn't actually move the init functions into respective components yet. This has to be carefully done in follow-up MRs.
2023-11-24 12:32:37 -05:00
# When apptrace module is enabled, there will be SEGGER_SYSVIEW calls in the newlib init.
# SEGGER_SYSVIEW relies on apptrace module
# apptrace module uses esp_timer_get_time to determine timeout conditions.
# esp_timer early initialization is required for esp_timer_get_time to work.
feat(esp_timer): Move esp_timer-related init steps into the component
2024-01-23 13:10:20 -05:00
CORE: 101: esp_timer_init_nonos in components/esp_timer/src/esp_timer_init.c on BIT(0)
refactor(startup): implement registration of core init functions Similar to how the secondary init functions were already registered via ESP_SYSTEM_INIT_FN, do the same for the core init functions. This MR doesn't actually move the init functions into respective components yet. This has to be carefully done in follow-up MRs.
2023-11-24 12:32:37 -05:00
refactor(uart_vfs): Move uart implementation of vfs to esp_driver_uart Deprecated esp_vfs_dev_uart_xxx APIs vfs_uart test case moved to esp_driver_uart test_apps Astyle fixed for uart_vfs
2023-11-24 01:56:08 -05:00
CORE: 102: init_newlib in components/newlib/newlib_init.c on BIT(0)
refactor(esp_psram): Decouple psram init from esp_system
2024-02-14 01:33:27 -05:00
CORE: 103: init_psram in components/esp_psram/esp_psram.c on BIT(0)
refactor(startup): implement registration of core init functions Similar to how the secondary init functions were already registered via ESP_SYSTEM_INIT_FN, do the same for the core init functions. This MR doesn't actually move the init functions into respective components yet. This has to be carefully done in follow-up MRs.
2023-11-24 12:32:37 -05:00
CORE: 104: init_brownout in components/esp_system/startup_funcs.c on BIT(0)
CORE: 105: init_newlib_time in components/esp_system/startup_funcs.c on BIT(0)
refactor(uart_vfs): Move uart implementation of vfs to esp_driver_uart Deprecated esp_vfs_dev_uart_xxx APIs vfs_uart test case moved to esp_driver_uart test_apps Astyle fixed for uart_vfs
2023-11-24 01:56:08 -05:00
# Peripheral-specific implementation operators should be filled first
# Then register vfs console, and follow by newlib stdio initialization
CORE: 110: init_vfs_uart in components/esp_driver_uart/src/uart_vfs.c on BIT(0)
refactor(usb_serial_jtag): make usb_serial_jtag as component
2024-01-02 05:08:35 -05:00
CORE: 111: init_vfs_usj in components/esp_driver_usb_serial_jtag/src/usb_serial_jtag_vfs.c on BIT(0)
CORE: 112: init_vfs_usj_sec in components/esp_driver_usb_serial_jtag/src/usb_serial_jtag_vfs.c on BIT(0)
feat(storage/vfs): add /dev/null for unwanted output redirection
2024-04-19 04:03:36 -04:00
CORE: 113: init_vfs_nullfs in components/vfs/nullfs.c on BIT(0)
fix(esp_vfs_console): add esp_vfs_console component move vfs_console related init steps from vfs component to new esp_vfs_console component
2024-01-23 06:09:57 -05:00
CORE: 114: init_vfs_console in components/esp_vfs_console/vfs_console.c on BIT(0)
refactor(uart_vfs): Move uart implementation of vfs to esp_driver_uart Deprecated esp_vfs_dev_uart_xxx APIs vfs_uart test case moved to esp_driver_uart test_apps Astyle fixed for uart_vfs
2023-11-24 01:56:08 -05:00
CORE: 115: init_newlib_stdio in components/newlib/newlib_init.c on BIT(0)
refactor(pthread): decouple pthread_init from esp_system
2024-02-05 04:38:53 -05:00
CORE: 120: init_pthread in components/pthread/pthread.c on BIT(0)
refactor(startup): implement registration of core init functions Similar to how the secondary init functions were already registered via ESP_SYSTEM_INIT_FN, do the same for the core init functions. This MR doesn't actually move the init functions into respective components yet. This has to be carefully done in follow-up MRs.
2023-11-24 12:32:37 -05:00
CORE: 130: init_flash in components/esp_system/startup_funcs.c on BIT(0)
feat(efuse): Move efuse-related init steps into the component
2024-01-11 07:59:08 -05:00
CORE: 140: init_efuse in components/efuse/src/esp_efuse_startup.c on BIT(0)
refactor(startup): implement registration of core init functions Similar to how the secondary init functions were already registered via ESP_SYSTEM_INIT_FN, do the same for the core init functions. This MR doesn't actually move the init functions into respective components yet. This has to be carefully done in follow-up MRs.
2023-11-24 12:32:37 -05:00
CORE: 170: init_xt_wdt in components/esp_system/startup_funcs.c on BIT(0)
########### SECONDARY startup stage ###########
esp_timer: perform initialization using ESP_SYSTEM_INIT_FN (startup.c still calls esp_timer_early_init directly)
2022-05-17 19:14:42 -04:00
# esp_timer has to be initialized early, since it is used by several other components
feat(esp_timer): Move esp_timer-related init steps into the component
2024-01-23 13:10:20 -05:00
SECONDARY: 100: esp_timer_init_os in components/esp_timer/src/esp_timer.c on ESP_TIMER_INIT_MASK
esp_timer: perform initialization using ESP_SYSTEM_INIT_FN (startup.c still calls esp_timer_early_init directly)
2022-05-17 19:14:42 -04:00
feat(esp_system): implement hw stack guard for riscv chips - add hardware stack guard based on assist-debug module - enable hardware stack guard by default - disable hardware stack guard for freertos ci.release test - refactor rtos_int_enter/rtos_int_exit to change SP register inside them - fix panic_reason.h header for RISC-V - update docs to include information about the new feature
2023-05-04 11:31:31 -04:00
# HW stack guard via assist-debug module.
refactor(startup): implement registration of core init functions Similar to how the secondary init functions were already registered via ESP_SYSTEM_INIT_FN, do the same for the core init functions. This MR doesn't actually move the init functions into respective components yet. This has to be carefully done in follow-up MRs.
2023-11-24 12:32:37 -05:00
SECONDARY: 101: esp_hw_stack_guard_init in components/esp_system/hw_stack_guard.c on ESP_SYSTEM_INIT_ALL_CORES
feat(esp_system): implement hw stack guard for riscv chips - add hardware stack guard based on assist-debug module - enable hardware stack guard by default - disable hardware stack guard for freertos ci.release test - refactor rtos_int_enter/rtos_int_exit to change SP register inside them - fix panic_reason.h header for RISC-V - update docs to include information about the new feature
2023-05-04 11:31:31 -04:00
feat(system): disable RNG module clock by default for save power
2024-02-28 04:04:18 -05:00
# RNG module clock was disabled in `esp_perip_clk_init`, if hw_random is used, need to re-ebnabled it in startup
SECONDARY: 102: init_rng_clock in components/esp_hw_support/hw_random.c on BIT(0)
esp_hw_support: perform sleep initialization using ESP_SYSTEM_INIT_FN
2022-05-17 19:15:38 -04:00
# esp_sleep doesn't have init dependencies
refactor(startup): implement registration of core init functions Similar to how the secondary init functions were already registered via ESP_SYSTEM_INIT_FN, do the same for the core init functions. This MR doesn't actually move the init functions into respective components yet. This has to be carefully done in follow-up MRs.
2023-11-24 12:32:37 -05:00
SECONDARY: 105: esp_sleep_startup_init in components/esp_hw_support/sleep_gpio.c on BIT(0)
SECONDARY: 106: sleep_clock_startup_init in components/esp_hw_support/sleep_clock.c on BIT(0)
SECONDARY: 107: sleep_sys_periph_startup_init in components/esp_hw_support/sleep_system_peripheral.c on BIT(0)
esp_hw_support: perform sleep initialization using ESP_SYSTEM_INIT_FN
2022-05-17 19:15:38 -04:00
app_trace: perform initialization using ESP_SYSTEM_INIT_FN
2022-05-17 19:16:12 -04:00
# app_trace has to be initialized before systemview
refactor(startup): implement registration of core init functions Similar to how the secondary init functions were already registered via ESP_SYSTEM_INIT_FN, do the same for the core init functions. This MR doesn't actually move the init functions into respective components yet. This has to be carefully done in follow-up MRs.
2023-11-24 12:32:37 -05:00
SECONDARY: 115: esp_apptrace_init in components/app_trace/app_trace.c on ESP_SYSTEM_INIT_ALL_CORES
SECONDARY: 120: sysview_init in components/app_trace/sys_view/esp/SEGGER_RTT_esp.c on BIT(0)
app_trace: perform initialization using ESP_SYSTEM_INIT_FN
2022-05-17 19:16:12 -04:00
feat(coredump): move esp_core_dump_init into component
2024-01-23 17:55:07 -05:00
# coredump doesn't have init dependencies
SECONDARY: 130: init_coredump in components/espcoredump/src/core_dump_init.c on BIT(0)
feat(system): move esp_dbg_stubs_init into component
2024-01-23 19:41:18 -05:00
# esp_debug_stubs doesn't have init dependencies
SECONDARY: 140: init_dbg_stubs in components/app_trace/debug_stubs.c on BIT(0)
refactor(startup): implement registration of core init functions Similar to how the secondary init functions were already registered via ESP_SYSTEM_INIT_FN, do the same for the core init functions. This MR doesn't actually move the init functions into respective components yet. This has to be carefully done in follow-up MRs.
2023-11-24 12:32:37 -05:00
# the rest of the components which are initialized from startup_funcs.c
esp_system: add a script to check the startup priorities
2022-05-18 11:25:38 -04:00
# [refactor-todo]: move init calls into respective components
refactor(startup): implement registration of core init functions Similar to how the secondary init functions were already registered via ESP_SYSTEM_INIT_FN, do the same for the core init functions. This MR doesn't actually move the init functions into respective components yet. This has to be carefully done in follow-up MRs.
2023-11-24 12:32:37 -05:00
SECONDARY: 201: init_pm in components/esp_system/startup_funcs.c on BIT(0)
SECONDARY: 203: init_apb_dma in components/esp_system/startup_funcs.c on BIT(0)
SECONDARY: 204: init_coexist in components/esp_system/startup_funcs.c on BIT(0)
esp_system: usb_console: fix restart when Wi-Fi is working Previously, reset over USB CDC was done by calling esp_restart from an interrupt handler. This works only until some restart hook function is registered using esp_register_shutdown_handler, and the hook function tries to do something that isn’t allowed in an interrupt handler. One such case is with Wi-Fi. When Wi-Fi driver is installed, it registers esp_wifi_stop as a shutdown handler function. However esp_wifi_stop cannot be called from an ISR, and hence we shouldn’t call esp_restart from an ISR either. This commit modifies USB CDC driver to call esp_restart by posting it to esp_timer task. Closes https://github.com/espressif/esp-idf/issues/7404
2022-01-18 14:49:58 -05:00
# usb_console needs to create an esp_timer at startup.
feat(esp_timer): Move esp_timer-related init steps into the component
2024-01-23 13:10:20 -05:00
# This can be done only after esp_timer initialization (esp_timer_init_os).
refactor(startup): implement registration of core init functions Similar to how the secondary init functions were already registered via ESP_SYSTEM_INIT_FN, do the same for the core init functions. This MR doesn't actually move the init functions into respective components yet. This has to be carefully done in follow-up MRs.
2023-11-24 12:32:37 -05:00
SECONDARY: 220: esp_usb_console_init_restart_timer in components/esp_system/port/usb_console.c on BIT(0)
# usb_serial_jtag needs to create and acquire a PM lock at startup.
# This makes more sense to be done after esp_pm_impl_init (called from init_pm).
refactor(usb_serial_jtag): make usb_serial_jtag as component
2024-01-02 05:08:35 -05:00
SECONDARY: 230: usb_serial_jtag_conn_status_init in components/esp_driver_usb_serial_jtag/src/usb_serial_jtag_connection_monitor.c on BIT(0)
refactor(startup): implement registration of core init functions Similar to how the secondary init functions were already registered via ESP_SYSTEM_INIT_FN, do the same for the core init functions. This MR doesn't actually move the init functions into respective components yet. This has to be carefully done in follow-up MRs.
2023-11-24 12:32:37 -05:00
# Has to be the last step!
# Now that the application is about to start, disable boot watchdog
SECONDARY: 999: init_disable_rtc_wdt in components/esp_system/startup_funcs.c on BIT(0)
usb_serial_jtag: Improve the code for the issue of usb cdc device unable to work during sleep 1. Remove RTC_CLOCK_BBPLL_POWER_ON_WITH_USB Kconfig option During sleep, BBPLL clock always gets disabled esp_restart does not disable BBPLL clock, so that first stage bootloader log can be printed 2. Add a new Kconfig option PM_NO_AUTO_LS_ON_USJ_CONNECTED When this option is selected, IDF will constantly monitor USB CDC port connection status. As long as it gets connected to a HOST, automatic light-sleep will not happen. Closes https://github.com/espressif/esp-idf/issues/8507
2022-11-07 12:54:23 -05:00
refactor(startup): implement registration of core init functions Similar to how the secondary init functions were already registered via ESP_SYSTEM_INIT_FN, do the same for the core init functions. This MR doesn't actually move the init functions into respective components yet. This has to be carefully done in follow-up MRs.
2023-11-24 12:32:37 -05:00
# DO NOT add new init functions here. Add them to the correct stage above.
Reference in New Issue Copy Permalink