Commit Graph

6689 Commits

Author SHA1 Message Date
Alexey Lapshin 4e2cb08534 feat(gdbstub): add f- and q-registers support 2026-03-27 17:04:24 +08:00
Jiang Jiang Jian 60bcaa6447 Merge branch 'fix/coredump_test_tcb_corrupted_v5.5' into 'release/v5.5'
test(espcoredump): fix test for corrupted TCB handling in coredump (v5.5)

See merge request espressif/esp-idf!45327
2026-03-03 19:37:10 +08:00
Fu Hanxi 6d0dfc32b6 ci: fix fast_template_app (v5.5) 2026-02-27 09:46:39 +01:00
Alexey Gerenkov 0c7eac2565 Merge branch 'feature/picolibc_v5.5' into 'release/v5.5'
feat(build): add Picolibc support (v5.5)

See merge request espressif/esp-idf!44108
2026-02-26 18:12:58 +08:00
Fu Hanxi 124a1d3b82 ci: backport master to 5.5 2026-02-25 11:38:38 +01:00
Roland Dobai 847ee14822 Merge branch 'fix/minimal_build_no_main_v5.5' into 'release/v5.5'
fix(build): ensure the main component exists when MINIMAL_BUILD is enabled (v5.5)

See merge request espressif/esp-idf!45916
2026-02-19 09:43:00 +01:00
Frantisek Hrbata 0d55253c8c fix(test_build_system): apply ruff formatting to test_components.py
Signed-off-by: Frantisek Hrbata <frantisek.hrbata@espressif.com>
2026-02-19 06:21:57 +01:00
Frantisek Hrbata 4818b0b2c5 fix(build): ensure the main component exists when MINIMAL_BUILD is enabled
The minimal build property is simply a shorthand for `set(COMPONENTS
main)`. The issue is that there is currently no check to verify whether
the `main` component actually exists or is known to the build system.
If the `main` component is not present, print an error message along
with suggestions on how to fix this inconsistency.

Closes https://github.com/espressif/esp-idf/issues/18219

Signed-off-by: Frantisek Hrbata <frantisek.hrbata@espressif.com>
2026-02-19 06:19:25 +01:00
Aditya Patwardhan 2c211b2367 change(version): Update version to 5.5.3 2026-02-17 19:24:16 +05:50
Alexey Lapshin 74ed018fc1 fix(test): fix tests according to the new toolchain flags 2026-02-05 13:40:11 +07:00
Fu Hanxi 3adb2a22c9 ci: ignore eco3 marker from adding rev_default marker 2026-02-02 12:36:42 +01:00
Alexey Lapshin c482665638 fix(ci): fix check_public_headers.py to check system headers 2026-02-02 12:27:24 +07:00
Alexey Lapshin 0b3929d0d9 feat(esp_libc): add full support for picolibc 2026-01-30 23:39:53 +07:00
Alexey Lapshin 1c08b38b27 feat(build): propagate compiler flags from files to toolchain.cmake
This change improves build consistency across external projects integrated
through CMake by ensuring that compiler flags defined in configuration files
are passed correctly to the toolchain. It covers the majority of use cases,
as external projects are typically also CMake-based. For projects that use
a custom build system, users will still need to specify the required flags
manually.
2026-01-30 17:30:49 +07:00
Alexey Lapshin 21fa93e55a feat(tools): update toolchain version to esp-14.2.0_20260121 2026-01-30 17:30:49 +07:00
Erhan Kurubas 8dbf56e077 test(espcoredump): fix test for corrupted TCB handling in coredump 2026-01-21 18:44:44 +03:00
Erhan Kurubas 88efba061e test(panic): improve stack dump capture to return full hex content 2026-01-21 18:37:52 +03:00
Alexey Gerenkov 69550e12e2 Merge branch 'fix/int_wdt_double_exception_v5.5' into 'release/v5.5'
fix(espcoredump): prevent double exception during int_wdt panic with custom stack (v5.5)

