esp-idf/components
Jiang Jiang Jian dd8080e164 Merge branch 'bugfix/BT-3491_v5.1' into 'release/v5.1'
bugfix(ble_mesh): Avoid provisioner handling messages from nodes that have...(v5.1)

See merge request espressif/esp-idf!28050
2024-04-12 10:30:49 +08:00
..
app_trace Merge branch 'fix/segger_sysview_build_v5.1' into 'release/v5.1' 2024-03-05 10:52:35 +08:00
app_update fix(app_update): fixed undeclared variable 'ret' in esp_ota_ops.c 2024-01-19 14:04:06 +05:30
bootloader doc(spi_flash): hide unsupported optional features 2024-03-12 10:48:08 +08:00
bootloader_support doc(spi_flash): hide unsupported optional features 2024-03-12 10:48:08 +08:00
bt Merge branch 'bugfix/BT-3491_v5.1' into 'release/v5.1' 2024-04-12 10:30:49 +08:00
cmock
console fix(console): Fix build issues when CONFIG_ESP_CONSOLE_NONE is enabled 2024-02-29 17:48:07 +08:00
cxx
driver Merge branch 'bugfix/gptimer_alarm_config_in_sram_v5.1' into 'release/v5.1' 2024-04-12 09:08:41 +08:00
efuse feat(efuse): Add flash&psram efuses for S3 2024-02-21 09:36:49 +02:00
esp_adc Merge branch 'bugfix/workaround_reset_eof_counter_c3_v5.1' into 'release/v5.1' 2024-03-14 10:44:23 +08:00
esp_app_format fix(ota): additional checks for secure version in anti-rollback case 2024-02-15 15:10:28 +02:00
esp_coex feat(coex): support to scan long time on channel, fix coexist sync issue 2024-03-15 10:49:18 +08:00
esp_common versions: Update version to 5.1.3 2024-02-26 11:09:16 +08:00
esp_eth Merge branch 'feature/mmd_access_v5.1' into 'release/v5.1' 2024-02-29 20:29:57 +08:00
esp_event docs(esp_event): Fixed mistake in API docs 2024-03-12 10:33:10 +08:00
esp_gdbstub fix(soc): change debug addr range to CPU subsystem range 2024-01-24 12:52:27 +05:30
esp_hid feat(nimble): added HID over Gatt profile support 2023-12-22 11:23:05 +05:30
esp_http_client Revert "fix(esp_http_client): Call event_handler after header value is received" 2024-04-01 13:19:57 +05:30
esp_http_server feat: ECDSA peripheral while performing http connection with mutual auth 2023-11-17 16:24:10 +05:30
esp_https_ota Merge branch 'bugfix/preencrypted_ota_failed_with_partial_download_v5.1' into 'release/v5.1' 2023-11-29 14:05:39 +08:00
esp_https_server feat: ECDSA peripheral while performing http connection with mutual auth 2023-11-17 16:24:10 +05:30
esp_hw_support Merge branch 'fix/fix_pmu_power_domain_initialize_order_v5.1' into 'release/v5.1' 2024-04-10 17:23:55 +08:00
esp_lcd fix(esp_lcd): Flush rgb lcd PSRAM framebuffers after allocation 2024-03-04 17:39:22 +08:00
esp_local_ctrl refactor(protocomm): Make the protocomm proto-c headers public 2024-03-01 10:26:42 +05:30
esp_mm fix(cache): no longer use freeze in esp_cache_msync 2023-07-21 17:19:11 +08:00
esp_netif Merge branch 'fix/esp_netif_lock_v5.1' into 'release/v5.1' 2023-12-08 11:18:09 +08:00
esp_netif_stack
esp_partition feat(example/storage/littlefs): add LittleFS demo example 2024-03-12 20:58:14 +08:00
esp_phy fix(esp_phy): update phylib for C3, S3, C2 and C6 2024-04-10 20:35:34 +08:00
esp_pm fix(esp_pm): safely check ccompare validity in DFS update_ccompare 2024-01-19 11:14:28 +08:00
esp_psram spi_flash: fixed issue that enabling HPM-DC by default may cause app unable to restart 2024-03-12 10:48:08 +08:00
esp_ringbuf
esp_rom fix(wifi): fixed some wifi issue 2024-04-11 15:33:43 +08:00
esp_system fix(clk): clear all lpclk source at clk init 2024-03-15 10:49:18 +08:00
esp_timer refactor(esp_timer): Remove duplicate code and move it to a common file 2023-08-22 17:22:24 +08:00
esp_wifi fix(wifi): fixed some wifi issue 2024-04-11 15:33:43 +08:00
esp-tls Merge branch 'fix/wrong_order_of_includes_in_esp_tls_v5.1' into 'release/v5.1' 2023-12-12 13:44:36 +08:00
espcoredump feat(coredump): save twdt panic output to coredump elf file 2024-03-12 10:40:29 +01:00
esptool_py spi_flash: fixed issue that enabling HPM-DC by default may cause app unable to restart 2024-03-12 10:48:08 +08:00
fatfs fix(storage/fatfs): check whether sdcard supports triming 2024-01-08 09:35:01 +01:00
freertos Merge branch 'bugfix/fix_freertos_system_task_names_v5.1' into 'release/v5.1' 2023-11-14 16:35:25 +08:00
hal fix: fix s3 bbpll cali fail bug 2024-03-14 15:45:37 +08:00
heap fix(heap): Wrong size propagated in alloc fail callback 2024-04-08 08:42:49 +02:00
http_parser
idf_test Merge branch 'feature/support_adc_calibration_on_h2_v5.1' into 'release/v5.1' 2023-11-17 16:41:00 +08:00
ieee802154 fix(802154): fix pending tx will be delayed issue 2024-02-01 14:16:00 +08:00
json feat(cjson): update submodule to v1.7.17 2024-01-19 14:06:11 +05:30
linux
log
lwip ci: build default app for lwip test app 2024-03-08 11:06:21 +01:00
mbedtls ci(mbedtls/gcm): Added test to verify software fallback for non-AES cipher GCM operations 2024-03-12 13:35:54 +05:30
mqtt change(mqtt): Update submodule to e6afdb 2023-10-02 06:23:35 +00:00
newlib feat(newlib): Add definition of aligned_alloc to heap.c 2024-03-12 14:07:53 +08:00
nvs_flash fix(nvs): Fixed Page::findItem performance degradation caused by wrong condition before hash map use 2024-03-12 16:27:36 +01:00
openthread fix(openthread): using atomic variable for buffer count 2024-03-14 17:18:16 +08:00
partition_table feat(example/storage/littlefs): add LittleFS demo example 2024-03-12 20:58:14 +08:00
perfmon
protobuf-c
protocomm Merge branch 'refactor/protocomm_public_hdr_v5.1' into 'release/v5.1' 2024-03-01 21:42:08 +08:00
pthread fix(pthread): fixed pthread_condvar linker hook 2023-09-18 12:31:25 +08:00
riscv fix(riscv): supports 1 byte and larger than 64byte range watchpoint setting 2023-11-16 20:40:04 +08:00
sdmmc fix(sdmmc): extend the maximum number of retries of ACMD41 2024-03-14 13:49:23 +08:00
soc [S3]fix(rtc_cntl_reg.h): fix RTC_CNTL_SLAVE_PD_M 2024-04-10 19:51:25 +08:00
spi_flash fix(spi_flash): Fix spi_flash counter test on CI 2024-03-18 20:23:55 +08:00
spiffs fix(spiffs): SPIFFS print formatter errors out 2023-08-17 11:46:25 +02:00
tcp_transport fix(tcp_transport): Fix coverity report regarding tcp_transport 2024-03-13 11:25:12 +05:30
touch_element
ulp change(ulp): added test for ulp adc init/deinit 2024-03-12 10:52:06 +08:00
unity
usb Merge branch 'feature/usb_hs_periodic_scheduler_v5.1' into 'release/v5.1' 2024-03-11 21:20:35 +08:00
vfs fix(vfs): fix eventfd select 2024-03-15 17:38:28 +08:00
wear_levelling
wifi_provisioning fix(wifi): fix esp_wifi_scan_start memory leakage issue 2024-03-11 10:49:18 +08:00
wpa_supplicant fix(wpa_supplicant): Compile error when CONFIG_SAE is disabled 2024-04-11 11:18:58 +05:30
xtensa
README.md