See merge request espressif/esp-idf!44174
2026-01-21 23:03:41 +08:00
Erhan Kurubas b38c003cb1 test(panic): add retry logic to espcoredump subprocess call 2026-01-21 00:24:38 +03:00
Roland Dobai 9c0f87f677 Merge branch 'contrib/github_pr_18103_v5.5' into 'release/v5.5'
Fix "IMPORTED_LOCATION not set for imported target" CMake errors during codemodel-v2 api queries with CMake 4.2 (GitHub PR) (v5.5)

See merge request espressif/esp-idf!45200
2026-01-20 20:42:22 +01:00
Fu Hanxi 85240aef96 ci: introduce default marker rev_default 2026-01-20 16:51:33 +08:00
Jiang Jiang Jian ca22d0e8ec Merge branch 'fix/minimal_build_property_v5.5' into 'release/v5.5'
fix(cmake): disable MINIMAL_BUILD build property if COMPONENTS is defined (v5.5)

See merge request espressif/esp-idf!45117
2026-01-19 11:11:49 +08:00
Ferdinand Bachmann bfb2c74b20 fix(cmake): Fix "IMPORTED_LOCATION not set for imported target" errors
esp-idf uses imported targets as dummy targets that are never linked.
Previous CMake versions would ignore these and not error on unset
IMPORTED_LOCATION if they are never actually linked. CMake 4.2 and newer
errors during codemodel-v2 api queries when imported targets are missing
IMPORTED_LOCATION, so set a dummy location that would error when
actually linked, which fixes the error during api queries.

Closes https://github.com/espressif/esp-idf/pull/18103
2026-01-16 12:11:20 +01:00
Jiang Jiang Jian f0538f38af Merge branch 'fix/ldgen_ipa_constprop_v5.5' into 'release/v5.5'
fix(ldgen): correctly place symbols generated by compiler during IPA (v5.5)

See merge request espressif/esp-idf!45111
2026-01-16 16:32:35 +08:00
Jiang Jiang Jian 8a2f308a07 Merge branch 'bugfix/esp_idf_c5_eco3_cpu_lockup_v5.5' into 'release/v5.5'
change: support top pd during sleep for esp32c5 eco3 and remove sleep mmu related flow (v5.5)

See merge request espressif/esp-idf!43570
2026-01-16 14:21:02 +08:00
Frantisek Hrbata b12bc58494 fix(cmake): disable MINIMAL_BUILD build property if COMPONENTS is defined
The MINIMAL_BUILD build property and the COMPONENTS variable are both
used to determine the initial component list for the build.

Currently, if the COMPONENTS variable is set, the MINIMAL_BUILD logic
is ignored during component selection, but the MINIMAL_BUILD build
property remains set. This leads to an inconsistent state where
menuconfig displays information indicating MINIMAL_BUILD is active,
even though it was ignored in favor of the COMPONENTS variable.

Fix this by setting the MINIMAL_BUILD property to OFF if the
COMPONENTS variable is used.

Signed-off-by: Frantisek Hrbata <frantisek.hrbata@espressif.com>
2026-01-16 13:00:38 +08:00
yinqingzhao 880a3c4d80 test(system): add esp32c61 eco4 build test 2026-01-16 11:40:31 +08:00
wanglei 7fca8a9c68 test(system): add esp32c5 eco3 build test 2026-01-16 11:40:31 +08:00
Frantisek Hrbata b28902c95a fix(ldgen): correct formatting issues reported by ruff
Resolve ruff's UP031 errors related to the use of percent formatting for
strings and lines longer than 120 characters.

Signed-off-by: Frantisek Hrbata <frantisek.hrbata@espressif.com>
2026-01-15 11:44:58 +01:00
hebinglin 17c110d640 change(esp_driver): set cases with toppd check only run in esp32c5eco3 rather than eco2 2026-01-15 17:04:17 +08:00
Frantisek Hrbata 6f9024233e fix(ldgen): correctly place symbols generated by compiler during IPA
As part of inter-procedural optimizations (IPA), the compiler may
perform tasks such as constant propagation for functions. This involves
generating a specialized version of a given function with a new symbol
name that includes a suffix. For example, during constant propagation,
the compiler might create a specialized version named
`spiflash_start_core.constprop.0` for the `spiflash_start_core`
function. Additionally, the compiler may generate multiple clones of a
single function. Currently, when ldgen performs symbol placement, it
does not account for these compiler-generated functions, leading to
their incorrect or unexpected placement in memory (markers).