Core Components

Overview

This document contains details about what the core components are, what they contain, and how they are organized.

Organization

The core components are organized into two groups.

The first group (referred to as G0 from now on) contains hal, xtensa and riscv (referred to as arch components from now on), esp_rom, esp_common, and soc. This group contain information about and low-level access to underlying hardware; or in the case of esp_common, hardware-agnostic code and utilities. These components can depend on each other, but as much as possible have no dependencies outside the group. The reason for this is that, due to the nature of what these components contain, the likelihood is high that a lot of other components will require these. Ideally, then, the dependency relationship only goes one way. This makes it easier for these components, as a group, to be usable in another project. One can conceivably implement a competing SDK to ESP-IDF on top of these components.

The second group (referred to as G1 from now on) sits at a higher level than the first group. This group contains the components esp_hw_support, esp_system, newlib, spi_flash, freertos, log, and heap. Like the first group, circular dependencies within the group are allowed; and being at a higher level, dependency on the first group is allowed. These components represent software mechanisms essential to building other components.

Descriptions

The following is a short description of the components mentioned above.

G0 Components

hal

Contains the hardware abstraction layer and low-level operation implementations for the various peripherals. The low-level functions assign meaningful names to register-level manipulations; the hardware abstraction provide operations one level above this, grouping these low-level functions into routines that achieve a meaningful action or state of the peripheral.