Consider a linker fragment with:

```
[mapping:spi_flash]
archive: libspi_flash.a
entries:
    esp_flash_api: spiflash_start_core (noflash)
```

The `spiflash_start_core` function should be placed in IRAM. However,
the compiler might generate an optimized version of this function with a
`.constprop.0` suffix, resulting in a
`.text.spiflash_start_core.constprop.0` input section. Currently, ldgen
does not handle this situation, leading to misplaced symbols.

Since `.` is not allowed in C identifiers, it should be safe to consider
all input sections for a symbol with any `.` suffix as representing that
symbol. This means considering the symbol suffixes should not cause any
ambiguity.

This change automatically places all input sections, including those
with possible suffixes for a given symbol, into the specified memory. In
other words, specifying a function name like `spiflash_start_core` in a
linker fragment automatically includes input section names matching
`spiflash_start_core(\..*)?$`.

Signed-off-by: Frantisek Hrbata <frantisek.hrbata@espressif.com>
2026-01-14 13:22:38 +01:00
Li Shuai 9ed3a7a49a change(tools): disable place rtc clock and rtc time modules into iram for flash auto suspend test 2025-12-31 14:37:46 +08:00
Chen Yudong dae2b988f4 ci: rename wifi_two_dut to two_duts 2025-12-30 10:53:16 +08:00
Jiang Jiang Jian fbfa940c73 Merge branch 'feature/update-openocd-to-v0.12.0-esp32-20251215_v5.5' into 'release/v5.5'
feat(tools): update openocd version to v0.12.0-esp32-20251215 (v5.5)

See merge request espressif/esp-idf!44311
2025-12-30 10:35:19 +08:00
Jiang Jiang Jian 3824958e95 Merge branch 'ci/known-failure-dut-id-v5.5' into 'release/v5.5'
ci: pytest-ignore skip using dut id

See merge request espressif/esp-idf!43625
2025-12-30 10:33:51 +08:00
Roland Dobai b214c68cc7 Merge branch 'feat/update_ccache_to_4.12.1_v5.5' into 'release/v5.5'
feat(tools): Updated ccache 4.11.2 -> 4.12.1 (v5.5)

See merge request espressif/esp-idf!43567
2025-12-26 07:03:22 +01:00
morris 30aaf64524 change(version): Update version to 5.5.2 2025-12-24 22:34:47 +08:00
morris 094518fa0d fix(check_placements): update method names to follow PEP 8 conventions 2025-12-23 16:28:08 +08:00
Erhan Kurubas 1991aa6da0 fix(espcoredump): prevent double exception during int_wdt panic with custom stack 2025-12-17 21:36:19 +01:00
Erhan Kurubas 2501b4403f feat(tools): update openocd version to v0.12.0-esp32-20251215 2025-12-16 12:45:12 +01:00
Marek Fiala 69873c01ab feat(tools): Updated ccache 4.11.2 -> 4.12.1
Closes https://github.com/espressif/esp-idf/issues/17756
2025-11-28 15:17:49 +08:00
Marek Fiala 2d47ed3c68 refactor(tools): test_idf_tools.py ruff changes 2025-11-28 15:17:49 +08:00
igor.udot 97a8ee870f ci: pytest-ignore skip using dut id 2025-11-27 08:56:36 +08:00
Omar Chebib a5bce887ab ci: re-enable eh_frame for the ESP32-P4 2025-11-26 11:40:01 +05:30
igor.udot 82cf7083e3 ci: disable p4 rev3 invalid tests temporarily for v5.5 only 2025-11-21 11:28:08 +08:00
armando a3bca48289 ci(p4): disable p4 rev3 invalid tests temporarily for v5.5 only 2025-11-21 09:19:16 +08:00
armando 4ef2005b80 change(ci): use p4 rev3 by default only when ci build 2025-11-20 11:33:36 +08:00
armando 304ba1655b fix check test scripts build issue 2025-11-20 11:33:36 +08:00
armando cdff2570c7 ci(p4): disable p4 rev3 invalid tests temporarily 2025-11-20 11:33:36 +08:00
armando 8f85983c9d ci(p4): re-enable p4 jobs 2025-11-20 11:33:36 +08:00