Example:

  • spi_flash_ll_set_address is a low-level function part of the hardware abstraction spi_flash_hal_read_block

arch

Contains low-level architecture operations and definitions, including those for customizations (can be thought of on the same level as the low-level functions of hal). This can also contain files provided by the architecture vendor.

Example:

  • xt_set_exception_handler
  • rv_utils_intr_enable
  • ERI_PERFMON_MAX

esp_common

Contains hardware-agnostic definitions, constants, macros, utilities, 'pure' and/or algorithmic functions that is useable by all other components (that is, barring there being a more appropriate component to put them in).

Example:

  • BIT(nr) and other bit manipulation utilities in the future
  • IDF_DEPRECATED(REASON)
  • ESP_IDF_VERSION_MAJOR

soc

Contains description of the underlying hardware: register structure, addresses, pins, capabilities, etc.

Example:

  • DR_REG_DPORT_BASE
  • SOC_MCPWM_SUPPORTED
  • uart_dev_s

esp_rom

Contains headers, linker scripts, abstraction layer, patches, and other related files to ROM functions.

Example:

  • esp32.rom.eco3.ld
  • rom/aes.h

G1 Components

spi_flash

SPI flash device access implementation.

freertos

FreeRTOS port to targets supported by ESP-IDF.

log

Logging library.

heap

Heap implementation.

newlib

Some functions n the standard library are implemented here, especially those needing other G1 components.

Example:

  • malloc is implemented in terms of the component heap's functions
  • gettimeofday is implemented in terms of system time in esp_system

esp_system

Contains implementation of system services and controls system behavior. The implementations here may take hardware resources and/or decide on a hardware state needed for support of a system service/feature/mechanism. Currently, this encompasses the following, but not limited to:

  • Startup and initialization
  • Panic and debug
  • Reset and reset reason
  • Task and interrupt watchdogs

esp_hw_support

Contains implementations that provide hardware operations, arbitration, or resource sharing, especially those that is used in the system. Unlike esp_system, implementations here do not decide on a hardware state or takes hardware resource, acting merely as facilitator to hardware access. Currently, this encompasses the following, but not limited to:

  • Interrupt allocation
  • Sleep functions
  • Memory functions (external SPIRAM, async memory, etc.)
  • Clock and clock control
  • Random generation
  • CPU utilities
  • MAC settings

esp_hw_support vs esp_system

This section details list some implementations and the reason for placing it in either esp_hw_support or esp_system.

task_wdt.c (esp_system) vs intr_alloc.c (esp_hw_support)

The task watchdog fits the definition of taking and configuring hardware resources (wdt, interrupt) for implementation of a system service/mechanism.

This is in contrast with interrupt allocation that merely facilitates access to the underlying hardware for other implementations - drivers, user code, and even the task watchdog mentioned previously!

crosscore_int.c (esp_system)

The current implementation of crosscore interrupts is tightly coupled with a number of interrupt reasons associated with system services/mechanisms: REASON_YIELD (scheduler), REASON_FREQ_SWITCH (power management) REASON_PRINT_BACKTRACE (panic and debug).

However, if an implementation exists that makes it possible to register an arbitrary interrupt reason - a lower level inter-processor call if you will, then this implementation is a good candidate for esp_hw_support. The current implementation in esp_system can then just register the interrupt reasons mentioned above.

esp_mac.h, esp_chip_info.h, esp_random.h (esp_hw_support)

The functions in these headers used to be in esp_system.h, but have been split-off.

The remaining functions in esp_system.h are those that deal with system behavior, such as esp_register_shutdown_handler, or are proxy for other system components's APIs such as esp_get_free_heap_size.

The functions split-off from esp_system.h are much more hardware manipulation oriented such as: esp_read_mac, esp_random and esp_chip_info.